FW: FA310T Netgear revD1 NIC

Neale Banks neale@lowendale.com.au
Fri Jun 11 07:41:26 1999

On Tue, 8 Jun 1999 bart@vianet.net.au wrote:

> I having big problems with the FA310T Netgear revD1 NIC
> I'v use the Netgear changed driver, the 2.2.9 tulip.c, the 0.91 tulip.c and the
> 0.91e with no luck.
> This is what happens.
> I will try to ping a box on our network lets say the router, I will start the
> ping the pings will fail. If I run arp it says incomplete HW address. It seems
> to only fail if there is net activity on the box Im trying to ping even if its
> small say even 5-10k a sec, ping will fail to the box Im trying to ping untill
> the activity stops. I have no problem with other boxes with different NIC on the
> network. It is as if the arp are going missing!!

Yes, others here have this problem too {:-(  Some hosts work, some don't.
If you get past the arping stage then all is indeed fine, so far as I can

I'm not so sure taht it's related to network activity on the offending
host. In my case I'm on a subnet with two other hosts which are passing
traffic back and forth - one (linux) is mostly OK and the other (Cisco
25xx) is mostly not (although that observation is probably influenced by
the fact that the Cisco is the default gateway and so the tulip-host
typically tries to contact it first (and arp fails) whereas the first
contact is typically from the other linux host to the tulip-host (inbound
arp to tulip)).

> tulip-diag shows the card to be "Lite-On 82c168 PNIC rev 33" with the 0.91e
> tulip.c

/proc/pci shows mine to be a "Lite-on LNE100TX (rev 33)", v0.89 and v0.91
of the driver have this same problem.

> The Boxes run Redhat6.0, kernel 2.2.9, non-SMP, glibc2.1.

Debian 2.1 (slink) here, kernel 2.0.36 (with ipchains patch, FWIW)
compiled with gcc,  libc6