ubuntu-users Digest, Vol 51, Issue 185

[Leonard Chatagnier]

--- On Thu, 11/13/08, Bill Taylor <th1bill at sbcglobal.net> wrote:

> From: Bill Taylor <th1bill at sbcglobal.net>
> Subject: Re: ubuntu-users Digest, Vol 51, Issue 185
> To: ubuntu-users at lists.ubuntu.com
> Date: Thursday, November 13, 2008, 8:55 AM
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I'm a compete noob, and even I know all he has to do
> now is edit the
> menu.lst file to add the new kernel to one of the boot
> options. I had
> the same thing happen to me when Hardy updated it's
> kernel but didn't
> update grub to point at the new one.
> 
> gksu gedit & will open your editor in administrative
> mode so you can
> open and edit the menu.lst file.
> 
> Later, Ray Parrish
> - ---------------------------------------------
> 
> Ray, I tried that but I must not have typed the correct
> syntax.  If I
> knew exactly what form to type the new kernel into the
> menu.lst I would
> attempt that once more but I do not wish to kill the system
> entirely.
>
Sorry if I've missed something as I've not followed this thread closely.  However, you should only have to do:

sudo update-grub to add any missing kernels that has been installed correctly on the version you are running. My output of the command includes all the kernels installed on Hardy as below:

lchata at ubuntu-hardy-64bit:~$ sudo update-grub
[sudo] password for lchata:
Updating /boot/grub/grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.24-21-generic
Found initrd image: /boot/initrd.img-2.6.24-21-generic
Found linux image: /boot/vmlinuz-2.6.24-20-generic
Found initrd image: /boot/initrd.img-2.6.24-20-generic
Found linux image: /boot/vmlinuz-2.6.24-19-generic
Found initrd image: /boot/initrd.img-2.6.24-19-generic
Found linux image: /boot/vmlinuz-2.6.24-16-generic
Found initrd image: /boot/initrd.img-2.6.24-16-generic
Found memtest86+ image: /boot/memtest86+.bin
done

If you haven't yet run the above, please do and it should resolve your issuse. If you ran it before, it wouldn't hurt to run it again as it does no harm. If no joy with the above, you can still edit menu.lst to add the new kernel as it wont kill the entire system.  It may crash when you select the new kernel if it's not added correctly but all you would have to do is reboot into a kernel you know is working and recheck menu.lst for any errors you have made in the new kernel listing. Linux is more user friendly than that unless you do something totally foolish like rm -rf / that would delete the entire partition. Of course you wouldn't do that.

HTH,

Leonard Chatagnier
lenc5570 at sbcglobal.net