Sure, but that was kind of a “workaround” to get the grub to recognize other systems installed with btrfs on a dual/multi -boot system.
I suspect there is something with the generation of the menuentries that fails. That is, something perhaps failing with grub-mkconfig. The os-prober part seems to run okay and discovers the other system. Don’t know.
I can only say one thing. I have gone through this grub thing so many times and I don’t find it that easy to understand how it works. For me there was always a problem with certain distros. When I was using Antergos I also had Manjaro installed with Windows 10 and I let Manjaro control the boot. It always seemed to work. But, I have done a lot of multiboot where grub is always an issue with microcode or something.
Endeavour works good under most but not all scenarios. So I like what I have now because I don’t have that problem! Each grub I have now is on its own installation of Btrfs onLuks or without Encryption and I am using rEFInd and booting with grubx64.efi as opposed to the vmlinux-limux image for UEFi. I like it and grub is a non issue for me unless I do a normal install then the grub picks it up. If it’s installed using @2000 Btrfs setup they are minding their own business! I also have them on separate drives.
Generating grub configuration file …
Found theme: /boot/grub/themes/EndeavourOS/theme.txt
Found linux image: /boot/vmlinuz-linux-zen Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot: initramfs-linux-zen-fallback.img
Found linux image: /boot/vmlinuz-linux Found initrd image: /boot/intel-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: initramfs-linux-fallback.img
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
So all is good now.
But how come at the first place …?
@ricklinux, I think I will need to get my act together and have a look at rEFInd some day soon. I don’t seem to be able giving up on multi-booting any time soon
Well I’m liking it with this Btrfs setup that @2000 has done. Although I may not totally understand it. It’s like EndeavourOS. I know that it works. A lot of stuff doesn’t. At least from my perspective as a normal user. For most people they aren’t the Linux gurus or Arch Elites. They just want to install something that works with no issues. This is why I like EndeavourOS because it’s mostly KISS! You want something fancy …you need to do it.
If I remember correctly, indeed not having intel-ucode really installed was a problem with a recent ISO. Which ISO did you use for installing?
Anyway, installing intel-ucode manually should fix that issue (as it did for you).
I used the older ISO (the one before the current one) and used the offline install and updated the system after the installation. Now that you mention it, I remember that I have come across some topic regarding this issue in the forum. So that explains why pacman -Qi and pacman -Ql showed that the intel-ucode was iinstalled and the intel-ucode.img present in /boot while it wasn’t in reality.
Thanks @manuel for pointing it out!
And thank you @all for your help and support!