Red Hat Bugzilla – Bug 250326
efibootmgr uses lower case hex values which violates EFI spec
Last modified: 2018-10-19 18:37:42 EDT
Description of problem:
On my SandDune (Superdome/sx2000), I have a _lot_ of disks, a lot of networking
cards, and a lot of various Linux installs. I have 10 bootable entries, as follows:
[root@worm0 ~]# efibootmgr
Timeout: 10 seconds
Boot0000* EFI Shell
Boot0001* Gbit Boot NIC
Boot0002* USB Optical/DVD drive
Boot0003* 10GigE NIC Boot
Boot0004* RHEL5 Server
Boot0005* RHEL4u4 AS
Boot0006* SCSI Optical/DVD Drive
Boot0007* Smart Setup from USB/HDD
Boot0008* RHEL4.5 AS (snap#5)
Now the problem is that if I install a NEW copy of RHEL4.5 (snapshot 5), the
installer creates an entry named "Boot000a" (with a lower-case 'A'). If you
boot to RHEL5 and run "efibootmgr", it complains about the lower-case 'A' and
suggests the user fix that by changing the boot entry via EFI.
The problem with this: EFI doesn't recognize it. So, RHEL4.5 needs to ensure
that Hex-digits a-f are UPPER-CASE when it creates boot entries.
It appears this was fixed upstream and is already fixed in RHEL5. I will
provide a patch.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Created attachment 160355 [details]
patch taken directly from upstream efibootmgr
Exception request will be filed ASAP.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.