Bug 920380 - Graphical menu screen garbled on thinkpad T400
Summary: Graphical menu screen garbled on thinkpad T400
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: grub2
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: RejectedFreezeException
Depends On: 858192
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-11 23:48 UTC by Lubos Kocman
Modified: 2015-02-17 14:51 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 858192
Environment:
Last Closed: 2015-02-17 14:51:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 701111 0 None None None Never

Description Lubos Kocman 2013-03-11 23:48:34 UTC
Having the same issue with t400 on grub2-2.00-13.fc18.x86_64
+++ This bug was initially created as a clone of Bug #858192 +++

Created attachment 613937 [details]
photo of grub menu

Description of problem:
Initial graphical menu screen is totally corrupted (see photo). The hardware is Thinkpad T400, with Intel GPU and 1440x900 panel.

Version-Release number of selected component (if applicable):
grub2-2.0-0.38.beta6.fc17



Additional info:
This bug apparently is NOT Fedora-specific. It wasn't fixed in other distribution, sadly:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/701111

--- Additional comment from Mads Kiilerich on 2012-09-18 15:24:10 EDT ---

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

--- Additional comment from Tomasz Torcz on 2012-09-18 15:45:21 EDT ---

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."

--- Additional comment from Tomasz Torcz on 2012-09-18 15:45:47 EDT ---

Created attachment 614109 [details]
vbeinfo-002

--- Additional comment from Tomasz Torcz on 2012-09-18 15:46:12 EDT ---

Created attachment 614110 [details]
vbeinfo-003

--- Additional comment from Mads Kiilerich on 2012-09-18 16:01:24 EDT ---

(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.

--- Additional comment from Tomasz Torcz on 2012-09-24 17:22:18 EDT ---

Created attachment 616737 [details]
dmesg from boot with GFXMODE=1440x900x16

1400x900x16 do not work

--- Additional comment from Tomasz Torcz on 2012-09-24 17:22:51 EDT ---

Created attachment 616738 [details]
dmesg from boot wihout any specific GFXMODE

--- Additional comment from Tomasz Torcz on 2012-10-10 07:51:27 EDT ---

Problem persist with grub2-2.00-9.fc18.x86_64

--- Additional comment from Tomasz Torcz on 2013-01-04 07:15:24 EST ---

Any progress on this?

Comment 1 Adam Williamson 2013-03-27 18:12:54 UTC
Discussed at 2013-03-27 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-03-27/f19alpha-blocker-review-3.2013-03-27-16.01.log.txt . Rejected for now: we agreed we do not want to touch this at least without some kind of concrete analysis of the bug and a possible fix. Please re-propose if some kind of fix for this actually turns up during a freeze.

Comment 2 Paul Bolle 2014-01-02 20:29:18 UTC
0) Still reproducible after a reinstall of grub2 using grub2-2.00-25.fc20.x86_64. For what it's worth: bios-version is "7UET79WW (3.09 )".

1) Adding
    GRUB_GFXMODE=1280x800

to /etc/default/grub and doing the grub2-mkconfig dance gives a usable grub2 menu in gfxterm mode.

2) Bug #825506 looks identical, by the way.

Comment 3 Tomasz Torcz 2014-01-02 20:50:21 UTC
Mine: 	Version: 7UET94WW (3.24 )
Please upgrade your BIOS first.

Comment 4 Paul Bolle 2014-01-02 20:53:46 UTC
(In reply to Tomasz Torcz from comment #3)
> Please upgrade your BIOS first.

Could you please elaborate?

Comment 5 Fedora End Of Life 2015-01-09 17:45:56 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.

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.

Comment 6 Fedora End Of Life 2015-02-17 14:51:22 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.