Hi, I stumbled on this yesterday. Anaconda using Legacy boot commands on EFI non-Fedora systems? https://ask.fedoraproject.org/en/question/90308/anaconda-using-legacy-boot-commands-on-efi-non-fedora-systems/ The bugs I've found that relate: https://bugzilla.redhat.com/show_bug.cgi?id=1161749 https://bugzilla.redhat.com/show_bug.cgi?id=859285 https://bugzilla.redhat.com/show_bug.cgi?id=1108344 https://bugzilla.redhat.com/show_bug.cgi?id=1173993 The issue as I understand it, Fedora's GRUB doesn't include linux and initrd grub commands. On UEFI it's linuxefi and initrdefi. One BIOS it's linux16 and initrd16. The bug is if the linux and initrd commands don't exist (which I think they don't with Fedora's GRUB), and if the Fedora GRUB grub2-mkconfig command produces a grub.cfg where non-Fedora linux menu entries use linux and initrd commands (that don't exist). It might end up being an osprober bug? But I see these bootloader commands in /etc/grub.d/ scripts, not in osprober. There is no release criteria for dual boot Fedora + some other Linux. It only applies for Windows and macOS. But it's also a regression, because this used to work. And there's no good user friendly work around on BIOS, and using the UEFI boot manager to choose the other OS's flavor of GRUB is suboptimal. But if this is just some script changes, it should be straight forward to fix. -- Chris Murphy -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://lists.fedoraproject.org/admin/lists/test@xxxxxxxxxxxxxxxxxxxxxxx
