Found a workaround that works much better. I've updated my bugzilla report with this: Found a workaround. When up brought up system settings (/usr/bin/systemsettings5) and went to the display applet, it showed the 2 monitors. I noticed the real monitor was labeled DP-1. The fake laptop screen was labeled eDP-1. I had been googling around for how to disable monitors at boot time and had come across the kernel parameter "video=DISPLAYNAME:d. I had been trying video=LVDS-1:d since everything I had found mentioned that as the laptop display. This time I tried adding "video=eDP-1:d" to the line for the kernel and it worked. I have since added it to the line in /boot/grub/grub.cfg. On 12/02/2016 02:12 PM, Charles R. Dennett wrote: > I filed a bugzilla report. It's > https://bugzilla.redhat.com/show_bug.cgi?id=1397864 > > Meanwhile I did some more poking around and found something that appears > very interesting. To quote a comment I added to the above bugzilla report: > > ================================================== > Apparently, kernels newer than 4.8.4 think my system has 2 monitors > attached to it. It only has one. It has never had two. I'm using the > embedded graphics for my one and only monitor. I have never added a > second video card. When I run the KDE system settings app and use the > display applet, it sees my main monitor and second monitor it describes > as a laptop monitor. This system is not a laptop. It is a desk-side > system. Only kernels newer than 4.8.4 (ie, 4.8.8.and 4.8.10) show this. > The 4.8.4 kernel correctly determines I only have one monitor. > ================================================== > > I've got a workaround for now. I can run system setting and choose the > display and monitor applet. That's where I see two displays. After > some back and forth I've found that clicking "Unify Outputs" gives me > one display. Icons are all messed up but I can live with that for now. > > Charlie > > > On 11/22/2016 05:27 PM, Charles R. Dennett wrote: >> Thanks for the suggestion. I removed the xorg-x11-dev-intel package and >> rebooted on the 4.8.8 kernel. It did not help. Same situation. Looks >> like it's using the modesetting driver from what I see in Xorg.0.log. >> I'll keep looging. >> >> Charlie >> >> >> >> On 11/21/2016 10:49 PM, Felix Miata wrote: >>> Charles R. Dennett composed on 2016-11-20 08:46 (UTC-0500): >>> ... >>> >>> Do you have any optional repos installed? >>> >>> I have no Skylake systems, but I do have multiple versions of Fedora on >>> multiple multiboot systems with Intel video. KDE in F24 is fine on all that I >>> can recall, but not so with F25 and Rawhide, which on at least one (older >>> than yours, Eaglelake) machine exhibits symptoms similar to what you report. >>> The difference I see is that F25 and Rawhide are now using server 1.19rc1, >>> while F24 (running 4.8.7 currently booted on host big41) remains on 1.18.4. >>> >>> Regardless whether a 1.19 server is present, you could try the driver >>> integrated into the server, "modesetting", (most easily) by uninstalling >>> xorg-x11-drv-intel. >>> >>> The modesetting driver seems to be the future of X regardless of gfxchip: >>> http://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Abandon-Intel-DDX _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
