Bug 858192
Summary: | Graphical menu screen garbled on thinkpad T400 | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tomasz Torcz <tomek> | ||||||||||||||
Component: | grub2 | Assignee: | Peter Jones <pjones> | ||||||||||||||
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||
Priority: | unspecified | ||||||||||||||||
Version: | 20 | CC: | dcantrell, dennis, mads, pjones | ||||||||||||||
Target Milestone: | --- | ||||||||||||||||
Target Release: | --- | ||||||||||||||||
Hardware: | Unspecified | ||||||||||||||||
OS: | Unspecified | ||||||||||||||||
Whiteboard: | |||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||
Clone Of: | |||||||||||||||||
: | 920380 (view as bug list) | Environment: | |||||||||||||||
Last Closed: | 2013-08-26 11:56:55 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: | |||||||||||||||||
Bug Depends On: | |||||||||||||||||
Bug Blocks: | 920380 | ||||||||||||||||
Attachments: |
|
Description
Tomasz Torcz
2012-09-18 09:50:48 UTC
Does it work when adding to /etc/default/grub something like GRUB_GFXMODE=1024x768 and running grub2-install /dev/sda grub2-mkconfig -o /boot/grub2/grub.cfg ? If so: Please show the grub commandline output of set pager=1 vbeinfo Created attachment 614108 [details]
vbeinfo-001
It did work. I'm attaching photos of vbeinfo (I hope those are readable enough).
BTW, Ubuntu bugreport contains this comment:
"This is happening because the VBE BIOS advertises a 1440x900x32 mode (and even advertises 1440x900 as the best mode, though I don't think EDID is specific about the preferred depth) but fails to program it correctly. I don't know what the best solution to this is as yet."
Created attachment 614109 [details]
vbeinfo-002
Created attachment 614110 [details]
vbeinfo-003
(I thought the * in vbeinfo pointed at the default menu ... but apparently it points at the current mode.) Do 1400x900x16 work? Please also attach a dmesg from a system that has been booted with the default non-working grub mode. Created attachment 616737 [details]
dmesg from boot with GFXMODE=1440x900x16
1400x900x16 do not work
Created attachment 616738 [details]
dmesg from boot wihout any specific GFXMODE
Problem persist with grub2-2.00-9.fc18.x86_64 Any progress on this? This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Problem still exists. grub2-2.00-25.fc20.x86_64 Oh well... the problem was fixed by upgrading BIOS to version 7UET94WW (3.24) 10/17/2012. |