View Issue Details

IDProjectCategoryView StatusLast Update
0016916CentOS-7grub2public2020-01-15 01:28
Reporterthangqn 
PrioritynormalSeverityminorReproducibilityrandom
Status newResolutionopen 
PlatformOsprey (Linux for aarch64)OSCentOSOS Version7.6
Product Version7.6.1810 
Target VersionFixed in Version 
Summary0016916: In grub menu, can't return to EFI shell when typing 'c' character
DescriptionFollowing standard flow, character ‘c’ was sent at Boot Menu and got to GRUB successfully. Then, type 'exit' in grub shell to return EFI shell. See the following errors:
1. Instead of entering UEFI Shell, the following message is displayed and UEFI automatically create a boot entry pointed to “\EFI\centos\shimaa64.efi”:
  “System BootOrder not found”.

2. Boot Menu appeared again. Type ‘c’ again to stop the countdown & got back to GRUB. Here, ‘exit’ was sent with the hope of exiting back to UEFI Shell but somehow UEFI reset the board.
Steps To Reproduce1. Install CentOS 7.6
2. Boot to UEFI, then grub menu.
3. Type 'c' to enter grub shell.
4. Type 'exit' to exit grub shell. Expect to return to EFI shell.
TagsNo tags attached.
abrt_hash
URL

Activities

thangqn

thangqn

2020-01-13 08:39

reporter  

thangqn

thangqn

2020-01-13 08:42

reporter   ~0036011

The issue does not happen again if downgrading shim and mokutil in CentOS 7.5 as in the following steps:
1. Download rpm package from :
http://mirrors.aliyun.com/centos-vault/altarch/7.5.1804/os/aarch64/Packages/shim-aa64-12-1.el7.aarch64.rpm
http://mirrors.aliyun.com/centos-vault/altarch/7.5.1804/os/aarch64/Packages/mokutil-12-1.el7.aarch64.rpm

2. Remove the current shim and mokutil:
  # yum remove -y shim-aa64
  # yum remove -y mokutil

3. Install rpm package , which was downloaded as above.
  # rpm -ivh shim-aa64-12-1.el7.aarch64.rpm
  # rpm -ivh mokutil-12-1.el7.aarch64.rpm

4. Check again the package installed:
  # rpm -qa | grep mok
  mokutil-12-1.el7.aarch64
  # rpm -qa | grep shim
  shim-aa64-12-1.el7.aarch64
GregoryYoung

GregoryYoung

2020-01-15 01:28

reporter   ~0036023

Does this happen if you upgrade to CentOS 7.7.1908? I know there were a few UEFI signing issues around the 1810 time-frame, and IIRC the cert expired, or there was some delay in the renewal. I don't use aarch64, so I can't test, but I have run into some UEFI issues on x86_64 over the past 2 years, either due to signing problems on the UEFI binaries, or missing upstream dracut module dependencies.

Issue History

Date Modified Username Field Change
2020-01-13 08:39 thangqn New Issue
2020-01-13 08:39 thangqn File Added: Screen Shot 2020-01-13 at 15.38.14.png
2020-01-13 08:39 thangqn File Added: Screen Shot 2020-01-13 at 15.38.50.png
2020-01-13 08:42 thangqn Note Added: 0036011
2020-01-15 01:28 GregoryYoung Note Added: 0036023