Red Hat Bugzilla – Bug 505371
Monitor suspends immediately on gdm startup when laptop 'lid' is closed
Last modified: 2015-01-14 18:23:07 EST
Created attachment 347436 [details]
Xorg.0.log booting with laptop lid open
Description of problem:
I was having difficulty getting Rawhide gdm to start with my system docked and the laptop lid closed (with external display connected).
System is Thinkpad X200 (Intel graphics).
When booting into runlevel 5, the display would almost immediately blacken and the monitor would suspend. I could not recover except to hard reboot.
I "worked around" this by booting into runlevel 3, logging in, running "startx", and constantly keeping the mouse in motion until the desktop was displayed. Then all was fine.
After some head scratching, I tried booting with the laptop lid open, and the system booted just fine.
I'm at a loss as to what info to provide. Please let me know.....
I attach /var/log/Xorg.0.log booting with lid open. Not sure what else is useful.
This only started occurring when I updated FC11 system to FC12-Rawhide.
Sorry if this is the wrong component. Please redirect!
Version-Release number of selected component (if applicable):
Steps to Reproduce:
What seems to be happening here is that the laptop LCD is active, not the external monitor, even though plymouth is quite happy using the external monitor.
I can login through the laptop LCD afterwhich gdm happily "switches" to the external monitor....
Notice errors like this:
Jun 8 06:33:24 tlondon kernel: [drm:gm45_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 1
Just about when "gdm-simple-greeter" starts.
Here is a bit more context:
Jun 7 13:04:23 tlondon kernel: [drm:gm45_get_vblank_counter] *ERROR* trying to get vblank count for disabled pipe 1
Jun 7 13:04:23 tlondon nscd: 22657 Access Vector Cache (AVC) started
Jun 7 13:04:23 tlondon NetworkManager: <info> Policy set 'System eth0' (eth0) as default for routing and DNS.
Jun 7 13:04:23 tlondon dnsmasq: reading /etc/resolv.conf
Jun 7 13:04:23 tlondon dnsmasq: using nameserver 220.127.116.11#53
Jun 7 13:04:23 tlondon dnsmasq: using nameserver 18.104.22.168#53
Jun 7 13:04:23 tlondon dnsmasq: using nameserver 22.214.171.124#53
Jun 7 13:04:25 tlondon ntpd: Deleting interface #9 wlan0, 192.168.1.103#123, interface stats: received=0, sent=0, dropped=0, active_time=10140 secs
Jun 7 13:04:31 tlondon gdm-simple-greeter: WARNING: Unable to parse history: (null) 4#012
Some more (possibly useful?) data:
I have two different external monitors, an not too old HP LCD and an quite old Mitsubishi LCD.
Entries from Xorg.0.log for both monitors:
(II) intel(0): Manufacturer: HWP Model: 265e Serial#: 16843009
(II) intel(0): Year: 2006 Week: 20
(II) intel(0): EDID Version: 1.3
(II) intel(0): EDID for output VGA1
(II) intel(0): Manufacturer: MEL Model: 4341 Serial#: 525
(II) intel(0): Year: 1999 Week: 31
(II) intel(0): EDID Version: 1.1
I connected the Thinkpad X200 (via dock) to each monitor, opened the laptop lid, and booted (with KMS).
The behavior is not quite the same. Below shows which screen(s) are active at each of the booting stages:
BIOS External only External only
Grub External only External only
Plymouth Both ext & laptop Both ext & laptop
gdm Both laptop LCD only
gnome Both External only
So the "problem" is that booting with the Mitsubishi, gdm "deactivates" the external "pipe".
[With the laptop lid closed, both configurations suspend the display and the system. I hard reset to recover.]
This issue continues with:
I have to boot with laptop lid open, even though plymouth has no problem detecting my external monitor.
In fact, the system immediately suspends, not just the monitor....
This issues seems to have gone away with latest rawhide/koji packages:
Boots up fine now (into 1280x1024) with the laptop lid shut. Gdm first boots up in reduced resolution (800x600?) for password entry, and then transitions to 1280x1024.
I'll monitor, and close this if it is stable for a few days....
Looks like this is gone....
Not sure what caused it, or what fixed it, but ....