[eepro100] Set to 100bt-FD, but advertising 10bt-FD

[Ben Greear]

System: RH 7.1, kernel 2.4.5-pre3
NIC: EEPRO single port.

I've been poking and prodding some EEPRO cards...

In this case, I set the card to various fixed rates
and interspersed auto-negotiate in there too.  I was
setting the values with the mii-diag interface calls.

I seem to have gotten the eepro driver in a state of
confusion.  Part of it thinks it is fixed at 100bt-FD, but
it is advertising 10bt-FD as if it's still trying to
auto-negotiate.  The IBM switch sees it as negotiated to 10bt-FD.

Unplugging & re-plugging the cable did not fix the problem, although
then the IBM switch saw the EEpro as negotiated to 100bt-HD.  Setting
the EEpro back to auto didn't fix it either, untill I also specified that
it should advertise 10/100 Half/Full duplex.  Before I told it what to
advertise again, it was advertising 10bt-FD (but the IBM didn't/couldn't
establish link).

If the mii-diag output doesn't offer enough clues, please let me
know what you need to help resolve this.

Here is the mii-diag output:

[lanforge@lf1 lanforge]$ mii-diag -vvf eth2
mii-diag.c:v2.00 4/19/2000  Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
 MII PHY #1 transceiver registers:
   2100 780b 2000 5c00 0041 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 8462
   8000 0021 0000 3800 a3b9 0080 9305 001d.
 Basic mode control register 0x2100: Auto-negotiation disabled, with
 Speed fixed at 100 mbps, full-duplex.
 Basic mode status register 0x780b ... 780b.
   Link status: not established.
   This transceiver is capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation not complete.
   *** Link Jabber! ***
 Link partner information information is not exchanged when in fixed speed mode.
 MII PHY #1 transceiver registers:
   2100 780b 2000 5c00 0041 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 0000
   0000 0000 0000 0000 0000 0000 0000 8462
   8000 0021 0000 3800 a3b9 0080 9305 001d.
 Basic mode control register 0x2100: Auto-negotiation disabled!
   Speed fixed at 100 mbps, full-duplex.
 Basic mode status register 0x780b ... 780b.
   Link status: not established.
   Capable of  100baseTx-FD 100baseTx 10baseT-FD 10baseT.
   Able to perform Auto-negotiation, negotiation not complete.
   *** Link Jabber! ***
 Vendor ID is 08:00:17:--:--:--, model 0 rev. 0.
   No specific information is known about this transceiver type.
 I'm advertising 0041: 10baseT-FD
   Advertising no additional info pages.
   IEEE 802.3 CSMA/CD protocol.
 Link partner capability is 0000:.
   Negotiation did not complete.


Here is the boot msg from dmesg:

eepro100.c:v1.09j-t 9/29/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
PCI: Found IRQ 9 for device 00:13.0
eth1: Intel Corporation 82557 [Ethernet Pro 100], 00:A0:C9:77:9D:D9, IRQ 9.
  Receiver lock-up bug exists -- enabling work-around.
  Board assembly 678400-001, Physical connectors present: RJ45
  Primary interface chip i82555 PHY #1.
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (0x49caa8d6).
  Receiver lock-up workaround activated.

-- 
Ben Greear <greearb@candelatech.com>          <Ben_Greear@excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear