[tulip] Cpq Presario problems

Olof Oberg mill@pedgr571.sn.umu.se
Thu, 13 Sep 2001 13:34:42 +0200


Hi, 

I have been having problems getting the builtin NIC 
on my Compaq Presario to work properly since I got 
it (June), but the last week has been unbearable with 
network downtime several times a day.

Currently used kernel that came with the distribution:
Linux version 2.2.18 (root@fritz) (gcc version 2.95.2 20000220 (Debian 
GNU/Linux)) #1 Tue Feb 27 10:33:03 EST 2001
...
tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov
eth0: Digital DS21143 Tulip rev 65 at 0x1400, 00:08:C7:63:8E:D8, IRQ 11.
eth0:  EEPROM default media type Autosense.
eth0:  Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block.
eth0:  Index #1 - Media 10baseT-FD (#4) described by a 21142 Serial PHY (2) 
block.

The kernel starts spewing: 

eth0: Tx hung, 2163 vs. 2162.
eth0: 21140 transmit timed out, status f0260000, SIA 000000c6 ffff0000 
fff8ffff 8ff40000, resetting...
eth0: transmit timed out, switching to 10baseT-FD media.
eth0: Tx hung, 2174 vs. 2162.
eth0: 21140 transmit timed out, status f0260000, SIA 000000c6 ffff0000 
fff8ffff 8ff40000, resetting...
eth0: transmit timed out, switching to 10baseT-FD media.

...


I have tried kernel 2.2.18, 2.2.19, 2.4.8, and 2.4.9 
with the tulip driver from 2.4.4 (saw it mentioned 
somewhere that it might work better).

I have put up the output from dmesg and tulip-diag at 
http://www.ludd.luth.se/~mill/tulip/ for the last week 
or so.

This is what tulip-diag -aa -ee -mm -f said this last time:

tulip-diag.c:v2.08 5/15/2001 Donald Becker (becker@scyld.com)
 http://www.scyld.com/diag/index.html
Index #1: Found a Digital DS21143 Tulip adapter at 0x1400.
Digital DS21143 Tulip chip registers at 0x1400:
 0x00: f8a08000 ffffffff ffffffff 0009d810 0009da10 f0260000 b3862002 fbfffbff
 0x40: e0000000 fff583ff ffffffff 00000000 000000c6 ffff0000 fffbff7f 8ff50008
 Port selection is 100mbps-SYM/PCS 100baseTx scrambler, 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 64 words, 6 address bits.
PCI Subsystem IDs, vendor 0e11, device b0bb.
CardBus Information Structure at offset 00000000.
Ethernet MAC Station Address 00:08:C7:63:8E:D8.
EEPROM transceiver/media description table.
Leaf node at offset 30, default media type 0800 (Autosense).
 2 transceiver description blocks:
  Media 10baseT, block type 2, length 6.
   Serial transceiver for 10baseT (media type 0).
    GP pin direction 08e1  GP pin data 0000.
  Media 10baseT-Full Duplex, block type 2, length 6.
   Serial transceiver for 10baseT-Full Duplex (media type 4).
    GP pin direction 08e1  GP pin data 0000.
EEPROM contents (64 words):
0x00:  0e11 b0bb 0000 0000 0000 0000 0000 0000
0x08:  183f 0104 0800 63c7 d88e 1e00 0000 0800
0x10:  8602 0002 08e1 0000 0286 e104 0008 0000
0x18:  0000 0000 0000 0000 0000 0000 0000 0000
0x20:  0000 0000 0000 0000 0000 0000 0000 0000
0x28:  0000 0000 0000 0000 0000 0000 0000 0000
0x30:  0000 0000 0000 0000 0000 0000 0000 0000
0x38:  0000 0000 0000 0000 0000 0000 0000 ce45
 ID block CRC 0x3f (vs. 0x3f).
  Full contents CRC 0xce45 (read as 0xce45).
   No MII transceivers found!
  Internal autonegotiation state is 'Autonegotiation disabled'.

I have tried to unload-load the module, but after that 
the network is unreachable so I always have to reboot.

Any help would be greatly appreciated. I have tried 
to use my D-Link DFE-530TX and 3COM 509, but neither 
is detected (the 3COM has served me since '95 in 
my old box).

 /mill

-- 
#############################################################
# S-mail: Olof Oberg     #  mill@pedgr571.sn.umu.se         #
#         Pedagoggr. 7A  #  mill@ludd.luth.se               #
#         S-907 30 Umea  #  tdv94oog@cs.umu.se              #
# Phone:  090-197395     #  http://pedgr571.sn.umu.se/~mill #
#############################################################