| Summary: | grub2 does not install /boot/efi/EFI/BOOT/BOOTx64.EFI on UEFI system | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael Brown <mryanbrown> |
| Component: | grub2 | Assignee: | Peter Jones <pjones> |
| Status: | CLOSED DEFERRED | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | bcl, dennis, mads, mryanbrown, pjones |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-08-26 15:09:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Michael Brown
2013-08-26 14:14:46 UTC
That is by design. That location is only intended for (re)movable bootable media. On normal EFI systems the firmware EFI bootloader should let the user choose or be configured in nvram to point at the fedora folder by default. see: https://bugzilla.redhat.com/show_bug.cgi?id=624873 and "... section 3.4.1.2 of the spec, which specifies that in the absence of any configured boot variables it is permitted for the firmware to treat the EFI system partition in the same way as removable media - that is, it'll boot EFI/boot/bootx64.efi or whatever." (source: http://mjg59.dreamwidth.org/4125.html) Sorry I forgot to add, befire I copied bootx64.efi, efibootmgr listed the following: BootCurrent: 0000 Timeout: 2 seconds BootOrder: 0000 After it displayed: BootCurrent: 0000 Timeout: 2 seconds BootOrder: 0000,0001 Boot0000* Fedora Boot0001* UEFI : SATA : PORT 6G 0 : Corsair Neutron GTX SSD : PART 0 : OS removed bootx64.efi and system now boots fine with the Fedora entry. will contact Intel regarding possible firmware issue |