<div dir="ltr"><br><div class="gmail_extra"><br><br></div><div class="gmail_quote">On Tue, Apr 8, 2014 at 7:30 AM, Adam Williamson <span dir="ltr"><<a href="mailto:awilliam@redhat.com" target="_blank">awilliam@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">On Tue, 2014-04-08 at 07:16 +0300, Fred New wrote:<br>
<br>
> The<br>
> Unified Extensible Firmware Interface wiki page is rather outdated and<br>
> unhelpful as well.<br>
<br>
In what way? I wrote it, just a month or two ago. I'm not aware of<br>
anything in it which is outdated.<br></blockquote><div><br></div><div>Sorry, my mistake. I thought this one also referred to Fedora 18. The main problem</div><div>I had was the UEFI boot order problem mentioned below. This page doesn't tell</div>
<div>me how to use efibootmgr to fix that.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
<br>
> If you have UEFI and you have run grub2-install, you need to un-do that by<br>
> re-installing<br>
> grub2-efi:<br>
><br>
> yum reinstall grub2-efi<br>
<br>
That won't 'undo' anything. The grub2-efi package doesn't actually have<br>
any scripts, so reinstalling it doesn't really do anything much.<br></blockquote><div><br></div><div>Well in my case, reinstalling grub2-efi caused GRUB2 to stop reading the</div><div>configuration file from /boot/grub2/grub.cfg and to start reading from</div>
<div>/boot/efi/EFI/fedora/grub.cfg again. I didn't have to re-run grub2-mkconfig</div><div>because the configuration file was already built during the last kernel</div><div>update. I haven't tried booting Windows from my GRUB menu since this</div>
<div>fix, but I suspect it will work again, too. With the grub2-install GRUB, it</div><div>couldn't find Windows because it wasn't looking in the EFI partition.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
<br>
> And since Windows on my system places itself first in the EFI boot list<br>
> every time it<br>
> is booted,<br>
<br>
That's likely an issue in your system's firmware or Windows install<br>
(somehow). It shouldn't be doing that.<br></blockquote><div><br></div><div>Yes, it seems that any time I touch my firmware configuration ("BIOS</div><div>settings") or interrupt the boot sequence to boot Windows (after I've</div>
<div>managed to put Fedora first), the boot order resets to Windows first.</div><div>It may not be Windows doing it. I cannot move Fedora to the top of</div><div>the list using the "BIOS settings", I need to use efibootmgr for that.</div>
<div>(HP Envy 17-j007eo)</div></div><p>Fred</p><div class="gmail_extra"><br></div></div>