Bug 711582 - i915: Bad screen colours with F15 kernel, regression compared to F14.
Summary: i915: Bad screen colours with F15 kernel, regression compared to F14.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 16
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-07 19:44 UTC by Maciej Żenczykowski
Modified: 2013-02-13 07:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 07:55:50 UTC
Type: ---


Attachments (Terms of Use)

Description Maciej Żenczykowski 2011-06-07 19:44:42 UTC
Description of problem:

When my system boots with the F15 kernel (kernel-2.6.38.6-27.fc15.x86_64) the display suffers from a 'black is green' problem, which isn't present when booted with the F14 kernel (kernel-2.6.35.12-90.fc14.x86_64).

The problem shows up during boot at the moment when it switches into graphical mode (ie. it happens before X boots, during i915 kernel module initialization).

System in question is a Shuttle SG33G5M Deluxe with an Intel built in graphics card.

# lspci -nn
00:02.0 VGA compatible controller [0300]: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 02)

The driver appears to be 'fbcon: inteldrmfb' and 'i915'.

The greenness makes white-on-black text mode hard to use, and effectively makes X unusable (you can barely tell the colours apart)

At a guess this is some sort of RGB vs CMYK vs YCbCr or byte ordering problem.  All the pixels are at the right location, it's just their colours that are totally off.


Perhaps relevant error messages:

[drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
...
[drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved]
...


What sort of information can I provide to help debug this further?

Thanks.

Comment 1 Maciej Żenczykowski 2011-06-08 15:39:33 UTC
Still happens with 2.6.38.7-30.fc15.x86_64

Comment 2 Maciej Żenczykowski 2011-06-08 15:50:34 UTC
Still happens with 2.6.38.8-31.fc15.x86_64

Comment 3 Maciej Żenczykowski 2011-06-08 16:02:27 UTC
Please note that 2.6.36.2-12.rc1.fc15.x86_64 is OK.

Please note that 2.6.37-2.fc15.x86_64 is *NOT* OK.

This presumably means that this regression happened in 2.6.37.

Comment 4 Maciej Żenczykowski 2011-06-08 16:23:54 UTC
2.6.37-0.rc5.git2.1.fc15.x86_64 <- busted (oops in i915 driver, never switches to graphics mode)
2.6.37-0.rc7.git0.1.fc15.x86_64 <- busted (oops in i915 driver, never switches to graphics mode)
2.6.37-1.fc15.x86_64 <- *NOT* ok

Comment 5 Maciej Żenczykowski 2011-06-24 09:58:49 UTC
AFAICT, this breaks before X even starts to load.
It breaks as soon as the kernel switches into graphics mode during boot (ie. when it switches to graphical frame buffer console by loading the i915 fb module, while it's still printing out the text boot messages [non quiet boot]).

# cat /proc/cmdline 
ro root=LABEL=X:ROOT acpi_enforce_resources=lax SYSFONT=latarcyrheb-sun16 LANG=en_US.utf8 KEYTABLE=us

As such I'm not convinced this should be classified to xorg-x11-drv-intel.

Comment 6 Maciej Żenczykowski 2011-08-03 08:44:08 UTC
Still broken with kernel-2.6.40-4.fc15 from koji.

But apparently no-one even looks here.

Comment 7 Maciej Żenczykowski 2012-06-06 15:43:15 UTC
still broken with all kernels I've bothered to check from fc16

Comment 8 Fedora End Of Life 2013-01-16 09:56:15 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Fedora End Of Life 2013-02-13 07:55:53 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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.