[tulip] No MII transceiver found

Sun Dec 8 06:09:00 2002

Hi.

I have now tried the PCMCIA tulip card on IRQ 10, but this still does
not work.

Donald Becker <becker@scyld.com> writes on the RealTek list:

> On 7 Dec 2002, Jarl Friis wrote:
> > > IRQ 9, the driver is using the same IRQ as reported in /proc/pci.
> > So that is as it should be, right?
> 
> Yes, if that IRQ works...
> 
> > > Do CardBus cards work?
> > 
> > I have only tried with the FA510 (DECchip) which, as you know does not
> > work completely, but I guess that is for another reason. It seems like the
> > CardBus system itself does work in general.
> 
> I suspect that the Tulip problem is related to this one.

It may be, but it is still unsolved.

While pinging the log file gives

Dec  8 11:22:09 hermes kernel: tulip.c:v0.95f 11/17/2002  Written by Donald Becker <becker@scyld.com>
Dec  8 11:22:09 hermes kernel:   http://www.scyld.com/network/tulip.html
Dec  8 11:22:09 hermes kernel: eth1: Digital DS21143-xD Tulip rev 65 at 0xd49ad000, 00:10:7A:15:F6:3E, IRQ 10.
Dec  8 11:22:09 hermes kernel: eth1:  EEPROM default media type Autosense.
Dec  8 11:22:09 hermes kernel: eth1:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
Dec  8 11:22:09 hermes kernel: eth1: ***WARNING***: No MII transceiver found!
Dec  8 11:22:13 hermes kernel: Trying to free nonexistent resource <d49ad000-d49ad07f>
Dec  8 11:22:22 hermes kernel: tulip.c:v0.95f 11/17/2002  Written by Donald Becker <becker@scyld.com>
Dec  8 11:22:22 hermes kernel:   http://www.scyld.com/network/tulip.html
Dec  8 11:22:22 hermes kernel: eth1: Digital DS21143-xD Tulip rev 65 at 0xd49aa000, 00:10:7A:15:F6:3E, IRQ 10.
Dec  8 11:22:22 hermes kernel: eth1:  EEPROM default media type Autosense.
Dec  8 11:22:22 hermes kernel: eth1:  Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block.
Dec  8 11:22:22 hermes kernel: eth1:  MII transceiver #1 config 1000 status 786d advertising 01e1.
Dec  8 11:23:00 hermes kernel: eth1: no IPv6 routers present
Dec  8 11:23:52 hermes kernel: eth1: Tx hung, 17 vs. 14.
Dec  8 11:24:52 hermes kernel: eth1: Tx hung, 34 vs. 23.
Dec  8 11:25:52 hermes kernel: eth1: Tx hung, 45 vs. 34.
Dec  8 11:26:52 hermes kernel: eth1: Tx hung, 56 vs. 45.
Dec  8 11:27:52 hermes kernel: eth1: Tx hung, 67 vs. 56.
Dec  8 11:28:52 hermes kernel: eth1: Tx hung, 73 vs. 67.
Dec  8 11:30:52 hermes kernel: eth1: Tx hung, 84 vs. 73.

Notice that sometimes loading the module gives
***WARNING***: No MII transceiver found!

The tulip-diag -eee -m -a gives

tulip-diag.c:v2.15 9/23/2002 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DS21143 Tulip adapter at 0x4000.
 * A potential Tulip chip has been found, but it appears to be active.
 * Either shutdown the network, or use the '-f' flag to see all values.
Digital DS21143 Tulip chip registers at 0x4000:
 0x00: f8a08000 ffffffff ffffffff 05024000 05024200 f0678047 b20e2002 fbfffbff
 Port selection is MII, half-duplex.
 Transmit started, Receive started.
  The Rx process state is 'Waiting for packets'.
  The Tx process state is 'Idle'.
  The transmit threshold is 128.
 Interrupt sources are pending!  CSR5 is f0678047.
   Tx done indication.
   Tx complete indication.
   Tx out of buffers indication.
   Rx Done indication.
  The NWay status register is 000000c6.

Note that these outputs was while the RealTek was up (with kernel
8139too driver) and running on eth0.

Jarl