On Tue, Apr 8, 2014 at 7:41 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > > You need to install or reinstall grub2-efi and shim packages. Aha, a correct answer! Thanks! Based on this hint, I think I figured it out. I updated the wiki accordingly. Can you take a quick look at: https://fedoraproject.org/wiki/GRUB_2#Updating_GRUB_2_configuration_on_UEFI_systems > > >> I can't fix it because any attempt to >> change my efi variables results in an OOPS. I can't report the OOPS >> with abrt because of a correct but inconsequential kernel taint due to >> #906568, which is probably fixed in 3.14. So I was going to wait for >> the 3.14 rebase or perhaps boot a custom kernel to see what helps. I >> haven't had time for that yet. > > Make sure the firmware is up to date. And if with 3.14 and current firmware you still get an oops when modifying NVRAM entries you'll want to file a bug against the kernel. If it were me I'd file both on kernel.org and redhat.com bugzillas with the proper cross-referencing. > > It may still end up being a firmware problem that the kernel folks can't do anything about, but to have a chance of it being fixed kernel side requires a bug > >> >>> 2. Do you have a /boot/efi/EFI/fedora/grub.cfg ? >> >> No. But I have a /boot/efi/EFI/redhat/grub.conf, attached. >> /etc/grub.conf is a symlink to it. > > That's what grub legacy EFI used. I forget if fedup upgrades grub on UEFI systems. > > > >> >> It's currently mostly working, modulo the efibootbgr issue. But I >> don't actually know what to type into efibootmgr to fix it, the OOPS >> notwithstanding. I can probably figure it out once the OOPS is fixed. > > Strictly speaking you don't need to point UEFI non-Secure Boot computer to shim.efi, you can just leave it alone and put a grub.cfg in the proper place. At the grub prompt if you type set you should see either config_directory= and prefix= to show where it's looking for the grub.cfg. https://bugzilla.kernel.org/show_bug.cgi?id=73761 https://bugzilla.redhat.com/show_bug.cgi?id=1085957 > >> or, even better, if anaconda's bootloader >> installation process were factored out into a command I could run. > > I don't understand what this means. Being able to do: $ sudo fedora-configure-bootloader would be awesome. It would probably have to take some command line arguments. --Andy -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
