[eepro100] Problems with eepro100, RH6.2, Asus MES-N NLX

[Donald Becker]

On Sat, 30 Sep 2000, Dieter Jansen wrote:

> I have an Asus MES-N NLX based rack box that we recently needed
> to rebuild because it had been compromised.  For the rebuild we
...
> Since rebuilding the box I have been unable to get the onboard
> ethernet to work - the hub just doesn't "light up" for that port.
..
>   eepro100.c:v1.09j-t 9/29/99
>     Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
>   eepro100.c: $Revision: 1.18 $ 1999/12/29

This is one of many modified versions of the driver.
Not generating link beat isn't a usual problem, but we only test
Scyld-released drivers here.

You can try the updated driver at
  http://www.scyld.com/network/eepro100.html
    ftp://www.scyld.com/pub/network/eepro100.c
  http://www.scyld.com/network/updates.html

> I downloaded and compiled mii-diag and it says:
>   Using the default interface 'eth0'.
>   Basic registers of MII PHY #1:  3000 7809 02a8 0154 05e1 0000 0000 0000.
>    Basic mode control register 0x3000: Auto-negotiation enabled.
>    Basic mode status register 0x7809 ... 7809.
>      Link status: not established.

Hmmm, the transceiver is responding pretty much normally, but it doesn't see
link beat either.

> which looks bad ;-(    I also tried pci-config:
> 
>   pci-config.c:v2.01 7/4/2000
...
>   Device #6 at bus 0 device/function 3/0, 12298086.
...
> I got a little confused at this poin on which one to check, but
> assuming that the #1 in the mii-diag is meant to correspond to
> the pci-config parameter, a pci-config -# 1 gave me:

You need to run
    pci-config -#6

The important detail is if the interface is a powered-down state (D1 D2 or
D3 instead of D0).


Donald Becker				becker@scyld.com
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Generation Two Beowulf Clusters
Annapolis MD 21403