From: "Thomas Molina" <tmolina@copper.net>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Kernel Panic while upgrading from 2.4.20 to 2.5.70
Date: Wed, 18 Jun 2003 17:48:03 -0400 [thread overview]
Message-ID: <MIECJFNNBOIGKGCCGDDECEANCBAA.tmolina@copper.net> (raw)
>Sourabh Ladha (EED) wrote:
>> Hi,
>>
>> [I know this has been discussed before but I tried the previous fixes
proposed without luck..so]
>>
>> I was trying to upgrade my kernel from 2.4.20 to 2.5.70. (I am running
RedHat 9). After getting the sources I did:
>>
>> make clean; make mrproper; make distclean; make menuconfig; make bzImage;
make modules; make modules_install; make install >(got past all of these)
>>
>> The make install updated my grub.conf as well...
>
>Just a wild guess: did you upgrade modutils to module-init-tools? 2.5.x
won't be happy
>until you do.
Actually, I have seen similar before. It happens when you install a new
kernel on a RedHat system which requires an initrd to boot. It happens
specifically because you upgrade module-init-tools. The upgraded
module-init-tools replaces files used by the previous version of the
utilities and creating links to them. It appears that the RedHat system
fails to find the proper version of the files it needs to build the initrd
image and therefor fails when it tries to load the ext3 modules. It then
can't find the init on the disk because it can't read the filesystem and
gives the error seen.
The two options are either build a kernel with everything required to boot
built in rather than modular, or else reinstll the old module tools, install
the new kernel (this allows RedHat to create a good initrd image), and then
reinstall the new module init tools.
next reply other threads:[~2003-06-18 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 21:48 Thomas Molina [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-18 13:23 Sourabh Ladha (EED)
[not found] <fa.o798dld.25grp5@ifi.uio.no>
2003-06-18 12:55 ` walt
2003-06-18 11:19 Sourabh Ladha (EED)
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=MIECJFNNBOIGKGCCGDDECEANCBAA.tmolina@copper.net \
--to=tmolina@copper.net \
--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
all inboxes | Powered by JetHome®