tulip: no link beat, media switching to 10Base2
[a repost of a message sent to the tulip bugtracking system on sourceforge]
I am using the tulip driver from vanilla linux-2.4.4, and when I disconnect the rj45 from the card I get the following message:
eth1: No 21041 10baseT link beat, Media switched to 10base2.
... and it never switches back (until I ifdown/ifup the interface, which is mighty inconvenient when I am off-site, which is usually).
Here are the bootup messages in 2.4.4:
[...]
Linux Tulip driver version 0.9.14e (April 20, 2001)
tulip0: 21041 Media table, default media 0800 (Autosense).
tulip0: 21041 media #0, 10baseT.
tulip0: 21041 media #4, 10baseT-FDX.
tulip0: 21041 media #1, 10base2.
eth0: Digital DC21041 Tulip rev 17 at 0xf880, 21041 mode, 00:00:C0:D4:74:D6, IRQ 5.
tulip1: 21041 Media table, default media 0800 (Autosense).
tulip1: 21041 media #0, 10baseT.
tulip1: 21041 media #4, 10baseT-FDX.
tulip1: 21041 media #1, 10base2.
eth1: Digital DC21041 Tulip rev 17 at 0xf800, 21041 mode, 00:00:C0:6A:7F:D5, IRQ 11. [...]
There are two identical(-ish) cards in the machine (it is acting as a router), both the same brand anyway (SMC EtherPower PCI). I was able to hack in 10BaseT stability in a previous kernel (2.4.1) using TULIP_DEFAULT_MEDIA and TULIP_NO_MEDIA_SWITCH, but I noticed in the ChangeLog for 2.4.4 that these features were removed. How do I get reliable 10BaseT operation inspite of possible cabling disconnections.
Signature · 4 lines
Russell Senior ``The two chiefs turned to each other. [email protected] Bellison uncorked a flood of horrible profanity, which, translated meant, `This is extremely unusual.' ''