Public bug reported:
Upgraded to grub2 in jaunty without problems, then upgraded to karmic and
grub.cfg was not a bootable config
In order to boot now I've had to:
uncomment the line GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub
this may be because of bug 392836 or 406774
I also have to edit the line
initrd /boot/initrd.img-2.6.31-5-generic
to init= /boot/initrd.img-2.6.31-5-generic
by hitting e when grub displays the menu, and ctrl-x to boot
Description: Ubuntu karmic (development branch)
Release: 9.10
up to date as of bug posting date
da...@davslaptop:~$ apt-cache show grub-pc
Package: grub-pc
Priority: extra
Section: admin
Installed-Size: 1816
Maintainer: Ubuntu Core Developers <ubuntu-devel-disc...@lists.ubuntu.com>
Original-Maintainer: GRUB Maintainers <pkg-grub-de...@lists.alioth.debian.org>
Architecture: amd64
Source: grub2
Version: 1.96+20090725-1ubuntu1
da...@davslaptop:~$ apt-cache show grub-pc
Package: grub-pc
Priority: extra
Section: admin
Installed-Size: 1816
Maintainer: Ubuntu Core Developers <ubuntu-devel-disc...@lists.ubuntu.com>
Original-Maintainer: GRUB Maintainers <pkg-grub-de...@lists.alioth.debian.org>
Architecture: amd64
Source: grub2
Version: 1.96+20090725-1ubuntu1
Linux davslaptop 2.6.31-4-generic #23-Ubuntu SMP Mon Jul 27 18:39:59 UTC
2009 x86_64 GNU/Linux
I should note that my system hung during the distribution upgrade using
the gui, and I had to boot back in and finish the upgrade by a bit of
coaxing and "apt-get dist-upgrade"ing
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
grub.cfg generated initrd intead of init= in karmic
https://bugs.launchpad.net/bugs/410468
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
