From: "Ingo T. Storm" <it@computerbild.de>
To: "Christian Loth" <chris@gidayu.max.uni-duisburg.de>,
<linux-kernel@vger.kernel.org>
Subject: Re: DHCP Problems with 3com 3c905C Tornado
Date: Thu, 4 Jan 2001 14:11:00 +0100 [thread overview]
Message-ID: <012101c0764f$c8b2f840$7400a8c0@dukat.cb.de> (raw)
> I recently installed a system with the 3c905C
>NIC on RedHat 6.2.
> The freshly installed RedHat 6.2 worked nice
>and flawlessly,
>However after upgrading
>to the 2.2.16 RedHat Kernel RPMS, the DHCP negotiation
>no longer worked!
>I downloaded 2.2.18 proper. I compiled in the support
>for the card, but also: same result.
Have you checked conf.modules that now is modules.conf?
In my case rh had just renamed/aliased the device and as soon as I had
adapted modules.conf accordingly, the card worked.
Of course, I might have completely misunderstood the problem, but it
sounds a lot like what I saw...
Cheers,
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-04 13:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 13:11 Ingo T. Storm [this message]
2001-01-04 13:23 ` DHCP Problems with 3com 3c905C Tornado Christian Loth
-- strict thread matches above, loose matches on Subject: below --
2001-01-04 11:31 Christian Loth
2001-01-04 12:41 ` Andrew Morton
2001-01-04 12:43 ` Christian Loth
2001-01-04 12:59 ` Andrew Morton
2001-01-04 13:19 ` Christian Loth
2001-01-04 16:01 ` Arjan van de Ven
2001-01-04 17:25 ` Christian Loth
2001-01-04 19:07 ` idalton
2001-01-07 13:42 ` Andrew Morton
2001-01-08 7:02 ` Tim Wright
2001-01-08 9:12 ` Andrew Morton
2001-01-08 9:13 ` David Ford
2001-01-08 11:56 ` Alan Cox
2001-01-08 12:53 ` Andrew Morton
2001-01-08 13:10 ` Christian Loth
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='012101c0764f$c8b2f840$7400a8c0@dukat.cb.de' \
--to=it@computerbild.de \
--cc=chris@gidayu.max.uni-duisburg.de \
--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.