Hi Felix,
Felix Zielcke wrote:
> Lucid has 1.97+20091130-1ubuntu1, which is more recent then your
> outdated svn build.
> So please try that and then this bug report can be probable just marked
> Fix Released.
> EFI port isn't well maintained but recently there was some work done
> with it IIRC.
After purging the Jaunty packages, I installed these Lucid ones via
`dpkg -i`:
grub-common_1.97+20091130-1ubuntu1_amd64.deb
grub-efi-amd64_1.97+20091130-1ubuntu1_amd64.deb
grub-install produces a working grub.efi in /boot/grub.
I am able to manually enter linux, initrd, and boot commands and boot my
system.
However, the update-grub script still produces a config file that fails
in the same way as described previously in this report.
Indeed, if I try any other commands instead of just immediately entering
the appropriate 'linux' and 'initrd' lines, grub stops behaving
appropriately in response to commands. This behavior appears consistent
with that observed via my own configuration files:
These two grub.cfg files fail:
menuentry "GNU/Linux" {
set root=(hd0,1)
linux /vmlinuz-2.6.31-14-generic root=/dev/sda6 ro
initrd /initrd.img-2.6.31-14-generic
}
set timeout=30
set default=0
menuentry "GNU/Linux" {
linux /vmlinuz-2.6.31-14-generic root=/dev/sda6 ro
initrd /initrd.img-2.6.31-14-generic
}
This grub.cfg works:
menuentry "GNU/Linux" {
linux /vmlinuz-2.6.31-14-generic root=/dev/sda6 ro
initrd /initrd.img-2.6.31-14-generic
}
Also, even with the failing grub.cfg files: if I immediately hit escape
and enter the linux and initrd commands manually, things work. If I
first attempt to boot the menu entry by hitting ENTER, and then go to a
grub prompt and attempt to do things manually, the 'linux' command is
not recognized.
It is as though the presence of the "set" commands cause defaults for
other environment variables to be discarded, which doesn't make sense to me.
Thanks,
-Jon
--
"Failed to boot default entries." with grub-efi-amd64 upon reboot on HP 8530p
with UEFI enabled
https://bugs.launchpad.net/bugs/499849
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
