On Fri, Aug 28, 2015 at 4:10 AM, Paul Cartwright pbcartwright@gmail.com wrote:
On 08/28/2015 04:22 AM, Tom H wrote:
On Thu, Aug 27, 2015 at 6:58 AM, Paul Cartwright pbcartwright@gmail.com wrote:
grub2-mkconfig works, but grub2-install /dev/sda gives me an error grub2-install /dev/sda grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist. Please specify --target or --directory. The message is clear. Use "grub2-install --target=x86_64-efi --efi-directory=/boot/efi /dev/sda"
I thought he said not to use grub2-install on UEFI systems..
Boot001A* ubuntu You've set Ubuntu to be the default efi binary.
You'd have to run "efibootmgr -o 0002,..." to set Fedora as the default.
and I did, and it works..
is there a good manual somewhere for efibootmgr??
efibootmgr -h
yeah, not a lot of help.. but this thread was:) efibootmgr -o xxxxx was the key...
I thought when a new kernel was installed, grub would automagically add it... not with efi?
Because you're using Ubuntu's grub. So you'd have to boot into Ubuntu and run "update-grub" in order to add the latest Fedora kernel to the Ubuntu grub mennu.
mmm in ubuntu I did grub-mkconfig & grub-install, but I didn't do the update-grub.. next time I boot ubuntu...
When UEFI Secure Boot is enabled, which it should be if available, especially on a system with Window on it, you need the distro signed shim.efi and grubx64.efi on the EFI system partition. If you use grub-install the signed copy is wiped out, and the system won't boot until you disable Secure Boot.
So in a UEFI Secure Boot world, grub-install (and grub2-install) is obsolete.
This bug is still annoying, and I wonder if it should be a blocker bug. https://bugzilla.redhat.com/show_bug.cgi?id=1170245