will run # grub-mkconfig -o /boot/grub/grub.cfg to update GRUB
Could you confirm @ricklinux if its ok?
No update-grub here it seems hahaha
Say what? This one! This ain’t Ubuntu! 
sudo grub-mkconfig -o /boot/grub/grub.cfg
That is of course a necessary step in “normal” cases. Here the problem is that the efi boot entry for EnOS doesn’t get “registered” in UEFI settings. That’s a must for the machine to be able to find the bootloader and boot up the system.
1 Like
It appears to be something missing
[liveuser@eos-2021.08.27 ~]$ sudo grub-mkconfig -o /boot/grub/grub.cfg
/usr/bin/grub-probe: error: failed to get canonical path of `airootfs'.
Sometimes the reason too why grub doesn’t get installed is because UEFI has too many entries and gets full. Sometimes it needs to be cleared of some useless entries or old entries. Just saying…may not be the issue here!
That is because you are not in the chroot.
1 Like
Stay in chroot or lose the boot!
Edit: I couldn’t help myself! 
3 Likes
Could this be one of those CMOS failing battery moments?
Chroot needs to be there (noted )
Here is my output for the grub update
[root@EndeavourOS liveuser]# arch-chroot /mnt
[root@EndeavourOS /]# sudo grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Found theme: /boot/grub/themes/EndeavourOS/theme.txt
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-linux-lts.img
Found fallback initrd image(s) in /boot: intel-ucode.img amd-ucode.img initramfs-linux-lts-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: intel-ucode.img amd-ucode.img initramfs-linux-fallback.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
Repeating
[root@EndeavourOS /]# efibootmgr -v
BootCurrent: 0005
Timeout: 2 seconds
BootOrder: 2003,2001
Boot0000* ubuntu HD(1,GPT,5bd5d652-b9af-46ec-97f3-0b4b8f104979,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0001* UEFI: IP6 Realtek PCIe FE Family Controller PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/MAC(d897ba884061,0)/IPv6([::]:<->[::]:,0,0)..BO
Boot0002* UEFI: IP4 Realtek PCIe FE Family Controller PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/MAC(d897ba884061,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0004* UEFI: IP4 Realtek PCIe FE Family Controller PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/MAC(d897ba884061,0)/IPv4(0.0.0.00.0.0.0,0,0)..BO
Boot0005* UEFI: Generic Flash Disk 8.07 PciRoot(0x0)/Pci(0x14,0x0)/USB(2,0)/USB(2,0)/HD(2,GPT,31323032-3830-4632-b232-303331313431,0x3a80bc,0x31000)..BO
Boot2001* EFI USB Device RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network RC
I guess the limit of entries for GRUB could be reached. That is why EnOS is not appearing.
Since My boot order has Newtork first i guess that is what fills up the grub menu.
Should I try to change boot order? Or erase those IP4 IP6 entries?
I would remove 1,2,4 at least. No harm trying.
1 Like
Could you post the content of grub.cfg from within chroot?
cat /boot/grub/grub.cfg
I mean if nothing helps to get the EnOS’ efi entry in UEFI settings, one option could be to use (K)Ubuntu’s grub to boot EnOS by creating a custom.cfg for EnOS in Kubuntu’s /boot/grub.
Did he change os-prober settings?
not yet, saw that did something. I read the warning during install.
Very large output. Anything to look for with grep? I’d rather not bloat the forum.
1 Like
cat /etc/default/grub | eos-sendlog
Here it is:
[root@EndeavourOS grub]# cat /etc/default/grub | eos-sendlog
https://clbin.com/wpJYz
Edit- Just needed the link
1 Like
You just needed to post the link!
@pebcak
Looks like the os-prober line isn’t there.
Edit: Is os-prober installed also?
I guess that won’t matter at this stage, the main issue being the EnOS’ efi boot entry not getting “registered”. Or what do you think? I mean installing os-prober etc. can be done later when the system is up and running.
1 Like
I already installed and updated grub. I guess I could just reboot now.
If that doesn’t work, I’ll change boot order (put Network last), and clear some entries of grub menu. If not, i’ll try what you said about doing the config in ubuntu.
Edit- typo
1 Like