I was trying to set up a dual boot with Windows 11 and Arch Linux with systemd-boot as bootloader. I've done it before, but it turns out newer versions of systemd no longer automatically create the "Linux Boot Manager" entry in the motherboard's UEFI, which was news to me.
I attempted to fix this using efibootmgr from outside of the chroot using the same installation USB. It looked like it worked, since running efibootmgr --unicode afterwards showed a "Linux Boot Manager" entry - so I restarted.
It didn't work, but it could still boot into Windows. However, if I now try booting from the same Arch USB in UEFI mode, it hangs on the Aorus logo until I turn off the computer. The USB still boots in legacy mode, however.
It could still boot the Windows 11 USB, so I tried wiping my SSD and reinstalling Windows to see if it would fix it. It didn't. I've tried clearing the CMOS, toggling secureboot so often I've lost count, I've tried a Debian USB (which did work in UEFI mode) an openSUSE Tumbleweed USB (which didn't work in UEFI mode). I've tried different USB sticks, and different USB ports, I've updated the UEFI. I've installed Debian in UEFI mode since its USB worked - none of that has fixed the issue.
Have I screwed up my NVRAM by messing up that efibootmgr command? It seems like some sort of secureboot issue, given that the Windows and Debian USBs work, but the Arch and openSUSE ones don't. Has anybody encountered anything like this before?
My motherboard is the Aorus B450 Pro Wifi, and my SSD is a 1TB Gigabyte NVMe that I've forgotten the SKU number for.
Thanks in advance.