[tulip] Lynksys ver2 not yet working

Sat, 20 May 2000 15:51:35 -0400

Hi,

The basic answer is that when you compile tulip.c v0.92, you also have to 
compile pci-scan.c that came with it. When it's done, run depmod -a to 
check module dependencies and then you can do modprobe tulip, or you can 
insert the pci-scan.o module manually before inserting the tulip.o module.

At 14:33 00-05-20 -0400, you wrote:
>Hi,
>O'K I know it is not yet a problem, just I'm lacking understanding
>something in
>configuration, so I'd appreciate some guidance
>
>I'm running 2.2.5 kernel (remnant of RH6.0 installation) and already
>have one tulip
>card (Accton EN1207 with original DEC 21140 chip - I guess 21140 AB) in
>my computer.
>It lives happily with 89H tulip driver.
>
>Now I got Lynksys  100 TX Fast Ethernet Adaptor (ver 2) yesterday and
>plug it
>into my machine, and it does not work.   Of course, you would say that
>I should
>upgrade to newer kernel/driver or use the driver supplied by Lynksys,
>and this will be
>a part of my question. But, first of all preliminaries
>
>PCI code detects the card allright (to my understanding)
>#cat /proc/pci
>
>   Bus  0, device  10, function  0:
>     Ethernet controller: DEC DC21140 (rev 34).
>       Medium devsel.  Fast back-to-back capable.  IRQ 9.  Master
>Capable.  Latency=32.  Min Gnt=20.Max Lat=40.
>       I/O at 0xc000 [0xc001].
>       Non-prefetchable 32 bit memory at 0xe1800000 [0xe1800000].
>   Bus  0, device  11, function  0:
>     Ethernet controller: LiteOn Unknown device (rev 37).
>       Vendor id=11ad. Device id=c115.
>       Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master
>Capable.  Latency=32.  Min Gnt=8.Max Lat=56.
>       I/O at 0xb800 [0xb801].
>       Non-prefetchable 32 bit memory at 0xe1000000 [0xe1000000].
>
>tulip-diag is also happy ( I have version  v1.19 10/2/99, so fairly new
>in comparison with the tulip driver itself)
>
>#tulip-diagtulip-diag.c:v1.19 10/2/99 Donald Becker
>(becker@cesdis.gsfc.nasa.gov)
>Index #1: Found a Digital DS21140 Tulip adapter at 0xc000.
>  Port selection is MII, half-duplex.
>  Transmit started, Receive started, half-duplex.
>   The Rx process state is 'Waiting for packets'.
>   The Tx process state is 'Idle'.
>   The transmit threshold is 128.
>Index #2: Found a Lite-On PNIC-II adapter at 0xb800.
>  Port selection is 10mpbs-serial, half-duplex.
>  Transmit stopped, Receive stopped, half-duplex.
>   The Rx process state is 'Stopped'.
>   The Tx process state is 'Stopped'.
>   The transmit threshold is 72.
>   The NWay status register is 000020ce.
>  The current PNIC-II MAC address is 00:a0:cc:e3:63:83 (a000a000
>e3cc8363).
>  The current PNIC-II WOL address is 00:a0:cc:e3:63:83.
>   Internal autonegotiation state is 'Ability detect'.
>  Use '-a' or '-aa' to show device registers,
>      '-e' to show EEPROM contents, -ee for parsed contents,
>   or '-m' or '-mm' to show MII management registers.
>
>--------
>What is wrong, is that no eth1 interface was created. Looking in
>/var/log/messages on boot
>we see the problem
>
>May 20 11:21:08 localhost kernel: tulip.c:v0.89H 5/23/98
>becker@cesdis.gsfc.nasa
>.gov
>May 20 11:21:08 localhost kernel: eth0: Digital DS21140 Tulip at 0xc000,
>00 00 e
>8 4e 5f 09, IRQ 9.
>May 20 11:21:08 localhost kernel: eth0:  MII transceiver found at MDIO
>address 1
>, config 1000 status 782d.
>May 20 11:21:08 localhost kernel:   PCI latency timer (CFLT) is 0x20,
>PCI comma
>nd is 0017.
>May 20 11:21:08 localhost kernel: Unknown Tulip-style PCI ethernet chip
>type 11a
>d c115 detected: not configured.
>
>-----------------
>So is this just a problem of old tulip driver, or I don't load the
>module properly
>(I tried to load manually with no effect - eth1 does not appear ) ?
>I read somewhere that there can be the problem with 2 tulip cards that
>the second
>is not recognized and you have to  supply i/o address to modprobe option
>explicitly.
>But I cannot find the reference.
>
>Now more specific questions: I tried to compile Donalds latest 0.92
>driver,  which is advertised
>to be compilable under every recent kernel but I'm getting
>#gcc -DMODULE -Wall -Wstrict-prototypes -O6 -c tulip.c
>tulip.c:161: pci-scan.h: No such file or directory
>tulip.c:162: kern_compat.h: No such file or directory
>
>I guess I'm missing some parts ?
>
>Attempt to compile tulip.c which comes on Lynksys floppy produce the
>whole stream of errors.
>Should it be possible to compile it with 2.2.5 kernel or probably just
>not ?
>
>                         Best regards, Dmitri Pogosyan
>
>
>
>_______________________________________________
>tulip mailing list
>tulip@scyld.com
>http://www.scyld.com/mailman/listinfo/tulip

Frédéric Cormier
cormierf@flashmail.com

Frédéric Cormier, alias Derf
derf@citeweb.net
ICQ:4735399
------------------------------------------------------
Quand je vois une grande personne sur une bicyclette,
j'ai confiance dans l'espèce humaine.
					H.G. Wells
------------------------------------------------------
http://derf.citeweb.net/