Description of problem: AArch64 disk images in rawhide currently default to the 'System Setup' grub menu entry on aarch64. On most SBC's this results in a failed boot and requires user intervention to select the kernel entry for a successful boot. Version-Release number of selected component (if applicable): grub2-2.02-69.fc30 How reproducible: Everytime. Steps to Reproduce: 1. Boot a recent aarch64 rawhide disk image on an SBC or in Qemu 2. System will default to the 'System setup' entry
Hello Paul, Could you please share the content of the /etc/grub2-efi.cfg and /boot/grub2/grubenv files, and also the BLS snippets in /boot/loader/entries?
Created attachment 1536412 [details] grub2-efi.cfg
Created attachment 1536413 [details] grubenv
No snippets in /boot/loader/entries
Thanks a lot for the info, the problem is that your grub2-efi.cfg has the following snippet: if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="1" fi While this usually is: if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="${saved_entry}" fi Since default is set to 1, and you only have the Fedora (5.0.0-0.rc6.git1.1.fc30.aarch64) 30 (Rawhide) boot entry, the default is set to to the one with index 1 (System setup). The grubby tool changes the default in the GRUB config file if you do grubby --set-default, so maybe you did this? You could either re-generate your grub2-efi.cfg again with grub2-mkconfig -o /etc/grub2-efi.cfg or set your default to 0 with grubby --set-default=/boot/vmlinuz-5.0.0-0.rc6.git1.1.fc30.aarch64.
Fixed in Fedora-30-20190224.n.0, thanks (again) Javier!