LinkSys EtherFast 10/100 LAN Card

Donald Becker
Thu Nov 5 16:11:37 1998

On Thu, 5 Nov 1998, David Rose wrote:

> Donald Becker writes:
> > This code is invoked when the interrupt line is constantly set.
> > 
> > It indicates that some other device is raising an interrupt.  There is not
> > way to clear it unless you know what that device is.
> Perhaps it's worthwhile to keep this old code in the driver--with a
> diagnostic warning about conflicting IRQ's--if only to alert the
> occasional foolish user like me?

I deleted the check because it could potentially be triggered by normal
interrupt sharing.  The only way to reliably detect this problem is in the
code that handles the interrupt controller, not in individual drivers.

> I do still get this:
> eth0: The transmitter stopped!  CSR5 is 2678016, CSR6 816e2002.
> shortly after initialization; should I be concerned?

This is normal with the PNIC. IIFC, it happens when the PNIC processes the
first configuration frame.  The driver just has to restart the chip.
It should never happen with the Tulip.
Turn down your debug level so you don't have to see this message.

> 2.1.123.  Here's what /proc/pci has to say about the card:
>   Bus  0, device  15, function  0:
>     Ethernet controller: LiteOn LNE100TX (rev 32).

Hmmm, try making the following change on line 77 of tulip-diag.c
-  { "Lite-On LNE100Tx", "Lite-On 82c168 PNIC",
+  { "Lite-On LNE100TX", "Lite-On 82c168 PNIC",

Donald Becker
USRA-CESDIS, Center of Excellence in Space Data and Information Sciences.
Code 930.5, Goddard Space Flight Center,  Greenbelt, MD.  20771