Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionFinnbarr P. Murphy
2010-08-18 01:04:33 UTC
Most UEFI firmware does not understand a bootfile path of /EFI/redhat/grub.efi. Instead they expect to be able to boot using /EFI/BOOT/BOOTX64.EFI for X64 platforms or /EFI/BOOT/BOOTIA32.EFI for IA32 platforms. This is what you use on the install DVD and hence UEFI installs work flawlessly OOTB.
However that logic is not maintained when the ESP (EFI System Partition) is setup - I assume by Anaconda. Instead UEFI firmware is expected to able to locate and boot /EFI/redhat/grub.efi which is a bootfile path not specified in the UEFI specification as far as I recall. ("redhat" is permissible but "grub.efi" is not)
Please add /EFI/BOOT/BOOTIA32.EFI and /EFI/BOOT/BOOTIA32.CONF to the ESP for IA32 UEFI installs and /EFI/BOOT/BOOTX64.EFI and /EFI/BOOT/BOOTX64.CONF for X64 installs.
Comment 2RHEL Program Management
2010-08-18 01:38:04 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
We haven't seen any UEFI machines that don't support booting from any path on the system once the EFI nvram variables are set correctly with efibootmgr. Any such machine would be non-conformant with section 3.4 of the UEFI specification. Additionally, using /EFI/BOOT/BOOTXXX.EFI on any non-removable media violates section 3.4 of the UEFI specification.
Most UEFI firmware does not understand a bootfile path of /EFI/redhat/grub.efi. Instead they expect to be able to boot using /EFI/BOOT/BOOTX64.EFI for X64 platforms or /EFI/BOOT/BOOTIA32.EFI for IA32 platforms. This is what you use on the install DVD and hence UEFI installs work flawlessly OOTB. However that logic is not maintained when the ESP (EFI System Partition) is setup - I assume by Anaconda. Instead UEFI firmware is expected to able to locate and boot /EFI/redhat/grub.efi which is a bootfile path not specified in the UEFI specification as far as I recall. ("redhat" is permissible but "grub.efi" is not) Please add /EFI/BOOT/BOOTIA32.EFI and /EFI/BOOT/BOOTIA32.CONF to the ESP for IA32 UEFI installs and /EFI/BOOT/BOOTX64.EFI and /EFI/BOOT/BOOTX64.CONF for X64 installs.