<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 16, 2015 at 12:13 AM, Chris Murphy <span dir="ltr"><<a href="mailto:lists@colorremedies.com" target="_blank">lists@colorremedies.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
> Windows failing to boot from grub with secure boot enabled is a different<br>
> story. If users can pick Windows in their firmware's boot device menu and it<br>
> boots and grub is simply failing to chainload it, then it's much less<br>
> critical of an issue, so I'm not sure if it should be a blocker, but it's<br>
> still a thing we probably want to work too, because it not working does hurt<br>
> the dual-boot user experience a bit.<br>
<br>
</span>Some manufacturers are not enabling USB or the keyboard at firmware<br>
initialization time in order to get faster boots. So it's not<br>
guaranteed the user can get to the firmware's built-in boot manager.<br>
In such a case, the user would need to boot Fedora (since they have no<br>
choice), and then use efibootmgr to change the BootNext NVRAM variable<br>
(or they can change BootOrder). So that'd need some better<br>
documentation probably.<br></blockquote><br></div><div class="gmail_quote">One idea that springs to mind is maybe having GNOME adding a "Reboot to Windows" option somewhere (if Windows is installed), and maybe a settings panel to select the default OS (I think OS X has something like this - correct me if I'm wrong).<br><br></div><div class="gmail_quote">However, I don't know if this is actually possible (or worth the effort).<br></div><div class="gmail_quote"><br></div>-- <br><div class="gmail_signature"><div dir="ltr">-Elad Alfassa.</div></div>
</div></div>