Switched from systemd-boot to limine bootloader - Errors on updating the system

[Zesko]

@taker88

File has already been signed /boot/aedb1c168bfc40d9b11f09dcd75d2040/6.14.5-2-cachyos/linux
failed signing /boot/vmlinuz-linux-cachyos: /boot/vmlinuz-linux-cachyos does not exist
File has already been signed /usr/lib/systemd/boot/efi/systemd-bootx64.efi.signed
failed signing /boot/EFI/BOOT/BOOTX64.EFI: /boot/EFI/BOOT/BOOTX64.EFI does not exist
failed signing /boot/EFI/systemd/systemd-bootx64.efi: /boot/EFI/systemd/systemd-bootx64.efi does not exist
error: command failed to execute correctly

This seems related to missing systemd-boot-created files.

I believe those errors come from sbctl-batch-sign and the active systemd-boot-update.service trying to access files that don’t exist.

---

@taker88

failed signing /boot/EFI/BOOT/BOOTX64.EFI: /boot/EFI/BOOT/BOOTX64.EFI does not exist

In case the standard EFI path /boot/EFI/BOOT/BOOTX64.EFI doesn’t exist on your UEFI system, you can run sudo limine-install --fallback once.

This installs and keeps a fallback bootloader on the boot partition. It’s useful because most UEFI systems (for example, buggy MSI BIOS firmware) will automatically look for this bootloader if custom boot entries get wiped.