From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Adam <adam@vbfx.com>,
linux-kernel@vger.kernel.org,
"Michael K. Johnson" <johnsonm@redhat.com>
Subject: Re: dhcp problem with realtek 8139 clone with rh 7.1
Date: Fri, 04 May 2001 13:20:49 -0400 [thread overview]
Message-ID: <3AF2E4F1.6C5BE7FC@mandrakesoft.com> (raw)
In-Reply-To: <E14vj1d-0007es-00@the-village.bc.nu>
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 ?
I would say if Monday comes by without hearing from me, yes. It fixes
some people, breaks others :/
I've already got a fix on the dhcp breakage -- need to lock and unlock
EEprom before setting certain registers, and I am working on the other
problem (symptom: 'partner ability 0000' even when a link is present).
--
Jeff Garzik | Game called on account of naked chick
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-05-04 17:21 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 [this message]
2001-05-05 15:29 ` Rogier Wolff
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=3AF2E4F1.6C5BE7FC@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=adam@vbfx.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.