[SGVLUG] resolved --> RH9, upgrading from 2.4.20-8 to 2.4.31 and initrd

[Robert Leyva]

Greets,

To my utter embarrassment, the real problem was that I hadn't copied the 
config2.4.20-8  from /boot to ".config" in my linux-2.4.31 directory 
before running "make oldconfig"

I then did the "mkinitrd initrd-2.4.31.img 2.4.31" the steps below, and 
it boots up just fine.

Me


****************
Greets,

Anyone know what modules I may need to manually add into the mkinitrd
command?

(I made my 2.4.31 kernel using "make oldconfig")

In "/boot" I do the default mkinitrd initrd-2.4.31.img 2.4.31 and get a
proper img file.

But during boot up I get a kernel panic about
...
VFS: cannot open root device "LABEL=/" or 00:00
please append a correct "root=" boot option
....

The thing is, I am using the same settings as the default entry in
/boot/grub.conf for 2.4.20-8.
The second entry starting with "title Red Hat Linux (2.4.31)" is what I
manually added.
...
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.20-8)
        root (hd0,0)
        kernel /vmlinuz-2.4.20-8 ro root=LABEL=/
        initrd /initrd-2.4.20-8.img
title Red Hat Linux (2.4.31)
        root (hd0,0)
        kernel /bzImage-2.4.31 ro root=LABEL=/
        initrd /initrd-2.4.31.img
....

I think I may need to specify a module to pass as an argument to
mkinitrd, but am not sure of which module(s) it needs.

(sigh) I didn't have this trouble with Debian, as sarge doesn't use initrd.

-- 
---
"Knowledge is Power." -- Francis Bacon

Robert Leyva
(Robert.Leyva at warnerbros.com)
Software Engineer
Warner Bros. Online