[tulip] 21041<->cable modem, led dark, kernel > 2.4.18
Donald Becker
becker@scyld.com
Mon Aug 5 12:53:01 2002
On Mon, 5 Aug 2002, Florian wrote:
> redhat 7.3 uses 2 tulip versions in its kernel/sources. old works new
> not - without options.
What driver versions?
You should be using the driver at
http://www.scyld.com/network/tulip.html
ftp://www.scyld.com/pub/network/tulip.c
Niether tulip driver in the kernel is an unmodified release, and the
modified versions have been broken throughout the 2.4 kernel, most
notably with 21041 and 21143+SYM designs.
> tulip_old finds all the right settings which are:
>
> tulip-diag.c:v2.11 6/17/2002 Donald Becker (becker@scyld.com)
> http://www.scyld.com/diag/index.html
> Index #1: Found a Digital DC21041 Tulip adapter at 0xd000.
> Port selection is half-duplex.
> Transmit started, Receive started, half-duplex.
> The Rx process state is 'Waiting for packets'.
> The Tx process state is 'Idle'.
> The transmit unit is set to store-and-forward.
> The NWay status register is 000001c8.
What is your link partner?
> The NWay status register is 000050c8.
Autonegotation is complete, but there is no link partner code word.
> now with "insmod tulip options=4" and working:
Media type 4 should set 10baseT-FDX (serial, not MII).
> Port selection is full-duplex.
> Transmit started, Receive started, full-duplex.
...
> The NWay status register is 000001c8.
...
> the nway value is back to "000001c8"!
There is no autonegotation with a forced media type.
--
Donald Becker becker@scyld.com
Scyld Computing Corporation http://www.scyld.com
410 Severn Ave. Suite 210 Second Generation Beowulf Clusters
Annapolis MD 21403 410-990-9993