Successfully installed but no bootloader in BIOS, despite one visible from efibootmgr

Pactman · January 10, 2025, 8:58pm

The first reboot after a successful install by the installer sent me to Window’s BitlLocker, so I tried booting from my BIOS but there’s still no option for the Linux boot manager. I’ve also tried, to no avail:

“reinstall-kernels” after chroot mounting like in https://forum.endeavouros.com/t/endeavour-os-doesnt-show-up-in-boot-menu/49696
Get into the EFI Shell in hope to run systemd-bootx64.efi directly (like https://mricher.fr/post/boot-from-an-efi-shell/), but it seems to be in one of the “BLK” rather than “FS” and so can’t be accessed??? With chroot I know that it exists in efi/EFI/systemd/. The efibootmgr and “bcfg boot dump -b” can also see it.

I’m using a somewhat old Asus with the most up-to-date BIOS available Aptio, from 2019. What do I do now? After hours of “debugging”, during which this forum has really helped, it’s frustrating to be stumped just before the finish line

ricklinux · January 11, 2025, 2:59am

Did you disable bitlocker before installing linux and then re-enable it after the install?

Pactman · January 11, 2025, 5:58am

I just disabled Secure Boot. Shouldn’t that be enough? I think EndeavourOS is on a completely different disk than Windows.

joekamprad · January 12, 2025, 11:18am

OS install was installing with systemd-boot or does it only show grub as bootloader option?
A side from disable secure boot you need to disable legacy boot options also for USB boot called CSM in most cases in the Bios Firmware interface.
https://discovery.endeavouros.com/installation/live-iso-tricks-tips/2021/03/

Could happen that it installs in legacy mode while Bios/efi firmware is set to boots installed OS only in efi mode… aka no boot entry for Bios/MBR legacy installs are shown.

Pactman · January 12, 2025, 6:48pm

I assume there isn’t “CSM” to begin with because the option doesn’t show up where it should according to Asus.

Both systemd and grub are available in Calamares. I just reinstalled with grub instead and the problem persists. In both cases the linux boot manager is in, under the EFI Shell, “DevPath” VenHw(…) and so can’t be “FS0:” into, I think (the Windows one in contrast shows up in HD(2,GPT,…)/EFI/MICROSOFT/BOOT/…) I’m guessing this is a symptom of something wrong but still no idea.

Saw an option not to install a bootloader in the installer. Maybe I should check it and do it manually (somehow)?

joekamprad · January 12, 2025, 7:01pm

Pactman · January 12, 2025, 7:23pm

Mine is in Legacy view and looks like this without the line about CSM. Asus also says if it “… does not have one of the settings below, please skip it and continue with the following steps”.