Hide Forgot
Description of problem: Motherboard with UEFI boot enabled. I have installed Fedora 24 using an Alpha netinstall usb stick. The system fails to boot asking for a boot disk. If, however, i disable UEFI in the boot menu, the system boots fine (except it has not added existing Windows 10 install to the menu list). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The system was installed with UEFI support enabled in BIOS.
Mixed firmware modes aren't supported in Fedora, or in any distribution that I know of. The firmware in this case is UEFI, it cannot be disabled regardless of the the UI says. UEFI "disabled" actually means "enable a UEFI compatibility support module to present a faux BIOS to the OS" so that the OS thinks it's a computer with BIOS firmware rather than UEFI firmware. UEFI and BIOS systems boot completely differently, requiring completely different bootloader binaries and installation method and location. To troubleshoot this you need to revert the firmware setting. I suggest making certain the firmware is up to date, there are tons of UEFI bugs. My new system has had half dozen firmware updates in less than 9 months. Then boot Fedora media and post the results of: # efibootmgr -v Assuming you get something other than a one or two line error message, proceed with reinstalling Fedora. Again, before rebooting from the installer, capture the result from 'efibootmgr -v' and then boot Fedora and see if it works. If it's not working I'll be curious what the efibootmgr output is.
Thank you for the feedback. Now this strange thing happens: - i can install then boot windows 10 when UEFI boot is 'enabled'. - i can install but not boot Fedora 24 when UEFI boot is 'enabled'. -- if i install F24 when UEFI boot is enabled and then disable UEFI boot, i can boot the installedF24 - But if UEFI boot is enabled i can boot F24 Live media or netinstall just fine. On the other hand, whether UEFI boot is enabled or disabled, efibootmgr produces same output: $ efibootmgr -v efibootmgr: EFI variables are not supported on this system. So i'm confused: - how can install media boot on the same system where the installed F24 can not? And why the output of efibootmgr is the same whether the setting is enabled or disabled? Regarding the firmware, it's the most uptodate but it's still old: 12/7/2012 . The board is: http://www.intel.com/content/www/us/en/support/boards-and-kits/desktop-boards/intel-desktop-boards-with-intel-h67-express-chipset/intel-desktop-board-dh67gd.html I hope something good comes out of this investigation.
(In reply to cornel panceac from comment #3) > - But if UEFI boot is enabled i can boot F24 Live media or netinstall just > fine. What kind of boot media are you using and how are you creating it? > $ efibootmgr -v > efibootmgr: EFI variables are not supported on this system. The system isn't booted in UEFI mode, it's booted in CSM-BIOS mode. > > So i'm confused: > - how can install media boot on the same system where the installed F24 can > not? Firmware oddness or bugs or both. And the super annoying thing is the UI for the firmware has no standardization so it's made more difficult for users to help each other configure things correctly. I don't know how common it is, but I've seen firmware default to CSM-BIOS mode booting from optical media, while defaulting to UEFI for drives including USB drives. Still others have BIOS/legacy boot options for USB and UEFI option for the exact same USB stick. So if you're not cluing into the arcane details, you won't realize you're getting completely different boots. > > And why the output of efibootmgr is the same whether the setting is enabled > or disabled? > > Regarding the firmware, it's the most uptodate but it's still old: 12/7/2012 You could try this: https://www-ssl.intel.com/content/www/us/en/support/boards-and-kits/desktop-boards/000005753.html?wapkw=intel+desktop+board+dh67gd Apple has been using CMOS/NVRAM for eons and have long ago discovered enough corruptions are possible that for 30+ years across a wide assortment of hardware, offer a keyboard shortcut for the user to easily reset NVRAM at startup.
(In reply to Chris Murphy from comment #4) > (In reply to cornel panceac from comment #3) > > > - But if UEFI boot is enabled i can boot F24 Live media or netinstall just > > fine. > > What kind of boot media are you using and how are you creating it? I use an USB stick. > > $ efibootmgr -v > > efibootmgr: EFI variables are not supported on this system. > > The system isn't booted in UEFI mode, it's booted in CSM-BIOS mode. This is strange, because as i've said, the BIOS interface says different things and, also in one case (UEFI boot disabled) installed Fedora 24 boots, and in the other (UEFI boot enabled) it does not, so the modes are clearly different. > > > > So i'm confused: > > - how can install media boot on the same system where the installed F24 can > > not? > > Firmware oddness or bugs or both. And the super annoying thing is the UI for > the firmware has no standardization so it's made more difficult for users to > help each other configure things correctly. > > I don't know how common it is, but I've seen firmware default to CSM-BIOS > mode booting from optical media, while defaulting to UEFI for drives > including USB drives. Still others have BIOS/legacy boot options for USB and > UEFI option for the exact same USB stick. So if you're not cluing into the > arcane details, you won't realize you're getting completely different boots. > > > > > And why the output of efibootmgr is the same whether the setting is enabled > > or disabled? > > > > Regarding the firmware, it's the most uptodate but it's still old: 12/7/2012 > > > You could try this: > https://www-ssl.intel.com/content/www/us/en/support/boards-and-kits/desktop- > boards/000005753.html?wapkw=intel+desktop+board+dh67gd > > Apple has been using CMOS/NVRAM for eons and have long ago discovered enough > corruptions are possible that for 30+ years across a wide assortment of > hardware, offer a keyboard shortcut for the user to easily reset NVRAM at > startup.
(In reply to cornel panceac from comment #5) > > What kind of boot media are you using and how are you creating it? > > I use an USB stick. Exactly how are you creating the install media on that USB stick. What utility? What command?
I am using the liveusb-creator, version 3.92.1-1.fc24 . Ref.: > You could try this: > https://www-ssl.intel.com/content/www/us/en/support/boards-and-kits/desktop- > boards/000005753.html?wapkw=intel+desktop+board+dh67gd > I am guilty, kp[aral warned me about this but i did not listen. It's actually the operating systm that is not booting, the system itself starts, it just does not start the installed operating system. So the title is misleading and i will update it now.
Created attachment 1151742 [details] UEFI boot options When the UEFI boot is enabled, installed Fedora 24 is not booting (but netinstall/live usb stick boots fine).
Created attachment 1151743 [details] Computer boot error with UEFI boot enabled. When UEFI boot is enabled, computer asks for a system disk.
Could you try this: 1. Make sure UEFI is enabled 2. Boot install media 3. Switch to console and run efibootmgr -v and attach the output here. You could also look in /sys/firmware/efi/efivars/ and see if there are entries. If not then it is certainly falling back to CSM mode and isn't really booting as a UEFI system for whatever reason.
(In reply to cornel panceac from comment #7) > I am using the liveusb-creator, version 3.92.1-1.fc24 . OK when I say 'what command' I literally mean what complete command line plus all flags plus source plus device. Please don't be coy when someone asks "exactly how". With 'livecd-iso-to-disk' on UEFI, typically options --format --reset-mbr --efi are all necessary to produce a USB stick that will actually boot a computer in UEFI mode. So if you're missing any of those please try again with all three. And make sure you point it at a whole USB stick, not a partition.
Chris, the install media is booting in EFI mode, the installed system is the one who is not booting. Regarding your question: liveusb-creator is a GUI thing, and no command line parameters were used. The Netinstall media is the F24 Alpha x64. I am sorry if sometimes i make mistakes, but i 'm trying hard not to :)
Created attachment 1152133 [details] efibootmgr -v Attached the efibootmgr -v output from netinstall.
Created attachment 1152136 [details] efivars Attached the content of /sys/.../efivars/ from netinstall.
One additional thing: depending on the "BIOS" boot configuration (UEFI mode disabled versus enabled), the boot menu of netinstall media changes from some nice coloured text to some also nice white only text. So the media (or at least grub/syslinux) 'knows' in what mode is booting.
Could it be that the problem here is that Ggrub is installed instead of syslinux? Can these two be installed one beside the other? Can syslinux be installed after the install completes?
The latest netinstall media i've tried behaves better: Allows Windows to boot, and from EFI boot manager you can select Fedora. Version is: Fedora-Everything-netinst-x86_64-24_Beta-1.2.iso Still, in my ideal world, the Windows boot manager would be replaced by fedora boot manager, from which you can select Windows and it boots. As a side note, right now, from Fedora boot manager you can select Windows but it does NOT boot.
Sorry, long week. Yes, that version of liveusb-creator should produce the USB stick correctly. The efibootmgr and efivars in c13 and c14 show that the system is booted in UEFI mode. However, efibootmgr shows Windows is the default boot entry, so it should boot by default without error; meanwhile there's no Fedora boot entry there. Re: c16 On Fedora syslinux is used to boot BIOS systems from install media. Installed systems use grub or grub-efi. Yes they can coexist but that's just going to confuse things more.
(In reply to cornel panceac from comment #17) > The latest netinstall media i've tried behaves better: Allows Windows to > boot, and from EFI boot manager you can select Fedora. > > Version is: Fedora-Everything-netinst-x86_64-24_Beta-1.2.iso Ah, good, so it sounds like this is fixed? Your results above confirm that the installation media *is* booting in UEFI mode which is what I was worried about. > > Still, in my ideal world, the Windows boot manager would be replaced by > fedora boot manager, from which you can select Windows and it boots. > > As a side note, right now, from Fedora boot manager you can select Windows > but it does NOT boot. That's a known issue, IIRC on some systems it works and on others you just have to use the EFI menu to boot windows.
Yep, that's probably bug 1320273.
So the original problem was that the installed OS was not booting in UEFI mode. Now it is booting, but never starts GUI for some reason. Due to the Easter in my country, i'll continue investigation only next Tuesday. Thank you for all the support up to this point. Oh, and i've seen that "error: out of memory" from the boot manager, too. But i _believe_ i've seen it while trying to boot Fedora ... As said, i'll check again on Tuesday.
F24 is still in development so it is likely this was fixed by an updated package. Not starting the GUI is going to be unrelated to this so I'm going to close this for now, thanks.