From: Russell Senior <seniorr@aracnet.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>, linux-kernel@vger.kernel.org
Subject: tulip: no link beat, media switching to 10Base2
Date: 09 May 2001 20:58:45 -0700 [thread overview]
Message-ID: <86wv7p7t3e.fsf_-_@coulee.tdb.com> (raw)
In-Reply-To: Jeff Garzik's message of "Wed, 09 May 2001 08:48:34 -0400"
[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.
--
Russell Senior ``The two chiefs turned to each other.
seniorr@aracnet.com Bellison uncorked a flood of horrible
profanity, which, translated meant, `This is
extremely unusual.' ''
reply other threads:[~2001-05-10 13:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86wv7p7t3e.fsf_-_@coulee.tdb.com \
--to=seniorr@aracnet.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®