Closed issue by dkwo on void-packages repository https://github.com/void-linux/void-packages/issues/38533 Description: ### Is this a new report? Yes ### System Info Void 5.18.16_1 x86_64-musl GenuineIntel uptodate rrnDFFFFFFFFF ### Package(s) Affected efibootmgr-18_1 ### Does a report exist for this bug with the project's home (upstream) and/or another distro? Cannot find any. ### Expected behaviour The kernel hook does the job of creating a new entry. ### Actual behaviour No entry is created: more precisely, it creates an entry, but does not add it to the bootorder. This is from inside the installer chroot (both the working way and the broken one). The package itself works if I use `doas efibootmgr --disk /dev/nvme0n1 --part 1 --create --label "Void Linux with test kernel" --loader /vmlinuz-5.18.16_1 --unicode 'loglevel=4 rd.luks.name=809df427-d7d5-408c-a195-3be6e8681333=cryptroot root=/dev/mapper/cryptroot rd.luks.options=discard initrd=\initramfs-5.18.16_1.img' --verbose` I'm using ``` $ cat /etc/default/efibootmgr-kernel-hook # Options for the kernel hook script installed by the efibootmgr package. MODIFY_EFI_ENTRIES=1 # Kernel command-line options. OPTIONS="loglevel=4 rd.luks.name=809df427-d7d5-408c-a195-3be6e8681333=cryptroot root=/dev/mapper/cryptroot rd.luks.options=discard" # Disk where EFI Partition is. Default is /dev/sda DISK="/dev/nvme0n1" # Partition number of EFI Partition. Default is 1 PART=1 ``` ### Steps to reproduce `xbps-reconfigure -f linux5.18`