Bug 771110

Summary: [Regression] Bring back modesetting for Intel Ironlake Mobile GPUs
Product: [Fedora] Fedora Reporter: Milan Bouchet-Valat <nalimilan>
Component: xorg-x11-drv-intelAssignee: Matthew Garrett <mjg59>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: ajax, gansalmon, itamar, jfeeney, jonathan, kernel-maint, madhu.chinakonda, xgl-maint
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:44:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
acpidump output none

Description Milan Bouchet-Valat 2012-01-01 14:00:18 UTC
I've an Intel Ironlake Mobile graphics card on a HP dm4 laptop. When I upgraded from F15 to F16, Anaconda automatically added "nomodeset" to the boot arguments. This worked fine, but I ended up with only the VESA driver!

Removing "nomodeset" from the boot arguments made the screen go blank when Plymouth starts, and stay this way forever (in F15, the screen was blank during boot, but returned later to a normal state). But I found a workaround on a forum[1]: use "acpi_osi=Linux acpi_backlight=vendor". With this, modesetting works, and hardware acceleration is back.

I've tested an Ubuntu development live CD with kernel 3.2rc7, and it seems there's no need for this hack, which probably means the problem was fixed the right way in the new kernel. I couldn't test Rawhide since live CDs are currently broken.

Do you think there's a way to backport the fixes to F16? This GPU family was working fine in F15, it would be a shame that people upgrading to F16 get only VESA, which can barely play a DVD.


The exact card is:
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller])
(integrated with the i5 M450)

1: http://www.fedoraforum.org/forum/showthread.php?t=272848

Comment 1 Milan Bouchet-Valat 2012-01-01 14:30:06 UTC
Actually, I installed kernel 3.2rc7 from Rawhide, and it doesn't change anything to the issue. So I wonder what Ubuntu does to their kernels.

Should I report this upstream directly then?

Comment 2 Matthew Garrett 2012-01-03 17:50:56 UTC
Can you try

acpi_backlight=vendor

without any acpi_osi option?

Comment 3 Milan Bouchet-Valat 2012-01-03 21:16:46 UTC
Yeah, sorry, I wanted to check and I forgot. "acpi-backlight" is enough to fix the bug.

Comment 4 Matthew Garrett 2012-01-03 21:26:37 UTC
Ok, I suspect I know what the underlying problem here is. Can you install the pmtools package, run acpidump as root and attach the output here?

Comment 5 Milan Bouchet-Valat 2012-01-03 21:51:32 UTC
Created attachment 550541 [details]
acpidump output

Sure.

Comment 6 Milan Bouchet-Valat 2012-12-22 15:21:46 UTC
This got fixed in F17.

Comment 7 Milan Bouchet-Valat 2012-12-22 16:08:54 UTC
...but regressed again in F18 (bug 889687).

If you need debugging, please just ask.

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

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 18'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.

Comment 9 Fedora End Of Life 2014-02-05 22:44:09 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.