On Fri, 2003-06-06 at 23:44, Warren Togami wrote: > On Fri, 2003-06-06 at 11:30, Anthony Joseph Seward wrote: > > Comparing the versions of the RPMs that came with shrike, it seems like > > the only thing that is needed is to add mod-init-tools in order to use a > > 2.5 kernel. When I try and boot I get a kernel panic that complains > > that there is no init. I'm using the same root partition as with my > > stock RH kernels so I don't understand what could be the problem. Can > > anyone help? > > > > Tony > > ====== > > [root@xxxxxxxx root]# depmod -V > > module-init-tools 0.9.12 > > > For module-init-tools, it is far safer and easier to use modutils from > Rawhide which has module-init-tools integrated into the same > executable. Using upstream's module-init-tools breaks mkinitrd when > installing 2.4 kernels in the future. > > > ====== > > # grub.conf generated by anaconda > > # > > # Note that you do not have to rerun grub after making changes to this > > file > > # NOTICE: You do not have a /boot partition. This means that > > # all kernel and initrd paths are relative to /, eg. > > # root (hd0,0) > > # kernel /boot/vmlinuz-version ro root=/dev/hda1 > > # initrd /boot/initrd-version.img > > #boot=/dev/hda > > default=1 > > timeout=10 > > splashimage=(hd0,0)/boot/grub/splash.xpm.gz > > title 2.5.70 > > root (hd0,0) > > kernel /boot/vmlinuz-2.5.70 ro root=/dev/hda1 > > initrd /boot/initrd-2.5.70.img > > title Red Hat Linux (2.4.20-18.9) > > root (hd0,0) > > kernel /boot/vmlinuz-2.4.20-18.9 ro root=LABEL=/ idebus=66 > > hdc=ide-scsi pci=biosirq > > initrd /boot/initrd-2.4.20-18.9.img > > title Red Hat Linux (2.4.20-8) > > root (hd0,0) > > kernel /boot/vmlinuz-2.4.20-8 ro root=LABEL=/ idebus=66 > > hdc=ide-scsi pci=biosirq > > initrd /boot/initrd-2.4.20-8.img > > Probably the problem is your kernel is unable to read the LABEL of the > partition. The workaround would be to change "LABEL=/" to the actual > root filesystem device. > > Anyone know what kernel option needs to be activated so the kernel can > read LABEL from the partitions? >From the above gtub config, it seems he's *not* using device label for the 2.5 kernel (only for the 2.4 kernels). I think he's having problems with the initial ramdisk image. I suggest removing the initial ramdisk "initrd" from grub.conf and compile a monolithic kernel with all drivers and filesystems needed to boot from /dev/hda1, and leave the rest as modules. I'm doing that way and don't have problems.
