[YLUG] Grub

mike cloaked mike.cloaked at gmail.com
Tue Dec 11 08:57:45 GMT 2007


On 11/12/2007, mike cloaked <mike.cloaked at gmail.com> wrote:

> 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....

Another approach may be to presume that the install of the new kernel
did not work for some reason. I presume that the yum repo files are
set to have gpgcheck=1 which will verify packages before they are
installed from the repos, and then you could boot to the working
kernel and do:
yum remove kernel-2.6.23.8-34.fc7 (I can't remember exactly which
kernel was problematic)

and once the latest kernel is removed then
yum install kernel-2.6.23.8-34.fc7
or simply yum install kernel
During the install the new initrd will be created. Then try booting to
the new kernel.

-- 
mike



More information about the York mailing list