Arch Linux

EISENFELD

Member

From: Germany

Registered: 2024-03-13

Posts: 27

Website

New boot entry (efibootmgr) doesn't persist after reboot

Some months ago I successfully created boot entries with efibootmgr but suddenly they don't persist
after reboot. I read all about this problem in the Wiki and tried several things they suggest there (delete efi dump files, boot with 'efi_no_storage_paranoia' kernel parameter)
but no success. I now use systemd-boot and that's fine, but I just want to know what is the problem with EFI STUB boot on my machine now ?
I have the actual firmware of my mainboard 'Asroch A520m-itx'. Maybe it's a bug in the firmware ?

---

Ich weiß, dass ich nichts weiß !

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,272

Website

Re: New boot entry (efibootmgr) doesn't persist after reboot

This is a fairly common problem, UEFI implementations tend to be buggy.

If you're committed to EFI_STUB booting then you could compile your own kernel with CONFIG_CMDLINE pointing to the the root partition and supplying the other kernel parameters then place the kernel at /EFI/Boot/bootx64.efi on the EFI system partition, which will be loaded automatically.

Alternatively use the same location for a Unified Kernel Image or EFI loader for any of the bootloaders. GRUB has a --removable flag to do that and systemd-boot uses that location as a fallback automatically.

---

Para todos todo, para nosotros nada

-thc

Member

Registered: 2017-03-15

Posts: 685

Re: New boot entry (efibootmgr) doesn't persist after reboot

UEFI implementations tend to be buggy.

I think the behavior of those EFI implementations is simply sloppy and/or deliberate. All my early attempts to add and/or modify EFI boot manager entries from the OS were simply overwritten, ignored or deleted.