From: Arjan van de Ven <arjanv@redhat.com>
To: neel vanan <neelvanan@yahoo.com>
Cc: William Lee Irwin III <wli@holomorphy.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel panic.. in 3.0 Enterprise Linux
Date: Mon, 05 Jan 2004 13:24:38 +0100 [thread overview]
Message-ID: <1073305477.4429.0.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20040105115610.49148.qmail@web9505.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 676 bytes --]
On Mon, 2004-01-05 at 12:56, neel vanan wrote:
> Hi all,
>
> The kernel I have working is version 2.4.21-4.EL and I
> can still boot up to that. I compiled a 2.6.0 version
> and installed it in exactly the same way that the old
> version is, just appending 2.6.0 to the end of the
> file. so when I reboot I get a boot screen that shows:
>
> Red Hat Enterprise Linux AS (2.4.21-4.ELsmp)
> Red Hat Enterprise Linux As-up (2.4.21-4.EL)
> Red Hat linux (2.6.0)
RHEL3 isn't quite 2.6 ready btw; you need to update quite a few packages
to get it working right.
Also if you use mount-by-label you do need to create an initrd (with a
2.6 capable mkinitrd)...
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-05 12:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S263478AbTLEJ0s/20031205092648Z+878@vger.kernel.org>
2003-12-05 9:34 ` Kernel panic neel vanan
2003-12-05 14:19 ` William Lee Irwin III
2003-12-06 5:47 ` William Lee Irwin III
2003-12-13 11:57 ` acpi related error neel vanan
2003-12-13 12:03 ` William Lee Irwin III
2004-01-05 11:56 ` Kernel panic.. in 3.0 Enterprise Linux neel vanan
2004-01-05 12:08 ` Christophe Saout
2004-01-05 12:23 ` Rik van Riel
2004-01-05 12:33 ` Christophe Saout
2004-01-05 12:21 ` Andreas Unterkircher
2004-01-05 12:24 ` Arjan van de Ven [this message]
2004-01-05 12:43 ` Kresimir Sparavec
2004-01-06 21:18 ` Lukas Postupa
2004-01-07 7:56 ` 2.6.0 works with 3.0 Enterprise Linux or not neel vanan
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=1073305477.4429.0.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neelvanan@yahoo.com \
--cc=wli@holomorphy.com \
/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;
as well as URLs for NNTP newsgroup(s).