From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Linux 2.4.32] SATA ICH5/PIIX and Combined mode
Date: Wed, 21 Dec 2005 22:42:02 -0600 [thread overview]
Message-ID: <43AA2E9A.1080007@shaw.ca> (raw)
In-Reply-To: <5maE0-21N-1@gated-at.bofh.it>
Paul Rolland wrote:
> Well, the other way around is to upgrade e1000 driver in the 2.4.21EL-smp,
> as the machine I'm using is quite new, and RHES3 kernel can't find the
> Ethernet device, so the machine has no network.
> My first idea was to consider this as an opportunity to upgrade to the
> latest 2.4.x kernel, but reading you, this looks like a bad idea...
> 2.6.x would be better ?
First make sure you have the latest RHEL3 errata kernel installed. If
that still doesn't work, you could install the latest e1000 driver
module from Intel.
Later vanilla 2.4 kernels are not necessarily an "upgrade" from Red Hat
kernels based on older 2.4 versions as you lose all the Red Hat patches
like NPTL and the O(1) scheduler.
If you are going to go to a 2.6 kernel you might as well just go to a
newer distribution.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2005-12-22 4:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5maE0-21N-3@gated-at.bofh.it>
[not found] ` <5maE0-21N-1@gated-at.bofh.it>
2005-12-22 4:42 ` Robert Hancock [this message]
[not found] <5mKo7-1sD-5@gated-at.bofh.it>
[not found] ` <5nFPq-1ZT-25@gated-at.bofh.it>
2005-12-27 2:38 ` [Linux 2.4.32] SATA ICH5/PIIX and Combined mode Robert Hancock
2005-12-21 11:10 Paul Rolland
2005-12-21 11:18 ` Jeff Garzik
2005-12-21 11:28 ` Paul Rolland
2005-12-21 11:34 ` Arjan van de Ven
2005-12-21 11:40 ` Paul Rolland
2005-12-23 1:57 ` Adrian Bunk
2005-12-23 2:16 ` Jeff Garzik
2005-12-25 15:17 ` Paul Rolland
2005-12-25 15:16 ` Paul Rolland
2005-12-23 7:45 ` Jesse Brandeburg
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=43AA2E9A.1080007@shaw.ca \
--to=hancockr@shaw.ca \
--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