![]() ![]() If so, please review the changes you've made to your menu.lst and apply them to the "Default options" section of variables in menu.lst, as documented in the same file then run 'sudo update-grub' and choose "install the package maintainer's version" instead of the default "keep the local version currently installed". ![]() The usual cause for the problem you're seeing is that you have manually edited your menu.lst, then on upgrade you've answered when prompted that you want to keep these local changes instead of letting update-grub overwrite them. ![]() So far, that bug has been unreproducible for anyone else. įound kernel: /vmlinuz- 2.6.31- 14-genericįound kernel: /vmlinuz- 2.6.28- 13-genericĪnd cat /boot/grub/menu.lst | grep nothing.Īttaching full output of installer on reinstall, and full menu.lst after that.īug #470265 is an exceptional case where the user's /etc/kernel- img.conf is missing the hooks that are supposed to be set up as part of every install. Testing for an existing GRUB menu.lst file. If I run reinstall of linux-image for 2.6.13 then grub says it updated menu.lst, but it did not. System still boots the old kernel 2.6.28-13-generic instead of current one 2.6.31. If running 'sudo update-grub' does not add a boot entry to /boot/grub/menu.lst for the Ubuntu 9.10 kernel (2.6.31), please follow the instructions there. Release notes for this issue can be found at ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |