Created attachment 1941302 [details] _ Command Description of problem: Grub 2 stuck on "_" command and enters frequent boot loop Version-Release number of selected component (if applicable): How reproducible: Very Steps to Reproduce: 1. Download Fedora Silver Blue 38 Rawhide 20230126.n.0 compose 2. Try to install OS to VM or bare metal. 3. Actual results: It goes back to the grub2 options menu. Expected results: It will load up the installer Additional info:
Created attachment 1941303 [details] Back to grub2 boot screen This is a screenshot of my VM of Fedora Silverblue 38 Rawhide being redirected back to grub2 boot menu. I am not too sure what is causing this issue.
Proposed as a Freeze Exception for 38-beta by Fedora user ahmedalmeleh using the blocker tracking app because: Description of problem: Grub 2 stuck on "_" command and enters frequent boot loop for grub2 menu. Version-Release number of selected component (if applicable): How reproducible: Very Steps to Reproduce: 1. Download Fedora Silver Blue 38 Rawhide 20230126.n.0 compose 2. Try to install OS to VM or bare metal. 3. Watch the boot loop for grub2 menu. Actual results: It goes back to the grub2 options menu. Expected results: It will load up the installer
This isn't happening in openQA - both BIOS and UEFI test installs work fine. If you hit 'e' to edit the boot parameters and remove 'rhgb quiet' then boot, you might see more information about what's going wrong...
Created attachment 1941404 [details] Works now Removing rhgb quiet seems to resolve the issue and I am able to access the boot screen. I think maybe as a patch for the next compose we should remove that "rhgb quiet"
Created attachment 1941405 [details] Works now It works now Removing rhgb quiet seems to resolve the issue and I am able to access the boot screen. I think maybe as a patch for the next compose we should remove that "rhgb quiet"
well, no, we're not going to do that. we don't want to show detailed boot messages on all boots (it looks ugly and scary) and we do want to show the graphical bootsplash (which is what rhgb does). your system not booting with rhgb (it's probably rhgb) is a bug, if that's reproducible. the fix would be to find the bug and fix it, not just turn it off for everyone.
I see although some distros like detailed messages. thanks for clarifying, I am not too sure how that fixed my one though.
rhgb I believe toggles whether to use plymouth. If enabling plymouth fails your boot, perhaps maintainers of that package might be able to help more. By the time it's executing, grub is done. And since I can't reproduce or get error logs, there isn't going to be anything we can do from grub2 anyway...
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle. Changing version to 38.
-4 in https://pagure.io/fedora-qa/blocker-review/issue/1030 , marking rejected FE.