From: Tom Rini <trini@kernel.crashing.org>
To: Jeff Garzik <jgarzik@mandrakesoft.com>, linux-kernel@vger.kernel.org
Subject: Broken tulip in 2.4.5+
Date: Sat, 30 Jun 2001 18:21:10 -0700 [thread overview]
Message-ID: <20010630182110.A1144@opus.bloom.county> (raw)
Hello. The current tulip driver in 2.4.5 and up no longer works with my
'tulip' ethernet card. 0.9.14 (what's in prior to 2.4.5-pre6, iirc) works
fine with the card, as does de4x5. Version 0.9.15-pre5 (2.4.6-pre8) and
1.1.8 (from sourceforge) both don't work. The card is:
01:15.0 Ethernet controller: Digital Equipment Corporation DECchip 21140 [FasterNet] (rev 22)
Flags: bus master, medium devsel, latency 96, IRQ 58
I/O ports at 0400 [size=128]
Memory at 80080000 (32-bit, non-prefetchable) [size=128]
Expansion ROM at <unassigned> [disabled] [size=256K]
The error(s) are as follows, for both 0.9.15-pre5 and 1.1.8:
Linux Tulip driver version 0.9.15-pre5 (June 16, 2001)
tulip0: EEPROM default media type 10baseT.
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.
tulip0: MII transceiver #1 config 1000 status 782d advertising 05e1.
eth1: Digital DS21140 Tulip rev 34 at 0xd2118000, 00:00:94:A3:FA:0D, IRQ 58.
eth1: Using EEPROM-set media 10baseT.
eth1: Setting full-duplex based on MII#1 link partner capability of 41e1.
NETDEV WATCHDOG: eth1: transmit timed out
eth1: 21140 transmit timed out, status fc680000, SIA ffffff0b ffffffff 1c09fdc0 fffffec8, resetting.
..
eth1: transmit timed out, switching to 100baseTx-FDX media.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
next reply other threads:[~2001-07-01 1:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-01 1:21 Tom Rini [this message]
2001-07-01 10:42 ` Pasi Kärkkäinen
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=20010630182110.A1144@opus.bloom.county \
--to=trini@kernel.crashing.org \
--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®