[tulip] Extremely stubborn 21143
Jon.Hinks
Jon.Hinks@berkeley-ifa.co.uk
Wed, 18 Oct 2000 12:18:01 +0100
Thanks for responding. I was in the middle of typing up a reply on one
machine and getting all the req'd info on another- when suddenly it started
working! As per your suggestion, I did `mii-diag -r` at the command line-
didn't even need to take the network down. Now pings to and from the box are
fine. Many thanks for this. So, what have I done here? One thing I notice is
that these commands need to be issued every time after powering up. What is
the 'permanent' solution? Can this be done without mii-diag?
Thanks again for your assistance. I have included the original response I
was working on before I had any joy, in case it helps answer my secondary
questions above.
Kind regards
Jon (Hinks)
I.T. Department
Berkeley Independent Advisers Ltd
Direct line (024) 7623 2041
[Long legal statement omitted here. Maybe I should tell a joke, or recall a
faintly amusing quotation instead]
-------------------------------------------------------
** My response was going to be: **
> What version are you using?
I downloaded pci-scan and tulip yesterday from scyld.com. These successfully
compiled, the .o files were placed in the /lib/modules/<version>/net/
directory and a `depmod -a` executed to make the dependency tree happy.
Version numbers here are taken from the source code:
pci-scan.c:v1.01 5/8/2000
tulip.c:v0.92 4/17/2000
> Was the interface up or down when this was run?
> (See the 'ifconfig eth0' output.)
Hmm, now that you mention it, I'm not sure. I have therefore included one at
the end of this thread together with an `ifconfig eth0` output.
> The 'mii-diag' program would have reported
> all of these problems.
A 'mii-diag -v' report was in my original posting; I have included another
together with the `tulip-diag -e` output at the end of this msg.
> What type of hardware do you have?
> It sounds like an early not-quite-right prototype board.
Well, I'm using my current board after giving up with a 3com 3c905 card-
although if anyone thinks that this is a more reliable card/more likely
card, then I'll give it another go. My current card is labelled thus:
Digital 21143-PA
21-44085-10
(c) DEC 1996
DC 1053B
A9640 L52948-04
-----------
It is I believe, a CNET, although is not obviously branded on the card. This
is, however, reported as part of the MAC addr on our server when the box in
running in Windows mode.
It may also help if I mention the following:
* If I do a `ifdown eth0`, the network is taken down. If, then, I do `ifup
eth0`, I get an error of "SIOCADDRT: File exists"
* After booting up to runlevel 3, I get a message periodically which says
something about timeouts. This is 'cos I set the debug level to 6 in
/etc/conf.modules
* I have removed all other cards from my machine to reduce chance of
conflicts
----------------------------------------------------
>> `ifconfig eth0` produces:
eth0 Link encap:Ethernet HWaddr 00:80:AD:B6:5A:86
inet addr:120.121.122.1 Bcast:120.121.122.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:187 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:11 Base address:0x5c00
---------------------------
`>> tulip-diag -e` produces:
tulip-diag.c:v2.04 9/26/2000 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a Digital DS21143 Tulip adapter at 0xf880.
Port selection is MII, half-duplex.
Transmit started, Receive started, half-duplex.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Waiting for Tx to finish'.
The transmit threshold is 128.
The NWay status register is 000000c6.
EEPROM size is 6.
PCI Subsystem IDs, vendor 0000, device 0000.
CardBus Information Structure at offset 00000000.
Ethernet MAC Station Address 00:80:AD:B6:5A:86.
EEPROM transceiver/media description for the Digital DS21143 Tulip chip.
Leaf node at offset 30, default media type 0800 (Autosense).
3 transceiver description blocks:
Media 10baseT, block type 2, length 12.
Serial transceiver for 10baseT (media type 64).
CSR13 ec01 CSR14 7f3f CSR15 0008.
GP pin direction 08ab GP pin data 0001.
Media 10baseT-Full Duplex, block type 2, length 12.
Serial transceiver for 10baseT-Full Duplex (media type 68).
CSR13 ec01 CSR14 7f3d CSR15 0008.
GP pin direction 08ab GP pin data 0001.
Media MII, block type 3, length 17.
MII interface PHY 0 (media type 11).
21143 MII initialization sequence is 2 words: 08ab 0001.
21143 MII reset sequence is 0 words:.
Media capabilities are 6000, advertising 01e1.
Full-duplex map 5000, Threshold map 0180.
No MII interrupt.
MII PHY found at address 0, status 0x782d.
MII PHY #0 transceiver registers:
3400 782d ffff ffff 01e1 0081 0000 ffff
ffff ffff ffff ffff ffff ffff ffff ffff
ffff ffff ffff ffff ffff ffff ffff ffff
ffff ffff ffff ffff ffff ffff ffff c200.
Internal autonegotiation state is 'Autonegotiation disabled'.
---------------------------
>> `tulip-diag -m` produces:
tulip-diag.c:v2.04 9/26/2000 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a Digital DS21143 Tulip adapter at 0xf880.
Port selection is MII, half-duplex.
Transmit started, Receive started, half-duplex.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Waiting for Tx to finish'.
The transmit threshold is 128.
The NWay status register is 000000c6.
MII PHY found at address 0, status 0x782d.
MII PHY #0 transceiver registers:
3400 782d ffff ffff 01e1 0081 0000 ffff
ffff ffff ffff ffff ffff ffff ffff ffff
ffff ffff ffff ffff ffff ffff ffff ffff
ffff ffff ffff ffff ffff ffff ffff c200.
Internal autonegotiation state is 'Autonegotiation disabled'.
---------------------------
>> ` mii-diag -v` produces:
mii-diag.c:v2.00 4/19/2000 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
MII PHY #0 transceiver registers:
3400 782d ffff ffff 01e1 0081 0000 ffff
ffff ffff ffff ffff ffff ffff ffff ffff
ffff ffff ffff ffff ffff ffff ffff ffff
ffff ffff ffff ffff ffff ffff ffff c200.
Basic mode control register 0x3400: Auto-negotiation enabled.
Transceiver isolated from the MII!
You have link beat, and everything is working OK.
This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD
10baseT.
Able to perform Auto-negotiation, negotiation complete.
Your link partner is generating 100baseTx link beat (no autonegotiation).
MII PHY #0 transceiver registers:
3400 782d ffff ffff 01e1 0081 0000 ffff
ffff ffff ffff ffff ffff ffff ffff ffff
ffff ffff ffff ffff ffff ffff ffff ffff
ffff ffff ffff ffff ffff ffff ffff c200.
Basic mode control register 0x3400: Auto-negotiation enabled.
Transceiver isolated from the MII!
Basic mode status register 0x782d ... 782d.
Link status: established.
Capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
Able to perform Auto-negotiation, negotiation complete.
This transceiver has no vendor identification.
I'm advertising 01e1: 100baseTx-FD 100baseTx 10baseT-FD 10baseT
Advertising no additional info pages.
IEEE 802.3 CSMA/CD protocol.
Link partner capability is 0081: 100baseTx.
Negotiation did not complete.