[tulip] Linksys card recognition?

David Shochat shochat@acm.org
Mon, 28 Aug 2000 18:51:58 -0400


I have the same card you have. It is working fine and my /proc/pci shows
pretty much exactly the same thing as yours for it:

  Bus  1, device  10, function  0:
    Ethernet controller: Unknown vendor Unknown device (rev 17).
      Vendor id=1317. Device id=985.
      Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master
Capable.  Latency=64.  Min Gnt=255.Max Lat=255.
      I/O at 0xd800 [0xd801].
      Non-prefetchable 32 bit memory at 0xff8ff800 [0xff8ff800].

Note that LNE100TX is just the card model number, not the chip.
According to what I see in my syslog from boot:

Aug 28 17:58:45 h kernel: tulip.c:v0.92 4/17/2000  Written by Donald
Becker <becker@scyld.com> 
Aug 28 17:58:45 h kernel:   http://www.scyld.com/network/tulip.html 
Aug 28 17:58:45 h kernel: eth1: ADMtek Comet rev 17 at 0xc805e800,
00:20:78:18:08:26, IRQ 11. 

I would say the driver thinks the chip is ADMtek Comet.

"David R. Kohel" wrote:
> 
> Hi,
> 
> I just obtained a Linksys LNE100TX card; no eth0 line appear in the
> boot sequence.  I find that the entry in /proc/pci is
> 
>   Bus  0, device  14, function  0:
>     Ethernet controller: Unknown vendor Unknown device (rev 17).
>       Vendor id=1317. Device id=985.
>       Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master
>       Capable.  Latency=32.  Min Gnt=255.Max Lat=255.
>       I/O at 0xe000 [0xe001].
>       Non-prefetchable 32 bit memory at 0xd5810000 [0xd5810000].
> 
> That is, it doesn't appear to pick up the chip LNE100TX or any other
> identifier.  Thereafter 'insmod tulip.o' gives an error message saying
> that the device is busy.
> 
> This is my first time to use a PCI card; any advice on forcing the
> card to be recognized would be greatly appreciated.  I'm running
> a Debian system with kernel 2.2.15.
> 
> --David
> 
> _______________________________________________
> tulip mailing list
> tulip@scyld.com
> http://www.scyld.com/mailman/listinfo/tulip