From: J Brook <jbk@postmark.net>
To: linux-kernel@vger.kernel.org
Subject: tulip driver BROKEN in 2.4.5-pre4
Date: Mon, 21 May 2001 01:37:05 +0000 [thread overview]
Message-ID: <20010521013705.4079.qmail@venus.postmark.net> (raw)
Okay, so Jeff Garzik already knows about this - I told him last week -
but seeing as how the code has made it to a Linus pre-release without
a fix I thought I'd better post the breakage description to l-k!
The symptoms are:
In 2.4.5-pre4 (and 2.4.4-ac8 and above - note: I didn't try -ac7)
system boots up normally, card is recognised etc, but all networking
services fail because it's not possible to talk to the network. The
system appears to be stable apart from the bug (possible to compile
kernels, run X, etc.), but nothing gets to or from the network.
I'm using the "DECchip Tulip (dc21x4x) PCI support" option to get the
driver for the PCI card which has a Digital 21041 chip in it.
FWIW I think it might be related to the selection of full- or
half-duplex. 2.4.4-ac6 (which works fine) says:
Port selection is half-duplex
when I run tulip-diag, whereas 2.4.5-pre4 says
Port selection is full-duplex
My system is RH7.1 (using gcc-2.96 not kgcc)
Duron 750, KT133 chipset (not kt133a!)
Network card details (it is a PCI):
Kingston KNE40BT (1995)
Digital 21041-AA DC1017BA
21-40756-01 Dec 1994
S15313-02
A 9615
More details on request. And I'm willing to test patches...
John
----------------
jbk@postmark.net
next reply other threads:[~2001-05-21 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 1:37 J Brook [this message]
2001-05-23 21:39 ` tulip driver BROKEN in 2.4.5-pre4 Lukasz Trabinski
-- strict thread matches above, loose matches on Subject: below --
2001-05-21 9:54 Studierende der Universitaet des Saarlandes
2001-05-24 2:24 ` Johan Kullstam
2001-05-21 11:50 J Brook
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=20010521013705.4079.qmail@venus.postmark.net \
--to=jbk@postmark.net \
--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