FS#33062 - [linux] 3.7.x - 3.8.x i915 black screen with backlight on after KMS inits

Attached to Project: Arch Linux
Opened by Tomas M. (eldragon) - Wednesday, 12 December 2012, 10:40 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 23 May 2013, 20:06 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:
lspci
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)

im leaving this as a reference, since im suffering from this ever since the rc1 series.

during boot, when the kernel mode setting kicks in, the screen goes dark (backlight on), besides this issue. the computer boots correctly.

to restore it: suspend - resume.

ive opened an upstream ticket here: https://bugs.freedesktop.org/show_bug.cgi?id=57365

This task depends upon

Closed by  Tobias Powalowski (tpowa)
Thursday, 23 May 2013, 20:06 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.9.x
Comment by Piruthiviraj Natarajan (hadrons123) - Monday, 21 January 2013, 15:04 GMT
I have the same issue and nomodeset at least get me to ttys. i tried in Debian sid - experimental kernel 3.7.x and fedora 3.7.X. series.Debian get me to gnome fallback. But fedora and Arch doesn't get beyond ttys. Without nomodeset the screen just goes black. Look like an upstream bug. Surprised to find there is no noise about this. I use ivybridge laptop Lenovo y580.
Comment by Olivier (olive) - Monday, 21 January 2013, 17:00 GMT
I suffer from similar problems but only when an external VGA screen is attached, all is normal if I do not plug the VGA screen at boot up. My graphic card is similar, relevant output of lspci
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
Kernels 3.6.x work fine if I boot with the "VIDEO=SVIDEO-1:d" kernel parameter (otherwise the screen goes blank, this time if I have no VGA screen attached, but X starts nevertheless correctly and put everything into normal, including the console).

Edited: Actually, this is worse than i imagined: the kernel crash at the insertion of the i915 module. Here is the relevant part of journalctl: http://pastebin.com/g6t5593h . Maybe I could open a separate bug? This one is actually a kernel crash. Most probably upstream. A few more starnge experiment: I've tried the fedora kernel: it boots fine in Fedora but crash the same way as I mentioned if I boot archlinux with it (Fedora is on an external HD while Archlinux is on the internal IDE-SATA disk if that makes a difference).
Comment by Anonymous (reallybmn) - Friday, 15 February 2013, 15:17 GMT
I have a similar problem to Olivier, if I try to boot linux 3.7 on my laptop with an external monitor attached it will crash as soon as it tries to boot the kernel, leaving a black screen on both displays. If I detach the monitor it will boot fine and I can then reattach the monitor and it will function as usual. I've tried 3.7.3 - 3.7.7 and all crash. I'm using an Acer Aspire One A110, lspci|grep Display:
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
Comment by Tomas M. (eldragon) - Friday, 15 February 2013, 16:46 GMT
If your system crashes, kernel oopses or similar. this is not the same bug.
Comment by Olivier (olive) - Thursday, 21 February 2013, 10:18 GMT
The 3.8.1 kernel from testing fix the problem for me.
Comment by Lucas Cano (canolucas) - Sunday, 24 February 2013, 08:20 GMT
The bug is still there. Even with 3.8.1 from testing. After I updated to 3.8.1, it worked on the first boot. But it stopped working on successive boot attempts. Screen remained black as before. 3.6.11 is still the last working kernel. Later versions seem to work only sporadically. @Olivier, as Tomas said, your issue was not related to this bug!
Comment by Tomas M. (eldragon) - Tuesday, 05 March 2013, 20:36 GMT
Hello, this has been fixed in 3.9-rc1

description on the fix is at the upstream bug report.


Comment by Tobias Powalowski (tpowa) - Thursday, 23 May 2013, 19:45 GMT
Fixed in 3.9?
Comment by Lucas Cano (canolucas) - Thursday, 23 May 2013, 19:54 GMT
yes, thanks

Loading...