From: J Brook <jbk@postmark.net>
To: linux-kernel@vger.kernel.org
Cc: jgarzik@mandrakesoft.com
Subject: Re: Current tulip driver from 2.4.5 is plain broken
Date: Tue, 29 May 2001 01:11:52 +0000 [thread overview]
Message-ID: <20010529011152.9622.qmail@venus.postmark.net> (raw)
Michal Jaegermann wrote:
> I mentioned that before but this should be stated clearly. As far
> as I am concerned "Linux Tulip driver version 0.9.15-pre2 (May 16,
> 2001)", as used in 2.4.5 - and other kernels - is totally buggered.
> It comes up, and ethernet interfaces can be configured, but does
> not matter how I am playing with options I cannot get a single
> packet through.
>
> Replacing it in 2.4.5 with "Linux Tulip driver version 0.9.14d
> (April 3, 2001)", which I have handy, restores sanity immediately
> and a network simply works without any heroic efforts.
>
> My NIC is "Digital DS21143 Tulip rev 65 at 0x8800". BTW - a
> version "tulip-1.1.7" from sourceforge behaves exactly like
> 0.9.15-pre2.
I see exactly the same (broken!) behaviour here. The last kernel
that
works for me in 2.4.4-ac6, which I'm running at the moment. All
subsequent -ac kernels and 2.4.5-pre4 and above are broken. I
reported
the bug last week. Quick system summary: RH7.1, Duron, KT133, Network
card chip "Digital 21041-AA". I get the same problem as above
(working
kernels set half-duplex, broken kernels set full-duplex). More
details
available on request, or at
http://boudicca.tux.org/hypermail/linux-kernel/2001week21/0278.html
Thanks!
John
----------------
jbk@postmark.net
next reply other threads:[~2001-05-29 2:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 1:11 J Brook [this message]
2001-05-29 2:57 ` Current tulip driver from 2.4.5 is plain broken Terry Shull
-- strict thread matches above, loose matches on Subject: below --
2001-05-28 23:16 Michal Jaegermann
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=20010529011152.9622.qmail@venus.postmark.net \
--to=jbk@postmark.net \
--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