MX Linux Forum

Holly Buzzfart fehlix!!

It worked! You're a freakin' genius and I thank you for your time!!

lachelp wrote: Sun Nov 10, 2024 7:47 pm It worked!

Glad you made it. Perhaps tidy up the NVRAM and remove the non-funtional boot entry
shown with "efibootmgr -v" as and remove on CLI with or with short options or using GUI do remove with "Manage UEFI Boot Options" found within the tool "MX Boot Options"

Thanks fehlix,

I've remove the non=functional boot entry, but how do I go about tidying up the NVRAM?

lachelp wrote: Mon Nov 11, 2024 8:27 am Thanks fehlix,

I've remove the non=functional boot entry, but how do I go about tidying up the NVRAM?

efibootmgr can read and write entries stored into the UEFI-NVRAM storage.
So if you removed the entry with efibootmgr or with MX "Manage Uefi Boot Options" you already
sorted the NVRAM. Some UEFI-firmware interface allow directly to remove those orphaned boot options.
Some other UEFI-firmware tidy up those by themself overtime.

Thank you for that, I did check both ways but cannot find the entry for the BlissOS installation that I deleted. I do see one labelled simply "UEFI OS" as option 3 but I am assuming that is the 'failsafe' (IRC) MX boot option but none for the BlissOS which is the last option still. Am I being blind or is it hiding?

lachelp wrote: Mon Nov 11, 2024 6:34 pm Thank you for that, I did check both ways but cannot find the entry for the BlissOS installation that I deleted. I do see one labelled simply "UEFI OS" as option 3 but I am assuming that is the 'failsafe' (IRC) MX boot option but none for the BlissOS which is the last option still. Am I being blind or is it hiding?

I don't know what you see, so I cannot comment on that.
In case the entry is not listed with "efibootmgr -v", than this is not visible from Linux,
so you may try to remove the entry from with the UEFI firmaware software (aks as BIOS setup).
A "Fallback" entry os sometjhing else, thats's the entry sown with UEFI boot option
list to "boot from the drive", where UEFI would search for the first ESP found
and within the ESP the efi-bootloader /EFI/BOOT/BOOTx64.efi
In case of "MX Linux" or the way you have resetted/regenerated the MX23 boot option,
it will also create the entry /EFI/BOOT/BOOTx64.efi to be identical
to /EFI/MX23/grubx64.efi. Which means you can either select "MX23" or
the fallback bootentry (the drive or whatever the label is used may be "UEFI OS" maybe
something else like the vendor name of the drive.)