From: "Johan Kullstam" <kullstam@ne.mediaone.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Tulip problem in Kernel 2.4.11
Date: 11 Oct 2001 07:38:46 -0400 [thread overview]
Message-ID: <m2adyy5ruh.fsf@euler.axel.nom> (raw)
In-Reply-To: <000701c151c4$0e6933e0$0300a8c0@theburbs.com> <87u1x6zmdy.fsf@penny.ik5pvx.ampr.org>
In-Reply-To: <87u1x6zmdy.fsf@penny.ik5pvx.ampr.org>
Pierfrancesco Caci <ik5pvx@penny.ik5pvx.ampr.org> writes:
> :-> "Jamie" == Jamie <darkshad@home.com> writes:
>
> > Hello there is a definate problem with the tulip drivers in the 2.4.11
> > kernel.
> > I have a DEC DC 21041 NIC which uses the tulip drivers. I use the 2.2.19
> > kernel and there are
> > two different sets of tulip drivers listed in that kernel which
> > I can choose
> > from in the 2.4.11 kernel there is only one. When I do a
> > modprobe tulip the
> > driver loads fine as you can see bellow there are no strange
> > error messages
> > ect. But I can not communicate though this one NIC. When I use
> > the 2.2.19
> > Kernel it works fine.
>
> I can add to this that 2.4.2 works fine, I've tried 2.4.9 and 2.4.11
> and I can't use the lan either.
> In 2.4.11, I can see that the driver can sense if I plug/unplug the
> connector (10BaseT, connected to a Compaq Netelligent 8 port hub), but
> nothing more.
linux 2.4.11 is broken with respect to tulip driver and dec 21041
chipset. my 21041 card doesn't work either. what you can do is the
following. compile kernel using a module for tulip driver. go to
tulip.sourceforge.net. get tulip-0.9.14. unpack it. for each new
kernel, manually (or make a script) compile a tulip driver in
tulip-0.9.14 and install it in
/lib/module/2.4.X/kernel/drivers/net/tulip. this will replace the
broken driver and keep you going.
--
J o h a n K u l l s t a m
[kullstam@mediaone.net]
next prev parent reply other threads:[~2001-10-11 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 19:45 Tulip problem in Kernel 2.4.11 Jamie
2001-10-11 7:06 ` Pierfrancesco Caci
2001-10-11 11:38 ` Johan Kullstam [this message]
2001-10-11 12:26 ` Pierfrancesco Caci
2001-10-11 13:50 ` Fabbione
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=m2adyy5ruh.fsf@euler.axel.nom \
--to=kullstam@ne.mediaone.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