[Bug 73971] Intel i915 screen remains blank when resuming from suspend

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Wed Apr 23 19:40:09 PDT 2014


https://bugzilla.kernel.org/show_bug.cgi?id=73971

--- Comment #33 from Denis Leclair <denis at theleclairs.ca> ---
great news...everything is now working.

For the record:
I booted into runlevel 3 without nomodeset. The idea was to reinstall Xorg in
case the previous installation with nomodeset on the kernel line affected
something. The re-installation made no difference. the behavior from startx was
the same and the xorg.conf file was also the same.

I then did some searching on the web and found that we should run "Xorg
-configure" to auto-scan the hardware and generate a proper xorg.conf file. So
I went back into runlevel 3 without nomodeset and ran the "Xorg -configure"
command. I will attach the xorg.conf file that it generated right after I post
this comment.

I rebooted with the new xorg.conf file and thankfully everything is now
working. I can now suspend and resume without problem, all the function keys
(volume, brightness, etc...) are working. I even plugged an external monitor to
my VGA port and it was automatically detected and my desktop was extended.

The only thing I haven't tried yet is putting the laptop on the docking station
to see how it behaves there. I will try that when I return to the office
tomorrow morning.


So it seems to me the root cause of all of this came down to two things:
1. the CentOS installer added nomodeset to the kernel line even though the i915
driver does not support it.

2. (perhaps due to problem #1) the CentOS installer did not automatically setup
the xorg.conf file by running an "Xorg -configure" scan.

Do you see anything incorrect with my conclusions?

I'm thinking I should file this as a bug with the CentOS maintainers so that
other people don't fall into the same trap but I'd like your perspective before
doing that.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the intel-gfx-bugs mailing list