0003 is not active, remove it also, it’s the same than 0008
efibootmgr -b 3 -B
0003 is not active, remove it also, it’s the same than 0008
efibootmgr -b 3 -B
i did like this:
efibootmgr -b 0004 -B
without sudo
look UP
efibootmgr -b x -B and not efibootmgr -b xxxx -B
Boot0001* EndeavourOS HD(1,GPT,5f774f65-6102-4e95-9fe0-06fb49f7d6e1,0x800,0x96000)/File(ࠜEFIEndeavourOSgrubx64.efi)
Looks like you missed some \ : EFIEndeavourOSgrubx64.efi >> \EFI\EndeavourOS\grubx64.efi
If
sudo efibootmgr -c -d /dev/nvme0n1 -p 1 -w -L EnOS -l “\EFI\EndeavourOS\grubx64.efi”
‘’
doesn’t get it right, remove the “quotes” and try again.
sudo efibootmgr -c -d /dev/nvme0n1 -p 1 -w -L EndeavourOS -l \EFI\EndeavourOS\grubx64.efi
efibootmgr: ** Warning ** : Boot0001 has same label EndeavourOS
BootCurrent: 0008
Timeout: 1 seconds
BootOrder: 0002,0001,0008,0000,0003
Boot0000* Windows Boot Manager
Boot0001* EndeavourOS
Boot0003 Fedora
Boot0008* Fedora
Boot0002* EndeavourOS
$ efibootmgr -v
BootCurrent: 0008
Timeout: 1 seconds
BootOrder: 0002,0001,0008,0000,0003
Boot0000* Windows Boot Manager HD(1,GPT,5f774f65-6102-4e95-9fe0-06fb49f7d6e1,0x800,0x96000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...,................
Boot0001* EndeavourOS HD(1,GPT,5f774f65-6102-4e95-9fe0-06fb49f7d6e1,0x800,0x96000)/File(ࠜEFIEndeavourOSgrubx64.efi)
Boot0002* EndeavourOS HD(1,GPT,5f774f65-6102-4e95-9fe0-06fb49f7d6e1,0x800,0x96000)/File(EFIEndeavourOSgrubx64.efi)
Boot0003 Fedora HD(1,GPT,5f774f65-6102-4e95-9fe0-06fb49f7d6e1,0x800,0x96000)/File(\EFI\FEDORA\SHIM.EFI)..BO
Boot0008* Fedora HD(1,GPT,5f774f65-6102-4e95-9fe0-06fb49f7d6e1,0x800,0x96000)/File(\EFI\FEDORA\SHIM.EFI)..BO
delete Boot0001?
Looks again that \ are missing. I don’t know why.
It’s still not good with the link on 0001 and 0002 !
We have to obtain File \EFI\EndeavourOS\grubx64.efi and not FileEFIEndeavourOSgrubx64.efi
I believe is due to the double quote " that couldn’t get the antislash \ then try it with simple quote '
like this:
sudo efibootmgr -c -d /dev/nvme0n1 -p 1 -w -L EnOS -l '\EFI\EndeavourOS\grubx64.efi'
This
Yes, and 0002 as well.
efibootmgr -v
BootCurrent: 0008
Timeout: 1 seconds
BootOrder: 0001,0002,0008,0000,0003
Boot0000* Windows Boot Manager HD(1,GPT,5f774f65-6102-4e95-9fe0-06fb49f7d6e1,0x800,0x96000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...,................
Boot0001* EndeavourOS HD(1,GPT,5f774f65-6102-4e95-9fe0-06fb49f7d6e1,0x800,0x96000)/File(\EFI\EndeavourOS\grubx64.efi)
Boot0002* EndeavourOS HD(1,GPT,5f774f65-6102-4e95-9fe0-06fb49f7d6e1,0x800,0x96000)/File(EFIEndeavourOSgrubx64.efi)
Boot0003 Fedora HD(1,GPT,5f774f65-6102-4e95-9fe0-06fb49f7d6e1,0x800,0x96000)/File(\EFI\FEDORA\SHIM.EFI)..BO
Boot0008* Fedora HD(1,GPT,5f774f65-6102-4e95-9fe0-06fb49f7d6e1,0x800,0x96000)/File(\EFI\FEDORA\SHIM.EFI)..BO
remove the 0002 now and you are ok
efibootmgr -b 0002 -B
Boot0001* EndeavourOS HD(1,GPT,5f774f65-6102-4e95-9fe0-06fb49f7d6e1,0x800,0x96000)/File(\EFI\EndeavourOS\grubx64.efi)
Looks good!
Before rebooting do I need to do this grub2-mkconfig -o /boot/grub2/grub.cfg
?
Before to reboot remove 0002 then update grub, it doesn’t kill a rabbit !
Show us before reboot to be sure…
If you want EnOS’s Grub to be in charge of the booting the other OS’s, then you need to run this when you boot into EnOS as well.
By the way, welcome to the forum and good luck with your endeavour.
What exactly needs to be shown?
efibootmgr -v
This is exactly what I want, please tell me how to do it !!! ???
From your efibootmgr -v, it looks you got both the boot entry and the boot order right. I would just reboot the system and boot into the EnOS and update it’s grub there.
$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Found Arch Linux on /dev/nvme0n1p6
Adding boot menu entry for EFI firmware configuration
done
$ efibootmgr -v
BootCurrent: 0008
Timeout: 1 seconds
BootOrder: 0001,0008,0000
Boot0000* Windows Boot Manager HD(1,GPT,5f774f65-6102-4e95-9fe0-06fb49f7d6e1,0x800,0x96000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...,................
Boot0001* EndeavourOS HD(1,GPT,5f774f65-6102-4e95-9fe0-06fb49f7d6e1,0x800,0x96000)/File(\EFI\EndeavourOS\grubx64.efi)
Boot0008* Fedora HD(1,GPT,5f774f65-6102-4e95-9fe0-06fb49f7d6e1,0x800,0x96000)/File(\EFI\FEDORA\SHIM.EFI)..BO
When you want to change order just use like this:
efibootmgr -o x,x
Everything is ok, so reboot to see what we got !
This will tell that your next reboot would be on 0001 EnOS in your example:
efibootmgr -n 1