I mentioned that before but this should be stated clearly. As far as I
am concerned "Linux Tulip driver version 0.9.15-pre2 (May 16, 2001)",
as used in 2.4.5 - and other kernels - is totally buggered. It comes up,
and ethernet interfaces can be configured, but does not matter how I am
playing with options I cannot get a single packet through.
Replacing it in 2.4.5 with "Linux Tulip driver version 0.9.14d (April 3,
2001)", which I have handy, restores sanity immediately and a network
simply works without any heroic efforts.
My NIC is "Digital DS21143 Tulip rev 65 at 0x8800". BTW - a version
"tulip-1.1.7" from sourceforge behaves exactly like 0.9.15-pre2.
This is an output of 'tulip-diag -af' from a working setup:
tulip-diag.c:v2.06 1/8/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a Digital DS21143 Tulip adapter at 0x8800.
Digital DS21143 Tulip chip registers at 0x8800:
0x00: f8a0e000 ffffffff ffffffff 0d572000 0d572200 f0660000 b2422002 fbfffbff
0x40: e0000000 fff583ff ffffffff 00000000 000052ca ffff0001 fffbffff 8ffd0008
Port selection is 10mpbs-serial, half-duplex.
Transmit started, Receive started, half-duplex.
The Rx process state is 'Waiting for packets'.
The Tx process state is 'Idle'.
The transmit threshold is 72.
The NWay status register is 000052ca.
Internal autonegotiation state is 'Negotiation complete'.
And this what shows up when I am trying to use "the-new-and-improved":
tulip-diag.c:v2.06 1/8/2001 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a Digital DS21143 Tulip adapter at 0x8800.
Digital DS21143 Tulip chip registers at 0x8800:
0x00: f8a0d000 ffffffff ffffffff 0b9f4000 0b9f4200 f0000000 b2420200 fbfffbff
0x40: e0000000 fff483ff ffffffff 00000000 000060ca ffff0001 fffbffff 8ffd0000
Port selection is 10mpbs-serial, full-duplex.
Transmit stopped, Receive stopped, full-duplex.
The Rx process state is 'Stopped'.
The Tx process state is 'Stopped'.
The transmit threshold is 72.
The NWay status register is 000060ca.
Internal autonegotiation state is 'Link check'.
Comments?
Michal
michal@harddata.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu May 31 2001 - 21:00:38 EST