On 3/21/07, Brad Bonkoski <bbonkoski@xxxxxxxxxxxxxx> wrote:
Looks like this command: ln -f -s vmlinuz-2.6.18-build-1 /boot/vmlinuz-2.6 linked your new kernel build to vmlinuz-2.6 (Do you have this in your /boot ?) So, in grub, you would use that instead of the xen.gz-2.6.18-1.2798.fc6
My grub.conf now looks like this : # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd1,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd1,0)/grub/splash.xpm.gz hiddenmenu title WinXP rootnoverify (hd0,0) chainloader +1 title Fedora Core (2.6.18-1.2798.fc6xen) root (hd1,0) kernel /xen.gz-2.6.18-1.2798.fc6 module /vmlinuz-2.6.18-1.2798.fc6xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet module /initrd-2.6.18-1.2798.fc6xen.img title Fedora Core (2.6.18-build-1) root (hd1,0) kernel /vmlinuz-2.6 module /vmlinuz-2.6.18-build-1 ro root=/dev/VolGroup00/LogVol00 rhgb quiet with Fedora Core (2.6.18-build-1) being the newly built kernel.However , selecting that kernel at boot time , resulted in a failed boot , with an error message saying : "Error 13:Invalid or unsupported executable format Press any key to continue....." The GRUB docs explain this error as : "This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD)." How can my built kernel be not supported?This was suppose to be any easy exercise, $make mrproper ;make xconfig;make;make modules_install install and 'make install' was suppose to do the magic of copying my new kernel to the right place , update grub.conf ...
