Force mediatype with tulip
Hi folks,
I got a ethercard with a DECchip 21140. I am using kernel 2.4.8, tulip
driver 0.9.15-pre6 (July 2, 2001). As my linux-box is connected to a
10/100Mbps dual-speed hub/switch (namely D-Link DFE-905DX) and the "10M"
indicator is active, I want to force media-type to 100baseTx.
The driver is compiled into the kernel, so I used
append="ether=0,0,3,eth0" in /etc/lilo.conf (according to the
tulip-driver-documentation.
Well, actually this doesn't seem to work ... here my logs:
/var/log/dmesg:
Linux Tulip driver version 0.9.15-pre6 (July 2, 2001)
tulip0: EEPROM default media type Autosense.
tulip0: Index #0 - Media 10baseT (#0) described by a 21140 non-MII (0) block.
tulip0: Index #1 - Media 100baseTx (#3) described by a 21140 non-MII (0) block.tulip0: Index #2 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block.
tulip0: Index #3 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block.
eth0: Digital DS21140 Tulip rev 32 at 0x6200, 00:40:05:31:21:F9, IRQ 10.
ifconfig eth0:
eth0 Link encap:Ethernet HWaddr 00:40:05:31:21:F9
inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:443 errors:1 dropped:0 overruns:0 frame:0
TX packets:441 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:53785 (52.5 Kb) TX bytes:158340 (154.6 Kb)
Interrupt:10 Base address:0x6200
tulip-diag:
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 DS21140 Tulip adapter at 0x6200.
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.
Use '-a' or '-aa' to show device registers,
'-e' to show EEPROM contents, -ee for parsed contents,
or '-m' or '-mm' to show MII management registers.
Thanks for any hints!
--
"are you punk rock, are you strung out or are you just crazy?"
----> http://experimental.tammen.net
Reply to: