diff options
| author | Renaud Métrich <rmetrich@redhat.com> | 2024-06-04 14:57:55 +0200 |
|---|---|---|
| committer | Peter Jones <pjones@redhat.com> | 2025-01-17 14:45:32 -0500 |
| commit | 7864c1048223e6f7a898a9f61ee3a639d1ff9b26 (patch) | |
| tree | 33eb40be1f1b3aa4f8f8b71202e781a9387da596 /mock-variables.c | |
| parent | 1508ece179267943bad5851010eba8c00570c0ed (diff) | |
| download | efi-boot-shim-7864c1048223e6f7a898a9f61ee3a639d1ff9b26.tar.gz efi-boot-shim-7864c1048223e6f7a898a9f61ee3a639d1ff9b26.zip | |
Provide better error message when MokManager is not found
If MokManager has to be entered but system is booting on disk on
EFI/BOOT/BOOTx.EFI entry, MokManager cannot be found because it's not in
that directory.
This indicates an issue with the BootOrder or the UEFI firmware is just
not taking BootOrder into account (seen on Lenovo ThinkPad P1 Gen 6 and
VMWare), or that the boot media has incorrectly been created without
MokManager.
This patch prints a related message and reboots after 10 seconds.
Reproducer:
1. Import a certificate using mokutil
2. Tell UEFI to boot on BOOTX64.EFI entry on next boot
Result without the patch with verbosity:
-----------------------------------------------------------------------
mok.c:1045:import_mok_state() checking mok request
shim.c:866:load_image() attempting to load \EFI\BOOT\mmx64.efi
Failed to open \EFI\BOOT\mmx64.efi - Not Found
Failed to load image \EFI\BOOT\mmx64.efi: Not Found
shim.c:888 load_image() Failed to open \EFI\BOOT\mmx64.efi - Not Found
shim.c:1115 read_image() Failed to load image \EFI\BOOT\mmx64.efi: Not Found
Failed to start MokManager: Not Found
mok.c:1047:import_mok_state() mok returned Not Found
Something has gone seriously wrong: import_mok_state() failed: Not Found
-----------------------------------------------------------------------
Signed-off-by: Renaud Métrich <rmetrich@redhat.com>
Diffstat (limited to 'mock-variables.c')
0 files changed, 0 insertions, 0 deletions