Bug 722789 - Intel G35 chipset graphics are all too green (KernelModeSetting problem)
Summary: Intel G35 chipset graphics are all too green (KernelModeSetting problem)
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-17 20:45 UTC by Jani Ollikainen
Modified: 2012-11-13 15:15 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-13 15:15:04 UTC
Type: ---


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 39314 0 None None None Never

Description Jani Ollikainen 2011-07-17 20:45:40 UTC
Description of problem:
When booting up after kernel does modeset it goes all too green!
Booting up with "nomodeset" everything doesn't go so green.

Version-Release number of selected component (if applicable):
kernel-2.6.38.8-36.fc15.i686
kernel-3.0-0.rc7.git3.1.fc16.i686

How reproducible:
Boot with it.

Steps to Reproduce:
1. Have G35 chipset
2. Boot Fedora 15
  
Actual results:
Too green!

Expected results:
Not so green!

Additional info:
Works with Fedora 14 kernel kernel-2.6.35.13-92.fc14.i686.
So some patches after that kernel has broken it!

00:02.0 VGA compatible controller: Intel Corporation 82G35 Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation 82G35 Express Integrated Graphics Controller (rev 03)

Comment 1 Jani Ollikainen 2011-07-17 21:18:03 UTC
Filed also a bug to as instructed at #intel-gfx/freenode:
https://bugs.freedesktop.org/show_bug.cgi?id=39314

Comment 2 Jani Ollikainen 2011-09-01 16:24:08 UTC
Confirme that the fixes they have made that are in Linux 3.1-rc4 will fix the problem.

So waiting those fixes to arrive to Fedora....

Comment 3 Josh Boyer 2011-09-01 17:14:10 UTC
(In reply to comment #2)
> Confirme that the fixes they have made that are in Linux 3.1-rc4 will fix the
> problem.
> 
> So waiting those fixes to arrive to Fedora....

You're in luck!  They're here:

https://admin.fedoraproject.org/updates/kernel-3.1.0-0.rc4.git0.0.fc16?_csrf_token=7f427e099e7bee69004559136bd81eac0e4bab06

Comment 4 Jani Ollikainen 2011-09-02 15:01:04 UTC
Yes, tested with rawhide kernel (fc17 tagged:), but probably same as that one.

Problem kind of lies in that I have FC15, but ok, it's good to know that next release at least will work again :)

Comment 5 Chuck Ebbert 2011-09-12 14:54:55 UTC
(In reply to comment #4)
> Yes, tested with rawhide kernel (fc17 tagged:), but probably same as that one.
> 
> Problem kind of lies in that I have FC15, but ok, it's good to know that next
> release at least will work again :)

Did you try 2.6.40.4-5.fc15?

Comment 6 Jani Ollikainen 2011-12-20 23:15:56 UTC
Uh, sorry, forgot this bug totally. Well, just upgraded to fc16 and 3.1.5-6.fc16.i686 works. There might be problems in fc15, but as fc16 works, there's solution to this and I think this can be closed.

Comment 7 Jani Ollikainen 2012-09-19 15:32:32 UTC
It's back!

kernel-3.4.7-1.fc16.i686
kernel-3.4.9-2.fc16.i686

Are green again and kernel-3.1.8-2.fc16.i686 works.

Comment 8 Jani Ollikainen 2012-09-19 15:48:30 UTC
Works with kernel-3.5.4-1.fc17.i686.rpm. So problem is with fc16 but most probably works with fc17. So maybe need to plan upgrade, but won't close this as fc16 is broken. Close if you don't want to fix fc16:)

Comment 9 Dave Jones 2012-10-23 15:27:06 UTC
# Mass update to all open bugs.

Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.

Please retest with this kernel, and let us know if your problem has been fixed.

In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with.  Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.

If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
different problem. 
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).

Comment 10 Justin M. Forbes 2012-11-13 15:15:04 UTC
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.


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