Fedora 17, EFI booting with grub-efi And then I used Fedup to update, which
went fine, and still uses grub legacy efi.
To upgrade to grub2-efi, I partially figured out how to do this:
cp /boot/efi/EFI/fedora/grubx64.efi
/boot/efi/EFI/System/Library/CoreServices/boot.efi
grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
Reboot now takes me to GRUB2, and loads the grub.cfg. However, at the point
where nouveau loads, text scroll hangs at nouveau. I can blindly login and do
some things, and ssh in. So I think it's vbios corruption again, and looks like
this bug has rematerialized:
https://bugzilla.redhat.com/show_bug.cgi?id=751147
Since it's the same kernel and nouveau, this actually looks like a GRUB2 bug,
not a nouveau bug. For whatever reason, even after installing the grub2-efi
package, the command grub2-install does not produce a new grub.efi file
anywhere I can find. The result I get is:
# grub2-install
/boot/efi doesn't look like an EFI partition.
Installation finished. No error reported.
Yet, there are no new files anywhere on the HFS+ EFI System partition, and
NVRAM hasn't been updated either. If I specify an alternate --efi-directory= I
can get a new grubx64.efi produced, relocate it, and update NVRAM, but it fails
in the same manner.
I'm thinking for F18 the easiest thing to do might be a sidebar/note in the
Fedup documentation that suggests Mac EFI boot users not upgrade grub-efi to
grub2-efi. And then sort out the grub2-efi issues for Fedora 19.
Comments?
What's weird is a beta or early final TC, Live CD written direct to a USB
stick, booted this same hardware to graphical Gnome without this problem. So
I'm not sure what's going on.
Chris Murphy
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
