From: R.E.Wolff@BitWizard.nl (Rogier Wolff)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Adam <adam@vbfx.com>,
linux-kernel@vger.kernel.org,
"Michael K. Johnson"@cave.bitwizard.nl, johnsonm@redhat.com,
jgarzik@mandrakesoft.com
Subject: Re: dhcp problem with realtek 8139 clone with rh 7.1
Date: Sat, 5 May 2001 17:29:47 +0200 (MEST) [thread overview]
Message-ID: <200105051529.RAA16274@cave.bitwizard.nl> (raw)
In-Reply-To: <E14vj1d-0007es-00@the-village.bc.nu> from Alan Cox at "May 4, 2001 06:05:51 pm"
Alan Cox wrote:
> > I've had the same problem with the 8139too drivers and DHCP. The reason
> > I figure it must be the drivers is because in the 2.4.3 kernel, I'm able
> > to use the 8139too drivers with DHCP without any problems. In 2.4.4 it
> > locks my system.
> Multiple such reports - seems the 8139too update broke stuf - any
> ideas Jeff, should I revert to the 2.4.3 one ?
Ack!
I have two diskless systems that with 2.4.4 end up with VERY slow
network interfaces. I then do a
cp ../linux-2.4.2.clean/drivers/net/8139too.c drivers/net
and rebuild. Fixes my problems....
Jeff, my offer of acess to a box that has this problem still stands.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
* There are old pilots, and there are bold pilots.
* There are also old, bald pilots.
next prev parent reply other threads:[~2001-05-05 15:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-04 15:20 dhcp problem with realtek 8139 clone with rh 7.1 Michael K. Johnson
2001-05-04 16:26 ` Adam
2001-05-04 17:05 ` Alan Cox
2001-05-04 17:20 ` Jeff Garzik
2001-05-05 15:29 ` Rogier Wolff [this message]
2001-05-04 16:35 ` Enrico Scholz
-- strict thread matches above, loose matches on Subject: below --
2001-05-05 22:14 Greg
2001-05-04 8:33 Rasmus Gunnar
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=200105051529.RAA16274@cave.bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc="Michael K. Johnson"@cave.bitwizard.nl \
--cc=adam@vbfx.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=johnsonm@redhat.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