NetGear FA310TX on a 486 MB

Donald Becker becker@cesdis1.gsfc.nasa.gov
Wed Apr 28 19:32:38 1999


On Wed, 28 Apr 1999, Louis Novak wrote:

> I'm trying to get a Netgear FA310TX 10/100 working on my ASUS
> PCI/I-486SPSG motherboard.

Do you mean "SPG3", with the Intel chipset?
If so you'll have to pass the module option "csr0=0x01A04800" to avoid a PCI
burst bug that may cause problems.

> [root@fairone lmn]#  /sbin/insmod tulip debug=7 options=5,16
> /lib/modules/2.0.36/net/tulip.o: init_module: Device or resource busy

Hmmm, this means that it can't find the card.
Has some other driver registered that I/O space?

> static const char version[] = "tulip.c:v0.91 4/14/99

Thanks for reporting the version.

> Output of tulip-diag, cat /proc/pci and cat /proc/interrupts are below

> [root@fairone tulip]#  tulip-diag -p 0x6000 -f -e -e -a -m -m
> tulip-diag.c:v1.10 4/12/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
> Digital Tulip, unknown type chip registers at 0x6000:
>   00000000 01ff0000 00000000 00000000 00000000 02001102 01440040 00000000
>   00000000 00001385 00000000 00000000 0000002d 00000000 00000000 10000000

Try using '-t 5' (or '-t -1' to see your options).

> [root@fairone lmn]# cat /proc/pci
> PCI devices found:
>   Bus  0, device  21, function  0:
>     Ethernet controller: Unknown vendor LNE100TX (rev 33).
>       Medium devsel.  Fast back-to-back capable.  IRQ 14.  Master...
>       I/O at 0x6000.

Grrr, this was what was broken about /proc/pci -- I can't tell what the PCI
Vendor ID and Device ID values are.  We must know those before I can tell if
the detection table in the driver is correct.  You might have to run
  ftp://cesdis.gsfc.nasa.gov/pub/linux/diag/pci-config.c

Donald Becker					  becker@cesdis.gsfc.nasa.gov
USRA-CESDIS, Center of Excellence in Space Data and Information Sciences.
Code 930.5, Goddard Space Flight Center,  Greenbelt, MD.  20771
301-286-0882	     http://cesdis.gsfc.nasa.gov/people/becker/whoiam.html