On Wed, 30 Mar 2022 00:59:54 +1000 "Michael D. Setzer II via users" <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > Machine that doesn't timeout boot, before it has a similar > saved_entry, but tried resetting it to 0 to boot from 1st > one. > > grub2-editenv list > saved_entry=0 > boot_success=1 > boot_indeterminate=0 > > This notebook that works fine > grub2-editenv list > saved_entry=189711f94e78436d9618b891a8fce70e-5.16. > 17-100.fc34.x86_64 > boot_success=1 > boot_indeterminate=0 I haven't had to examine grub for a long time. So, I'm not familiar enough with it to say what is incorrect. What do the successful and failing system have in /etc/default/grub ? I think if you put the line GRUB_DEFAULT=saved in that file on the failing machine, and then run grub2-mkconfig -o grub.cfg on the failing machine in the directory where the grub.cfg is, it will start booting properly again. The location of grub.cfg *should* be in /boot/grub2/ unless the machines are booting EFI. Then the grub.cfg will be in /boot/efi/EFI/fedora. This has changed since f34 so that grub.cfg is *always* in /boot/grub2/ now. If you install / have installed pinfo, you can get lots of information about grub by running pinfo grub2 Arrow keys will move around, space will move to links. _______________________________________________ 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 on the list, report it: https://pagure.io/fedora-infrastructure
