We got reports from the field stating that the boot failed because the
efi variables could not be set and we bail out in this case. As the
systemd boot protocol is not a mandatory feature, we can safely ignore
this case. This is in line with the implementation in systemd-boot.
We now change the bail-out to an error message without bail-out.
Fixes: 7c90e82 ("efi: implement systemd boot loader interface")
Reported-by: Jan Kiszka <jan.kis...@siemens.com>
Signed-off-by: Felix Moessbauer <felix.moessba...@siemens.com>
---
main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/main.c b/main.c
index 3885754..f0b9aa0 100644
--- a/main.c
+++ b/main.c
@@ -192,8 +192,8 @@ EFI_STATUS efi_main(EFI_HANDLE image_handle,
EFI_SYSTEM_TABLE *system_table)
bg_interface_params.loader_device_part_uuid = boot_medium_uuidstr;
status = set_bg_interface_vars(&bg_interface_params);
if (EFI_ERROR(status)) {
- error_exit(L"Cannot set bootloader interface variables",
- status);
+ ERROR(L"Cannot set bootloader interface variables (%r)\n",
+ status);
}
INFO(L"LoaderDevicePartUUID=%s\n", boot_medium_uuidstr);
FreePool(boot_medium_uuidstr);
--
2.49.0
--
You received this message because you are subscribed to the Google Groups "EFI
Boot Guard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to efibootguard-dev+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/efibootguard-dev/20250514085307.2026263-2-felix.moessbauer%40siemens.com.
