Recompiling kernel and grub

[ne...]

On Jun 3, 2004 at 22:11, Juan L. Pastor in a soothing rage wrote:

>Hello all,
>
>I have recompiled my FC2 kernel (make xconfig, make bzImage, make
>modules, make modules_install), I copied the bzImage and System.map to
>the /boot directory and then updated the /etc/grub.conf file with the
>new entry (first one):
>
>default=0
>timeout=10
>splashimage=(hd2,0)/grub/splash.xpm.gz
>title Fedora Core (2.6.5-1.358)
>        root (hd2,0)kernel /bzImage ro root=/dev/hdc2 rhgb quiet
>        kernel /bzImage ro root=/dev/hdc2 rhgb quiet
>        initrd /initrd-2.6.5-1.358.img
>title Fedora Core (2.6.5-1.358) 02 Jun 06
>        root (hd2,0)
>        kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/ rhgb quiet
>        initrd /initrd-2.6.5-1.358.img
>title Windows
>        rootnoverify (hd0,0)
>        chainloader +1
>
>The second Fedora entry is working OK, but why if I change
>
>kernel /bzImage ro root=/dev/hdc2 rhgb quiet
>
>from the first entry to:
>
>kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/ rhgb quiet
>
>FC2 does not want to boot?
Cause you didn't configure your kernel the way the original
one was configured. You never created the proper initrd image
for the kernel you compiled. Instead of copying over the bzImage
and System.map to the /boot directory, why not do a make install
instead? This should set things up nicely for you including the
changes to /boot/grub/grub.conf.

N.Emile...
-- 
Registered Linux User # 125653 (http://counter.li.org)
Switch to: http://www.speakeasy.net/refer/190653
You know you've been spending too much time on the computer when your
friend misdates a check, and you suggest adding a "++" to fix it.
 16:22:30  up 20:18,  3 users,  load average: 0.00, 0.00, 0.00