On Mon, Jun 3, 2024 at 3:11 AM Patrick Dupre via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > I updated a fedora 38 installation to 40 (on sdc3) as I used to do. > But this installation is now not visible from the grub bot menu. > I run grub2-mkconfig -o /boot/grub2/grub.cfg > again, and again from both installation (40 and 38 on sda4). > > The output seems OK (Fedora 40 found from fedora 38, and fedora 38 found > from fedora 40). > os-prober OK > cf > /dev/sdc3:Fedora Linux 40 (Forty):Fedora1:linux (from fedora 38) > > The only way to start fedora 40 is to boot from super grub2 > If I understand UEFI does not see the fedora 40 installation > > It looks that the information from > grub2-mkconfig > are never made available to the grub boot I ran into something similar installing Fedora 39 under KVM. To make it work I had to make sure the VM was configured for UEFI. I did not pursue trying to get to boot as BIOS. -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
