[tulip] Problem with Linksys EtherFast 10/100 Cardbus PC Card

Garion garion@garion.mnbsyr.com
Fri Mar 29 11:52:01 2002

Hello.. I seem to have a problem with my card, and wondering if someone here 
could help.. 

It seems that I can only get 10Mbit.. I have verified the cable as perfect, 
and that the port on my switch (Matrox Shark) is fine.

At first I thought it might be the laptop, as its fairly old (P166, 48 Megs).. 
But then I started looking into the possiblity that it could be the driver.. 
So I upgraded to tulip 0.93.. Same issue.. Then I started running the various 
diag programs..

The card is a Linksys EtherFast 10/100 Cardbus PC Card, PCMPC200..  cardctl 
reports it as:

Socket 0:
  no product info available
Socket 1:
  product info: "Linksys", "EtherFast 10/100 CardBus PC Card(PCMPC200)", 
"V1.0", ""
  manfid: 0x0149, 0x0231
  function: 6 (network)
  PCI id: 0x1011, 0x0019

tulip-diag.c:v2.10 3/08/2002 Donald Becker (becker@scyld.com)
Index #1: Found a Digital DS21143 Tulip adapter at 0x100.
 Port selection is MII, full-duplex.
 Transmit started, Receive started, full-duplex.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit threshold is 128.
  The NWay status register is 000000c6.
  Internal autonegotiation state is 'Autonegotiation disabled'.
 Use '-a' or '-aa' to show device registers,
     '-e' to show EEPROM contents, -ee for parsed contents,
  or '-m' or '-mm' to show MII management registers.

mii-diag: (this is the suspicious one):
Basic registers of MII PHY #0:  0000 0000 0000 0000 0000 0000 0000 0000.
 Basic mode control register 0x0000: Auto-negotiation disabled, with
 Speed fixed at 10 mbps, half-duplex.
 Basic mode status register 0x0000 ... 0000.
   Link status: not established.
 Link partner information is not exchanged when in fixed speed mode.
   End of basic transceiver information.

For some reason, my speed is fixed at 10Mb... Not to mention, with everything 
at 0's, it looks bad, and no auto-negotiation.

I am not sending any options to the module. I have tried sending options=13 
and options=14, full_duplex=1, and so forth, but no changes in speed or teh 
results of mii-diag... 

This card did sit around for several months without use, and the battery in 
the laptop had died, could the mii rom (or whatever) have died? Is there a 
way to fix this?