You are not logged in.
Hi folks, I am new to Arch and have had a lot of challenges getting my first install to boot.
My biggest hurdle was that, following the Install guide, I used efibootmgr to pass '--loader=\vmlinuz-linux' to the firmware. It needed to be vmlinuz-linux.efi, because UEFI needs the .efi extension. Or I guess on many / most implementations? Or just mine. I dunno.
Main issue now is: I can apparently only add a single boot entry via efibootmgr. I'm interested in sticking various kernels on this box and adding a boot entry for each, and switching by going into firmware configuration, as is a suggested possibility in some places (like https://www.rodsbooks.com/efi-bootloaders/efistub.html). But as it stands now, if I add a second entry, upon booting, only the most recent one is in there.
I'm curious if there is some option with efibootmgr or other tool or trick I can use. Like maybe the entries are only put in one area of NVRAM or something. Or is this something specific to my BIOS. Do I just not have enough NVRAM to support more than one entry added this way?
FWIW I have an old-ish mini PC with AMI Aptio BIOS, I upgraded it to F9 which seems to be the most recent. CSM and Secure Boot are both off.
Thanks.
Offline
efibootmgr certainly does not have that limitation on this system. I have six options set on this Asus Vivobook as I type this. It could be a limitation of your system; older systems seem to be worse than contemporary systems.
Your only choice may be to use an EFI aware boot loader such as GRUB or rEFInd
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
I never really thought it was a problem with efibootmgr. Maybe my firmware just has a very small bit of nvram?
I wish it ere easier to find all tis stuff out.
Offline
It does sound like a problem with lack of storage. It is a tale often told -- many manufacturers of laptops release sub-optimum firmware for things such as DSDT, ACPI, uEFI; the only criteria being that they can support MS Windows on the platform. Often they only way to change things such as Secure boot or to update system firmware are through Windows or user space programs that run on Windows. Some are better than others.
As I say, you may want to look at rEFInd. It can be a little trouble to set up, but it is a solid boot loader with a fairly nice user interface.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline