#editing grub menu
1 messages · Page 1 of 1 (latest)
for some reason, i think you need to configure grub manually, in /etc/grub.d/, then regenerate the config
let me look into it lol
i don't know, this whole system is a bit weird on atomic
well, i'm looking, and i'm certain it's a solvable issue
your issue is relatively minor as far as i'm aware: when starting your device, you currently have to use the uefi boot options to choose windows, rather than doing it from grub
if i'm understanding rightly, this is like p2 at best
that's a separate thing
do you want to look at that first?
so it seems that to get grub2-mkconfig working, you need to disable composefs due to a bug
it seems like there are no docs yet https://forge.fedoraproject.org/atomic-desktops/tracker/issues/73
https://github.com/fedora-silverblue/issue-tracker/issues/284 exists, but Timothee Ravier (don't ping him here) says:
It is unlikely that we'll get work done on dual boot support in GRUB so we should recommend users create distinct EFI & boot partition for each systems and use the EFI firmware settings to select the system to boot.
so the currently supported situation is what you're doing right now - if you decide to keep using secureblue, i'd just chill out, set your favourite one as the default (first in the boot order), and either use bootnext or the uefi boot menu
isn't that what you're already doing?
i think "using the EFI firmware settings to select the system to boot" just means smashing F2 or F12 during startup, and then choosing your desired OS
no worries :)