Red Hat Bugzilla – Bug 971980
UEFI installation hangs
Last modified: 2014-02-05 16:43:24 EST
Description of problem:
Installation of Fedora 18 hangs in UEFI mode on ASUS F2A85-M Board. (current BIOS Version 6102 and all lower versions)
Create Boot-medium (USB Flash Drive or DVD), press F8 after power on, select UEFI: <Device with Install-Medium>
Steps to Reproduce:
1. Press F8 after power on, to open BOOT-Menu
2. Select UEFI: <Install medium>
3. GRUP MENU is showning
4. Select first entry
5. "Secure boot not enabled" is showing
6. Blank screen is showing
7. nothing happens
showing Grub Menu, Secure boot not enabled(or if secureboot is enabled: "Binary is verified by the vendor certificate"), blank screen -> hangs
boot to the installer
Samsung 830 SSD 256GB
I get exactly the same on a Thinkpad W530 attempting a Fedora 19 x86_64 install (or rescue, or ISO checksum test) in UEFI mode. I have 32 GB RAM and discrete graphics is disabled in the BIOS. Enabling/disabling UEFI CSM does not change the outcome.
While trying to boot from the F19 install DVD from an external USB I get to the Grub menu as expected. No matter which option I select, there is a short activity on the DVD drive and then I'm stuck at "Secure boot not enabled" (if secure boot is disabled in the bios) or the "Binary is verified..." message if I enable it.
I have an F19 installation on my (GPT-partitioned) SSD that was FedUp-graded from F18. This used to boot in UEFI mode, but I broke something during the beta cycle. When I try to boot this install I get exactly the same issue: The Grub2 commandline works, but when booting a kernel it immediately hangs with the "Secure boot not enabled" message on an otherwise black screen. However, on the already installed version the /boot/efi/EFI/fedora/grub.cfg is wrong so I might be doing something wrong on the Grub2 commandline.
I also have the same thing on an MSI GX70 3BE. At the suggestion of upstream, I added the efi linux.mod to a usb live (or install) key, added "insmod linux" and changed "linuxefi" and "initrdefi" to "linux" and "initrd" in grub.cfg and was able to boot successfully.
I think bug 1004195 is a duplicate.
Stills happens with Fedora-Live-Desktop-x86_64-20-Alpha-4.iso, for the record.
I applied the latest bios update to my W530 since the changelog mentioned some fix for usb booting, but that didn't make a difference either.
(In reply to Volker Braun from comment #1)
> No matter which option I select, there is a short
> activity on the DVD drive and then I'm stuck at "Secure boot not enabled"
> (if secure boot is disabled in the bios) or the "Binary is verified..."
> message if I enable it.
This means the kernel was loaded successfully and then it failed.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.