[tulip] RE: tulip Digest, Vol 1, Issue 717

Wed Jun 9 03:55:06 PDT 2004

Hi,

 "No MII Transceiver" is OK in your case since your card (according to
the eeprom) was implemented using the built-in serial and SYM PHYs
For 10 and 100MBps respectively, and not with MII.

A problem that can be noticed is that your Tulip TX and RX machines are
stopped. Also notice that CSR6 value is 0xb3860000 
Which means that your TX and RX machines were not activated after the
stop.
This condition (if no error exists, at least CSR 5 does not report one)
may be due to the autosense algorithm 
switching to another port  without restarting the TX and RX machines
again.
(this action usually involves stopping the TX and TX machines, switching
to the new port and starting the machines again ).

Try to force you chip to 100mbps half duplex (I am sure there is a
keyword for that) and see what happens.

Moti

-----Original Message-----
From: tulip-bounces at scyld.com [mailto:tulip-bounces at scyld.com] On Behalf
Of tulip-request at scyld.com
Sent: Tuesday, June 08, 2004 9:04 PM
To: tulip at scyld.com
Subject: tulip Digest, Vol 1, Issue 717

Send tulip mailing list submissions to
	tulip at scyld.com

To subscribe or unsubscribe via the World Wide Web, visit
	http://www.scyld.com/mailman/listinfo/tulip
or, via email, send a message with subject or body 'help' to
	tulip-request at scyld.com

You can reach the person managing the list at
	tulip-owner at scyld.com

When replying, please edit your Subject line so it is more specific than
"Re: Contents of tulip digest..."

Today's Topics:

   1. MII Transceivers (Jim McCloskey)

----------------------------------------------------------------------

Message: 1
Date: Sun, 06 Jun 2004 17:50:36 -0700
From: Jim McCloskey <mcclosk at ucsc.edu>
Subject: [tulip] MII Transceivers
To: tulip at scyld.com
Message-ID: <E1BX8LU-0000DP-00 at toraigh>

The second network card in a machine I look after suddenly ceased to
work this afternoon.

tulip-diag identifies it this way:

   Index #1: Found a Digital DS21143 Tulip adapter at 0xdc00

and dmesg (linux kernel 2.4.23):

   Linux Tulip driver version 0.9.15-pre12 (Aug 9, 2002)
   PCI: Found IRQ 11 for device 00:0a.0
   tulip0:  EEPROM default media type Autosense.
   tulip0:  Index #0 - Media 10baseT (#0) described by a 21142 Serial
PHY (2) block.
   tulip0:  Index #1 - Media 10baseT-FDX (#4) described by a 21142
Serial PHY (2) block.
   tulip0:  Index #2 - Media 100baseTx (#3) described by a 21143 SYM PHY
(4) block.
   tulip0:  Index #3 - Media 100baseTx-FDX (#5) described by a 21143 SYM
PHY (4) block.
   eth1: Digital DS21143 Tulip rev 65 at 0xdc00, 00:40:F6:4C:01:22, IRQ
11.

Attempts to bring up the eth1 interface (at boot-time or manually)
produce:

   SIOCADDRT: Network is unreachable
   Failed to bring up eth1.

The tulip driver is loaded. I don't believe that anything has changed in
the configuration, so I turned to tulip-diag to try to diagnose the
problem.  The output from `tulip-diag -aem' is this:

   tulip-diag.c:v2.17 5/6/2003 Donald Becker (becker at scyld.com)
     http://www.scyld.com/diag/index.html
   Index #1: Found a Digital DS21143 Tulip adapter at 0xdc00.
   Digital DS21143 Tulip chip registers at 0xdc00:
   0x00: f8a08000 ffffffff ffffffff 0f724000 0f724200 f0000102 b3860000
f3fe0000
   0x40: e0000000 ffffcbf8 ffffffff 00000000 40a1d2cd ffff0001 fffbffff
8ffd0008
     Port selection is 100mbps-SYM/PCS 100baseTx scrambler, half-duplex.
   Transmit stopped, Receive stopped.
    The Rx process state is 'Stopped'.
    The Tx process state is 'Stopped'.
    The transmit threshold is 128.
    The NWay status register is 40a1d2cd.
      Link Partner ability: 40a1.
      100baseTx link good.
  EEPROM 64 words, 6 address bits.
  PCI Subsystem IDs, vendor 0000, device 0000.
  CardBus Information Structure at offset 00000000.
  Ethernet MAC Station Address 00:40:F6:4C:01:22.
  EEPROM transceiver/media description table.
  Leaf node at offset 30, default media type 0800 (Autosense).
   4 transceiver description blocks:
    Media 10baseT, block type 2, length 6.
     Serial transceiver for 10baseT (media type 0).
      GP pin direction 08af  GP pin data 00a5.
    Media 10baseT-Full Duplex, block type 2, length 6.
     Serial transceiver for 10baseT-Full Duplex (media type 4).
      GP pin direction 08af  GP pin data 00a5.
    Media 100baseTx, block type 4, length 8.
     SYM transceiver for 100baseTx (media type 3).
      GP pin direction 08af  GP pin data 00a5.
      No media detection indication (command 80 61).
    Media 100baseTx Full Duplex, block type 4, length 8.
     SYM transceiver for 100baseTx Full Duplex (media type 5).
      GP pin direction 08af  GP pin data 00a5.
      No media detection indication (command 80 61).
     No MII transceivers found!
    Internal autonegotiation state is 'Negotiation complete'.

I'm afraid that I don't know enough to make much of this though. Could
anyone tell me if this might be showing me the source of the problem: 
`No MII transceivers found!' for instance?

I'd be very grateful indeed for any advice or help,

                                                     Jim

PS the network configuration file (Debian's /etc/network/interfaces)
looks like this:

----------------------------------------------------------------------
auto lo
iface lo inet loopback

# The first network card:
#
auto eth0
iface eth0 inet static
address 64.142.49.200
network 64.142.49.0
netmask 255.255.255.0
broadcast 64.142.49.255
gateway 64.142.49.1

# The second network card
#
auto eth1
iface eth1 inet static
address 192.168.93.3
network 192.168.93.0
netmask 255.255.255.0
broadcast 192.168.93.255
gateway 64.142.49.1
----------------------------------------------------------------------

------------------------------

_______________________________________________
tulip mailing list
tulip at scyld.com
http://www.scyld.com/mailman/listinfo/tulip

End of tulip Digest, Vol 1, Issue 717
*************************************