Strangely the EndeavourOS boot option is not in BIOS, perhaps I should try re-doing the boot segment of the commands..?
There should be: Linux Boot Manager.
From what I saw there was only two Windows boot options (still not sure why) and the USB one (where I am currently talking through). Perhaps there was some kind of error in the process..? I mean, something did pop up when I executed the bootctl command, but I was thinking it was more of a warning that the action had been executed.
Boot the live usb again and do this:
sudo mount /dev/nvme0n1p6 /mnt
sudo mount /dev/nvme0n1p5 /mnt/efi
sudo arch-chroo /mnt
bootctl install
reinstall-kernels
If anything pops up, post it here.
Then check with efibootmgr. You should see: Linux Boot Manager
This appeared when I executed bootctl:
Running in a chroot, enabling --graceful.
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/efi/EFI/systemd/systemd-bootx64.efi".
Copied "/usr/lib/systemd/boot/efi/systemd-bootx64.efi" to "/efi/EFI/BOOT/BOOTX64.EFI".
⚠ Mount point '/efi' which backs the random seed file is world accessible, which is a security hole! ⚠
⚠ Random seed file '/efi/loader/random-seed' is world accessible, which is a security hole! ⚠
Random seed file /efi/loader/random-seed successfully refreshed (32 bytes).
Not booted with EFI or running in a container, skipping EFI variable modifications.
Show: efibootmgr
Here:
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 2001,0003,0001,2002,2003
Boot0000* USB HDD: SMI USB DISK PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/HD(1,MBR,0xea64eddc,0x5853c0,0x560
00)RC
Boot0001* Windows Boot Manager HD(5,GPT,4ff5982f-ef7d-44aa-8e73-25e4e9794acf,0xa585cbe,0x400000)/\EFI\Microso
ft\Boot\bootmgfw.efiRC
Boot0003* Windows Boot Manager HD(1,GPT,4d531f9e-9b77-4ce9-b4e9-a30236ed5e53,0x800,0x32000)/\EFI\Microsoft\Bo
ot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b0039006400650
0610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003
400640034003700390035007d00000079000100000010000000040000007fff0400
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
Don’t know why it doesn’t create an entry.
You can try doing it manually following this model, in chroot:
efibootmgr --create --disk /dev/nvme0n1 --part 5 --loader '\EFI\systemd\systemd-bootx64.efi' --label "Linux Boot Manager" --unicode
Alright.. what should I do after that? (by the way here’s the output of efibootmgr, now it seems to show Linux Boot Manager, so I think everything’s fine now..?)
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0002,2001,0003,0001,2002,2003
Boot0000* USB HDD: SMI USB DISK PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/HD(1,MBR,0xea64eddc,0x5853c0,0x56000)RC
Boot0001* Windows Boot Manager HD(5,GPT,4ff5982f-ef7d-44aa-8e73-25e4e9794acf,0xa585cbe,0x400000)/\EFI\Microsoft\Boot\bootmgfw.efiRC
Boot0002* Linux Boot Manager HD(5,GPT,4ff5982f-ef7d-44aa-8e73-25e4e9794acf,0xa585cbe,0x400000)/\EFI\systemd\systemd-bootx64.efi
Boot0003* Windows Boot Manager HD(1,GPT,4d531f9e-9b77-4ce9-b4e9-a30236ed5e53,0x800,0x32000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320
063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000079000100000010000000040000007fff0400
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
Oh my god it worked.. I was honestly thinking I’d have to redo all of the work I put in a few files, but it finally worked!!
I honestly cannot thank you enough.. I really appreciate all of the help you people have given me, and for putting in the effort to help me at all. Also sorry for being quite an inconvenience in a few topics, I’m not used to using the Terminal and messing with my computer’s firmware.
Before I put a solution to this, I’d just like to know if there is any way to prevent anything like this happening. I was thinking that cancelling any Windows 10 updates should work, but I’m not too sure considering how Windows likes to play when there’s more than one distro in your computer.. other than that, my problems are solved!
The most efficient way would be to not dualboot with Windows at all.
I can understand that perhaps that cannot be an option for some users.
I don’t think you can do much about it if Microsoft/Windows decide to remove your Linux boot entry in a future update. If so happens, use this thread as reference and repair your system again.
Hm.. that’s understandable. Thanks again for the help though! I appreciate it, more than you can imagine.
You are welcome! Glad I could help.
i had the same thing happen in the past were i was not able to create/recreate entries in nvram over bootctl command.. and efbootmgr was working.