Bug 2020950
| Summary: | Grub2 Menu 'scanlines' on Framework laptop | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | amanzer | ||||||||
| Component: | grub2 | Assignee: | Javier Martinez Canillas <fmartine> | ||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | low | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 35 | CC: | be.0, fmartine, hdegoede, lkundrak, pjones, rharwood | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2022-01-28 13:07:58 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
> Running `sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg` resolves the problem by generating a better grub.cfg than the default.
Please provide both the old and new grub.cfg.
Created attachment 1840756 [details]
The default (bad) grub.cfg
This is the grub.cfg that is installed by `grub2-common` package
Created attachment 1840757 [details]
The better generated grub.cfg
This is the grub.cfg as generated by `grub2-mkconfig`.
I also run into this bug on a Lenovo Yoga 920 laptop. Thank you for your bugreport. I hit the same issue myself and I've written a set of patches fixing this and submitted it upstream and downstream: https://lists.gnu.org/archive/html/grub-devel/2022-01/msg00169.html https://github.com/rhboot/grub2/pull/95 If you want to test the fix, here is a build of the latest fedora-36 branch of grub with the fixes included: https://fedorapeople.org/~jwrdegoede/rhbz1946969/grubx64.efi To test this backup /boot/efi/EFI/fedora/grubx64.efi (in case the new one does not work) and then copy the linked file to /boot/efi/EFI/fedora/grubx64.efi with it. Note this is not signed and as such you will need to disable secure-boot to test this. Warning disabling secureboot and running semi-random binaries from the internet is not the best idea from a security pov. If you do decide to give this a test, please don't forget to restore the original /boot/efi/EFI/fedora/grub.cfg . Note the menu looks slightly different in the fedora-36 branch, because a couple of downstream patches which tweak the menu look have been dropped to bring us closer to the upstream grub sources. This same issue has been reported before as bug 1946969, so I'm marking this bug as a duplicate of that one. *** This bug has been marked as a duplicate of bug 1946969 *** |
Created attachment 1840565 [details] Both grub.cfg files produced by default by grub2-common, and by grub2-mkconfig Description of problem: I've installed Fedora 34, and now 35 on the Framework laptop. In the default configuration, when grub boots, it first prints the boot selection menu, but then also prints what look like SPACE characters in a kind of scan-line pattern over the entire screen before starting the selection timeout. During this time, grub is unresponsive to UP/DOWN key presses, but queues them up and replays them once the timeout starts. Running `sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg` resolves the problem by generating a better grub.cfg than the default. Version-Release number of selected component (if applicable): 2.06-8 (latest at time of submission) 2.06-6 How reproducible: Always Steps to Reproduce: 1. Install/Reinstall `grub2-common` package 2. Reboot Actual results: Grub produces 'scan lines' across the entire screen Expected results: Grub timeout should start as soon as the menu entries are printed Additional info: I'm not sure if this is a Fedora bug, or a Grub bug, but given that regenerating the grub config resolves the issue, I feel like this might be a Fedora packaging error. I own a Framework laptop and would be happy to test proposed solutions.