[tulip] No MII transceiver found

Donald Becker becker@scyld.com
Tue Dec 3 15:43:00 2002


On 3 Dec 2002, Jarl Friis wrote:
> Hi, just downloaded netdrivers-3.3, system is otherwise SuSE 8.1
> 
> I can't get my NetGear FA510 PCMCIA to work, I have tried the tulip dirver
> with debug=2 and among other things I get 
> Dec  3 19:26:59 hermes kernel: eth0: ***WARNING***: No MII transceiver found!
> 
> Can somwone help? Or can I do something to improve the driver...

What does
  tulip-diag -eee -m -a
report?

[[ I need to see the reset and transceiver activation sequences.  I'll
likely use those to add code to tulip-diag that tests the activation. ]]

What are the PCI IDs (including subsystem) of the card?

[[ Those will be necessary to conditionalize any fix. ]]

> Following is the log for the commands insmod ..., ifconfig ... up,
> ping, ifconfig ... down, rmmod:
> 
> Dec  3 19:26:59 hermes kernel: tulip.c:v0.95f 11/17/2002  Written by Donald Becker <becker@scyld.com>
> Dec  3 19:26:59 hermes kernel:   http://www.scyld.com/network/tulip.html
> Dec  3 19:26:59 hermes kernel: eth0: Digital DS21143-xD Tulip rev 65 at 0xd49a9000, 00:10:7A:15:F6:3E, IRQ 10.

A previous problem was the driver assming that a specific ID a 21143,
when the chip was actually the ADMtek Comet.  The chips are similar, but
have different EEPROM formats, transceiver selection, Rx filter, and
transceiver connections.

The "rev 65" makes me believe that this is really a 211143.

> Dec  3 19:26:59 hermes kernel: eth0:  EEPROM default media type Autosense.
> Dec  3 19:26:59 hermes kernel: eth0:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
> Dec  3 19:26:59 hermes kernel: eth0: ***WARNING***: No MII transceiver found!

-- 
Donald Becker				becker@scyld.com
Scyld Computing Corporation		http://www.scyld.com
410 Severn Ave. Suite 210		Scyld Beowulf cluster system
Annapolis MD 21403			410-990-9993