public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chmouel Boudjnah <chmouel@mandrakesoft.com>
To: Garett Spencley <gspen@home.com>
Cc: Michael F Gordon <Michael.Gordon@ee.ed.ac.uk>,
	<linux-kernel@vger.kernel.org>
Subject: Re: 2.4.4 breaks dhcpcd with Realtek 8139
Date: 01 May 2001 01:16:15 +0100	[thread overview]
Message-ID: <m3hez52ab4.fsf@giants.mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0104281142520.3423-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.30.0104281142520.3423-100000@localhost.localdomain> (Garett Spencley's message of "Sat, 28 Apr 2001 11:44:58 -0400 (EDT)")

Garett Spencley <gspen@home.com> writes:

> On Sat, 28 Apr 2001, Michael F Gordon wrote:
> 
> > dhcpcd stops working if I install 2.4.4.  Replacing the 2.4.4 version of
> > 8139too.c with the 2.4.3 version and leaving everything else exactly
> > the same gets things working again.  Configuring the interface by hand
> > after dhcpcd has timed out also works.  Has anyone else seen this?
> 
> I noticed this in 2.4.3-acX series as well. But here's the funny part:
> When dhcp starts up during bootup it doesn't work. But as
> soon as I log in and do a su -c '/etc/rc.d/init.d/network restart' there's
> instant success!
> 
> This is on Mandrake 8.0
> 
> It doesn't make much sense to me.

you may want to report the bug at :

https://qa.mandrakesoft.com/

  parent reply	other threads:[~2001-04-30 23:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-28 15:30 2.4.4 breaks dhcpcd with Realtek 8139 Michael F Gordon
2001-04-28 15:44 ` Garett Spencley
2001-04-28 18:29   ` David Lang
2001-04-28 22:11     ` Michael F Gordon
2001-04-29 11:04       ` Ingo Oeser
2001-04-29 15:46         ` Garett Spencley
2001-05-01  0:16   ` Chmouel Boudjnah [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-28 15:46 André Cruz

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=m3hez52ab4.fsf@giants.mandrakesoft.com \
    --to=chmouel@mandrakesoft.com \
    --cc=Michael.Gordon@ee.ed.ac.uk \
    --cc=gspen@home.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