NetGear FA310TX on a 486 MB

[Louis Novak]

Donald Becker wrote:

> 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.

The board is labelled SP3-G50-1, The user manual refers to PCI/I-486SP3, and I
think the G goes
on the end so, SP3G .?... anyways:

[root@fairone tulip]#  /sbin/insmod tulip debug=7 options=5,16 csr0=0x01A04800
./tulip.o: init_module: Device or resource busy

Is that how I'm supposed to pass in the option?

    ... deleted ...

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

ummmm, how would I determine that?

   ... deleted ...

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

[root@fairone tulip]#  tulip-diag -p 0x6000 -f -e -e -a -m -m -t 5
tulip-diag.c:v1.10 4/12/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)
Lite-On 82c168 PNIC chip registers at 0x6000:
  00000000 01ff0000 00000000 00000000 00000000 02001102 01440040 00000000
  00000000 00000000 00000000 00000000 0000002d 00000000 00000000 10000000
  00000000 00000000 f0041385 000000bf 60960000 00000000 00000000 0201f878
  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
 Port selection is MII, 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.
EEPROM contents:
  00a0 cc3a ef49 f004 1385 00f1 0000 e514
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
  0000 0000 0000 0000 0000 0000 0000 0000
 ID CRC 0x34 (vs. 00), complete CRC 43f43593.
 A simplifed EEPROM data table was found.
 The EEPROM does not contain transceiver control information.
 MII PHY found at address 1, status 0x7809.
 MII PHY #1 transceiver registers:
   1000 7809 7810 0000 01e1 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 0000 4000 0000 0009 0010 0000 0002
   0001 0000 0000 0000 0000 0000 0000 0000.
 Basic mode control register 0x1000: Auto-negotiation enabled.
 Basic mode status register 0x7809 ... 7809.
   Link status: not established.
   Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation not complete.
 Vendor ID is 1e:04:00:--:--:--, model 0 rev. 0.
   Vendor/Part: Level One LXT970.
 I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 0000:.
   Negotiation did not complete.


> 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

[root@fairone tulip]# pci-config
pci-config.c:v1.04 2/19/99 Donald Becker (becker@cesdis.gsfc.nasa.gov)

This didn't seem to affect the results of loading the driver or tulip-diag.

--
Louis Novak                |  Suffering from pronoia, the sneaking feeling
www.msen.com/~lnovak       |  that someone is conspiring behind my back
lmn@wwnet.com              |  to help me. How can I help you?