Bug 32998 - intel external monitor isn't reactived on resume
Summary: intel external monitor isn't reactived on resume
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium minor
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-11 09:39 UTC by Toralf Förster
Modified: 2011-03-24 09:06 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.0.log (92.74 KB, text/plain)
2011-01-11 09:39 UTC, Toralf Förster
no flags Details

Description Toralf Förster 2011-01-11 09:39:46 UTC
Created attachment 41879 [details]
Xorg.0.log

I wonder whether the following lines in my Xorg.0.log :

 60.051] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
[    60.051] (**) Lid Switch: Applying InputClass "keyboard-all"
[    60.051] (**) Lid Switch: always reports core events
[    60.051] (**) Lid Switch: Device: "/dev/input/event1"
[    60.053] (WW) Lid Switch: Don't know how to use device
[    60.056] (II) UnloadModule: "evdev"
[    60.056] (EE) PreInit returned NULL for "Lid Switch"


points to this problem:
If I use my ThinkPad T400 /1440x900) in a dual-head mode with an external VGA screen (1280x1024) "above" the T400 display and s2ram the T400 it and wake it up, then the external VGA screen is black (but the virtual screen "works" - I can move a window partially or fully to the 2nd monitor, but the LED at the external monitor is yellow == so signal from the notebook). However if I then type Ctrl+Alt+F12 and switch back with Ctrl+Alt+F7, the external screen is visible too (and the LED is green of course).
Comment 1 Julien Cristau 2011-01-11 09:50:57 UTC
It's unrelated.  The Lid switch messages can be ignored.
Comment 2 Toralf Förster 2011-01-12 00:27:15 UTC
(In reply to comment #1)
> It's unrelated.  The Lid switch messages can be ignored.
Thx. WRT to the issue of the 2nd monitor - is this xorg or rather kernel related ?
Comment 3 Toralf Förster 2011-03-24 09:06:02 UTC
It is solved with kernel 2.6.38.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.