Re: 2.5 kernels and shrike RPMs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
======
# 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



My panic was similar. Usually, on a manual partitioning, I choose /boot as /dev/hda1 -- / as /dev/hda2 -- /home as /dev/hda3 and swap as /dev/hda4.

With my automatic partitioning from a server class installation. It chose /dev/hda3 as / and /dev/hda2 was /home.

Unless you don't have a /boot partition (all / with boot in a directory), it is probably another partition. It is looking for the partition mounted as /. Running mount, without any arguments should display where / is mounted. About two of the three kernel arguments. The 66 pin cable (idebus=66) and the pci=biosirq, they are probably needed also.

How did you get an intird image? I boot without one. I've never created one for any kernels. If you have the intird image, you might be able to use basically what the other entries are. If my memory serves me right, someone mentioned that the intird image is where the LABEL=/ information is stored.

Jim




[Index of Archives]     [Fedora Users]     [Centos Users]     [Kernel Development]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Red Hat Phoebe Beta]     [Yosemite Forum]     [Fedora Discussion]     [Gimp]     [Stuff]     [Yosemite News]

  Powered by Linux