[tulip] Netgear FA310-TX NIC problems

[A.J. Rossini]

On Mon, 10 Jul 2000, Donald Becker wrote:

> I'm asking because the "FA310TX" name refers to three or four different
> chips and transceiver configurations.

I'll open it up tonight when I get back from work.

> If it's easy to look at the board itself, what is the brand and part number
> of the transceiver?  (Probably unimportant, but I'll see if I can add it to
> libmii.c).

Again, will do tonight.  Does this mean you don't need it, or still do? 

> Ahhh, rev. 32, definitely a '169 with the fixed MII register hardware.

> I'll need the output from 'tulip-diag -af'.  It's easiest to do
>   tulip-diag -af  > /tmp/t-d-working

Here it is:

tulip-diag.c:v2.00 4/19/2000 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a Lite-On 82c168 PNIC adapter at 0xde00.
Lite-On 82c168 PNIC chip registers at 0xde00:
  00008000 01ff0000 00450008 0ba3b000 0ba3b200 02660010 814c20c2 0001ebef
  00000000 00000000 0ba3b230 07dbae0c 00000025 00000000 00000000 10000001
  00000000 00000000 f0041385 000000bf 6086782d 0ba3b0b0 0bb70010 0201f878
  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
 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 72.

>   tulip-diag -af  > /tmp/t-d-broken

and here:

tulip-diag.c:v2.00 4/19/2000 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a Lite-On 82c168 PNIC adapter at 0xde00.
Lite-On 82c168 PNIC chip registers at 0xde00:
  00008000 01ff0000 01000608 0ba3b000 0ba3b200 02260010 814c20c2 0001ebef
  00000000 00000000 0ba3b2d0 0ba3b2d0 00000025 00000000 00000000 10000001
  00000000 00000000 f0041385 000000bf 6086782d 0ba3b1c0 07767010 0201f878
  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
 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 'Waiting for Tx to finish'.
  The transmit threshold is 72.

And to be annoying pedantic, I'm seeing this error flash every 30 seconds
or so (maybe less):

	eth0: Transmit timeout using MII device.

I'm running Debian, so I reset it using 
	/etc/init.d/networking restart
and all is fine.

best,
-tony