Pilsner Tux's lil' helper
Joined: 14 Mar 2008 Posts: 89
|
Posted: Sat Feb 23, 2013 6:51 am Post subject: External monitor powers off durinx X startup |
|
|
Since upgrade from kernel 3.5.7 version I am seeing this error of weird nature.
Whenever I start laptop pressing a button on the docking station following happens. GRUB menu appears on external monitor, timeout expires and kernel v. 3.7.9 starts booting. All text mode stuff is on external monitor, showing ok till it's time to start X server. When X server starts laptop has KDM menu, but external monitor powers off (message is monitor going to sleep) and then there is no way to bring it back: xrandr, or start and stop kdm, unplugging laptop and plugging it back to docking station - external monitor remains switched off till I reboot the system.
After some trials I've noticed that turning point is whether laptop lid is closed while GRUB did not kick off booting the kernel. If I have laptop lid open during GRUB counter, then X server boots ok on both laptop and external monitor. But when I have laptop lid closed and then open it only after kernel starts booting, X server will not start on the external monitor.
Code: | Linux gent 3.7.9-gentoo #1 Fri Feb 22 10:35:03 MSK 2013 x86_64 Intel(R) Core(TM) i5 CPU M 540 @ 2.53GHz GenuineIntel GNU/Linux |
It all started after kernel version 3.5.7, which was last kernel to work ok with external monitor.
partial lspci -v
Code: | 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 12) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device 172a
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at d0000000 (64-bit, non-prefetchable) [size=4M]
Memory at c0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 5050 [size=8]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
|
Does anyone seen this and why that happens? Probably a bug in intel driver. |
|