I had dual boot working on this setup at one point with Silverblue 39. So it may have been the installer messing something up, or it may be something else. How can I confirm that I am using EFI boot?
Edit: From the docs, [ -d /sys/firmware/efi ] && echo UEFI || echo BIOS confirms I am using UEFI.
I spent an hour or so trying to fix this today. It’s difficult because different docs offer different course of actions and some don’t match the setup the atomic spins have. It’s frustrating and this may be the deal break for me and immutable desktops.
My understanding is that you can fix this manually but beyond that a lot of the suggestions I’ve found haven’t worked for me. os-prober returns no output so it’s not as simple as running that and regenerating the grub config.
I’ve been looking into what happened and my understanding is that Anaconda doesn’t play nice with the existing Windows EFI boot (or other OSes) and blows it away and makes it own.
Is there a reason you can’t use the UEFI boot menu to select the other OS?
No because I was partitioning one drive and now the only UEFI boot on it is the Bazzite (Kinoite) one.
This is known issue with Anaconda and it sounds like the reason things like os-prober and grub2-mkconfig weren’t adding Windows is because the Windows boot got wiped.
To answer my original question, the Atomic distros use the same process as standard Fedora to configure Grub. I was just thinking I was doing something wrong because of the aft-for mentioned issue.