efibootmgr: kernel post-install hook creates entries which are not bootable on strict UEFI

ackalker commented 5 years ago

System

xuname:
Void 5.1.10_1 x86_64 GenuineIntel uptodate rrrrmdFFFFFFFFF
package:
efibootmgr-17_2

Expected behavior

Installing a new kernel or force reconfiguring an already installed kernel should create or update a boot entry that actually boots that kernel.

Actual behavior

The generated boot entry for booting EFISTUB kernel gets rejected by my UEFI firmware because the binary file name (for example vmlinuz-5.1.10_1 lacks an .efi extension.

Steps to reproduce the behavior

Boot the system in UEFI mode on machine with a 'strict' (standard compliant) UEFI firmware.
Install efibootmgr package
Make sure that /etc/default/efibootmgr-kernel-hook contains uncommented line MODIFY_EFI_ENTRIES=1 and appropriate OPTIONS="..." value for that kernel
Install or force reconfigure a kernel
(optional) Reconfigure boot order using efibootmgr -o ...

dko1905 commented 3 years ago

I have the same issue. It would be nice for this to be fixed.

github-actions[bot] commented 2 years ago

Issues become stale 90 days after last activity and are closed 14 days after that. If this issue is still relevant bump it or assign it.

void-linux / void-packages