[SOLVED] efibootmgr boot entries not persistent, but I can find traces of them in NVRAM | Arch Linux Community | Page 1

torn verge Aug 28, 2023, 1:53 PM

#

I don't really know which part of the stack is causing this problem, so sorry if it turns out to be completely unrelated to linux

I'm trying to use EFISTUB to boot, and every time I add the boot entries with efibootmgr they then show up properly when I run efibootmgr -u, but as soon as I power cycle the computer they are gone. I thought this was as simple as the firmware wiping NVRAM on boot for some reason, but I noticed in bcfg that there are traces of them in a different entry. The attached image is the entry for Windows Boot Manager, and you can see remnants of linux kernel args near the end. The only other bootable device on the system is GRUB, so those kernel parameters could only be from the EFISTUB entries as far as I understand

I did manage to get the new boot entries to show up once, and I have no idea why it worked when it did. I was preparing to update the motherboard firmware and they suddenly all showed up, even though those entries were added multiple power cycles ago by that point. I had to remove those entries to change a kernel parameter and I haven't been able to get them to show again since.

So is this a problem I can actually fix, or is the firmware just bad? I have an Asrock B550 phantom gaming 4 motherboard, if that info's of any use.

orchid snow Aug 28, 2023, 1:55 PM

#

try a UKI

#

its really simple and easy to setup

#

if you set the UKI path to /boot/efi/boot/bootx64.efi then you wont need efibootmgr at all

torn verge Aug 28, 2023, 1:56 PM

#

So I can replace bootx64.efi to override the entry currently for GRUB? Or does GRUB launch from somewhere else?

orchid snow Aug 28, 2023, 1:57 PM

#

you have just one boot partition on a GPT partition table right?

torn verge Aug 28, 2023, 1:57 PM

#

Yes

orchid snow Aug 28, 2023, 1:58 PM

#

if GRUB takes precedence and you dont want it to, you can delete the boot entries for GRUB and the old EFISTUB entries, leaving only the current EFISTUB entry to exist

#

and if you use a UKI, you can remove all entries

torn verge Aug 28, 2023, 2:41 PM

#

Well I created a UKI to boot from and added it through efibootmgr and it showed up first time, working perfectly. I have no idea why the entry for the UKI image worked perfectly while the EFISTUB entries always broke, but I'm just not going to touch it

Did have to remove my fallback initcpio to make space in /boot though, i guess booting through GRUB can be my fallback now

#

Thanks for the help!

orchid snow Aug 28, 2023, 2:47 PM

#

np

#

i mean u dont have to remove anything if they all fit into /boot

#

since you wont get any more space in / anyway

sullen shard Aug 28, 2023, 3:36 PM

#

torn verge Thanks for the help!

... solved

wise marlinBOT Aug 28, 2023, 3:36 PM

#

#9742 📣 If there is nothing else that we can do for you, please close this thread by adding "[SOLVED]" to the title.

You can do this on desktop by clicking the three dots on the top right of the page, and pressing "Edit Post".
You can also do this on Android / iOS by long tapping your post in the text channel list, and tapping "Edit Post".

Your title should be like so: https://cdn.discordapp.com/attachments/503224329191030787/1039841700417384498/image.png
Thank you

#[SOLVED] efibootmgr boot entries not persistent, but I can find traces of them in NVRAM