xorg-server-1.14.2 blacks out the external display here. It is connected via VGA and gets recognized by kscreen, but unfortunately it stays black and the display menu doesn't recognize the laptop. Using xorg-server-1.14.1 and everything works fine. emerge -pv xorg-server [ebuild r U ~] x11-base/xorg-server-1.14.2:0/1.14.2 [1.14.1:0/1.14.1] USE="ipv6 nptl suid udev xorg -dmx -doc -kdrive -minimal (-selinux) -static-libs -tslib -xnest -xvfb" 0 kB [ebuild rR ~] x11-drivers/xf86-input-synaptics-1.7.1 0 kB [ebuild rR ~] x11-drivers/xf86-input-evdev-2.8.0 0 kB [ebuild rR ~] x11-drivers/xf86-video-intel-2.21.10-r1 USE="dri sna udev xvmc -glamor -uxa" 0 kB [ebuild rR ~] x11-drivers/xf86-video-nouveau-1.0.8 0 kB (nouveau is disabled, just using internal intel graphics)
Can you bisect between 1.14.1 and 1.14.2? Also, does this affect older xf86-video-intel too?
You may also want to try xf86-video-intel-2.21.11
Thanks for the hint, I'll try it asap. I'm pretty sure it isn't related to xorg-server-1.14.2 cause I had the same problem with xorg-server-1.14.1
(from comment #0) > Using xorg-server-1.14.1 and everything works fine. (from comment #3) > I had the same > problem with xorg-server-1.14.1 I don't quite understand. Which versions of which packages work, and which ones don't?
Sorry for the confusion. This is a strange behaviour and I'm not sure which component is causing the random blackout. The system once worked fine on my external monitor and after I've updated to the new xorg-server it didn't work anymore, so xorg-server was suspicious to me. As I'm using the ebuilds available with ABI_X86=32 support, I've put many testing ebuilds into my installation. Yesterday (xorg-server-1.14.1 / xf86-video-intel-2.21.10-r1) the configuration didn't work either, so I think there might be another component that creates problems. Right now I'm using xorg-server-1.14.2 / xf86-video-intel-2.21.11 and after some changes with kscreen (disable/enable external vga) it works again. VGA always gets detected, but if it fails, there is no output on it. HDMI output seems to be completetly unaffected. So I'm not sure whats the proper way to deal with it.
The relevant components are kernel (DRM) xorg-server xf86-video-intel (DDX) Nowadays, most things related to configuring outputs (aka. modesetting) happen in the kernel.
Also you could try xf86-video-intel-2.21.12 which contains fixes for uninitialized gamma settings, especially: d36c9542d2bd707838a87c451bf76f091aaf5cba ebf4517a0bb510e406795c169aa21b7cc615ed31
I have a bug which may be related Bug 476994 with =x11-drivers/xf86-video-intel-2.21.12 but might be something else since today (maybe yesterday I have problem with 2 display) might be related to another updated component
and by the way I am still using gentoo-source-3.9.6 and havn't touch it's config . It was working fine with this kernel3.9.6 it's not working with the same untouched kernel3.9.6. jumping in as I start to think that my bug 476994 might be a duplicate of this one.
What kernel are you using? On my system, since 3.9 I've got no fbcon most of the time (but X) and since 3.11 neither fbcon nor X on the external display. Also, since 3.11 the display often isn't even detected so I can't bring it up manually. But sometimes it works.
Please make sure that upstream becomes aware of the problem by reporting a bug at https://bugs.freedesktop.org/ and provide the link here. If the bug was introduced between kernel 3.8 and 3.9, you could try to bisect to find the commit that caused it.
(In reply to Chí-Thanh Christopher Nguyễn from comment #11) > Please make sure that upstream becomes aware of the problem by reporting a > bug at https://bugs.freedesktop.org/ and provide the link here. If the bug > was introduced between kernel 3.8 and 3.9, you could try to bisect to find > the commit that caused it. Sorry, I'm currently fighting three i915 bugs at once and messed up what was introduced when - my blank screen trouble actually began with 3.8, not 3.9. I did report that already, and tried to bisect twice, but it's completely hopeless due to the randomness of the bug: https://bugs.freedesktop.org/show_bug.cgi?id=58876 mrueg, you could try 3.4.62 (which is always working for me, as anything pre-3.8) to see if it's kernel related.
Works for me again with 2.99.910 and xorg-server-1.15.0.
(In reply to Manuel Rüger from comment #13) > Works for me again with 2.99.910 and xorg-server-1.15.0. Is this bug still needed? It works for me again, not sure if anyone else still has a problem?
I think it's very likely this is fixed in a new version of the driver. If it's not, please file a bug upstream at bugs.freedesktop.org. We're not prepared to fix driver issues that aren't fixed upstream.
