[YLUG] Grub

[mike cloaked]

On 11/12/2007, john halewood <john.halewood at gmail.com> wrote:

> Okay, the problem is nothing to do with the kernel then. This suggests
> that the problem you have is with initrd - the initial ramdisk that
> the kernel boots. When the kernel is initialising it, it's finding
> problems inside the ramdisk - i.e. it can't find the right drivers
> inside the ramdisk. This has been reported before (google for
> setuproot -xen). You bascially need to get a replacement initrd (or

I had not thought to check which kernel is installed but it might be
worth checking with:
ls /var/cache/yum/updates/packages/kern* (presuming that the yum cache
has not been cleared out).

and check that
a) it is not the xen kernel installed and
b) the kernel is for the correct architecture?

The output for one of my machines running F7 is:
/var/cache/yum/updates/packages/kernel-2.6.23.1-10.fc7.i686.rpm
/var/cache/yum/updates/packages/kernel-2.6.23.1-21.fc7.i686.rpm
/var/cache/yum/updates/packages/kernel-2.6.23.8-34.fc7.i686.rpm
/var/cache/yum/updates/packages/kernel-devel-2.6.23.1-10.fc7.i686.rpm
/var/cache/yum/updates/packages/kernel-devel-2.6.23.1-21.fc7.i686.rpm
/var/cache/yum/updates/packages/kernel-headers-2.6.23.1-10.fc7.i386.rpm
/var/cache/yum/updates/packages/kernel-headers-2.6.23.1-21.fc7.i386.rpm

It is possible to install both normal and xen kernels in F7 - and if
both are installed then the boot may default to the xen rather than
the normal kernel.
It is just possible that for some reason the update process to pull
new kernels has got an i586 rather than a i686 kernel - and this may
well cause a problem.  Either way it is worth checking.  Also I don't
know what the hardware is - what kind of laptop?

The other thing is that you can run mkinitrd to recreate initrd for
the new kernel that won't boot....

-- 
mike