[eepro100] Dell PowerEdge 1550 dual port NIC problem

[Paul English]

On Tue, 28 Jan 2003, Donald Becker wrote:

> On Tue, 28 Jan 2003, Paul English wrote:
> 
> > I'm having trouble getting a link on a a Dell Powered 1550 with 
> > dual port Intel nics. I've tried the intel e100 driver that comes with 
> > Suse (8.0) as well as the Scyld eepro100 driver. Using mii-diag I've 
> > forced the duplex and speed to various settings, but no matter what I do 
> > I'm not getting link. 
> ...
> > 	Below are the outputs of eepro100-diag and mii-diag:
> > eepro100-diag -a
> > eepro100-diag.c:v2.11 8/27/2002 Donald Becker (becker@scyld.com)
> >  http://www.scyld.com/diag/index.html
> > Index #1: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xecc0.
> >  * A recognized chip has been found, but it does not appear to exist in
> >  * I/O space.  Use the '-f' flag to see the register values anyway.
> 
> This is bad.  Your device is broken or powered down.
> You can get some indication with 'lspci'.

Interestingly enough lspci seems to report both of them okay:
00:01.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 
08)
00:02.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 
08)

On further investigation, it looks like both of the NICs will report the 
above error to eepro100-diag if they've been activated. I had not set the 
second one to be activated on boot, but if I ifconfig it up, (then back 
down again because eepro100-diag complains if it is up) it reports that 
error also. 

> > Index #2: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xec80.
> > i82557 chip registers at 0xec80:
> >   00000000 00000000 00000000 00080002 10000000 00000000
> 
> Try '-m' to see if the transceiver is responding.

Here it is with -m:
eepro100-diag.c:v2.11 8/27/2002 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xecc0.
 * A recognized chip has been found, but it does not appear to exist in
 * I/O space.  Use the '-f' flag to see the register values anyway.
Index #2: Found a Intel i82557/8/9 EtherExpressPro100 adapter at 0xec80.
i82557 chip registers at 0xec80:
  00000000 00000000 00000000 00080002 183f0000 00000000
  No interrupt sources are pending.
   The transmit unit state is 'Idle'.
   The receive unit state is 'Idle'.
  This status is unusual for an activated interface.
Primary transceiver is MII PHY #1. MII PHY #1 transceiver registers:
   3000 7809 02a8 0154 05e1 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 0000 0001 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000.

> > mii-diag eth0
> > Basic registers of MII PHY #1:  1000 7809 02a8 0154 0081 0000 0000 0000.
> >  Basic mode control register 0x1000: Auto-negotiation enabled.
> >  Basic mode status register 0x7809 ... 7809.
> >    Link status: not established.
> >    End of basic transceiver information.
> > mii-diag eth1
> > Basic registers of MII PHY #1:  2000 7809 02a8 0154 05e1 0000 0000 0000.
> >  Basic mode control register 0x2000: Auto-negotiation disabled, with
> >  Speed fixed at 100 mbps, half-duplex.
> 
> Is this setting what you intended?
> 
> Try hard-power-off (unplug), and see what the 'mii-diag' reports without
> forcing the speed.

No, that wasn't what I intended - it must have been a leftover from my 
earlier fiddling. Here it is after the power down:
mii-diag 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.
   End of basic transceiver information.

mii-diag eth1
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.
   End of basic transceiver information.

Paul