Intrepid problem
Ray Parrish
crp at cmc.net
Thu Nov 13 06:40:32 UTC 2008
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
Steven Davies-Morris wrote:
> Bill Taylor wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> You need to upgrade the kernel to the latest 2.6.27.x version. In
>> Synaptic look for linux-image-2.6.27 and associated files. Then do
>> the vBox upgrade to 2.0.4.
>>
>> Cheers, SDM
>> - ------------
>> Steven, sudo update-grub returns;
>>
>> Searching for GRUB installation directory ... found: /boot/grub
>> Searching for default file ... found: /boot/grub/default
>> Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
>> Searching for splash image ... none found, skipping ...
>> Found kernel: /boot/vmlinuz-2.6.27-7-generic
>> Found kernel: /boot/vmlinuz-2.6.24-19-generic
>> Found kernel: /boot/memtest86+.bin
>> Updating /boot/grub/menu.lst ... done
>>
>> but when rebooted it is not there.
>>
>
> Ooooh. Not nice. Have you tried a recovery boot and told it to fix
> broken packages? Or you could boot of the 2.6.24-19 kernel, then go
> into Synaptic and uninstall the 2.6.27-7 kernel. Then reinstall it.
> Or alternatively go to a shell and use apt-get to remove and then do
> a reinstall of the 2.6.27-7 kernel. Or wait until somebody here that
> knows a lot more than I do suggests something else.
>
--
http://www.rayslinks.com/ Web index of human reviewed links.
<http://www.rayslinks.com/Troubleshooting%20and%20fixing%20Windows.html>
Trouble shooting and Fixing Windows
http://www.writingsoftheschizophrenic.com My poetry in web pages
More information about the ubuntu-users
mailing list