Created attachment 129307 [details] dmesg with drm.debug=0xe Bug description: I've been trying to get Ubuntu 16.10 working on my custom PC with Intel core i3-7100 (Kaby Lake), but can't get the graphics working properly. My display flashes off regularly - about once every second if I use resolution 1920x1080, rendering it practically unusable, and once every 5-10 seconds with resolution 800x600. I'm fairly certain it's a driver issue because everything worked fine when I installed Windows, and also works in Ubuntu if I switch to the console (Ctrl-Alt-F1). The frequency seems to be correlated with how much change there is on the screen - if I don't move anything at resolution 800x600, it doesn't blink. I've tried suggestions online to use the latest kernel version (tried both 4.10-rc6 from mainline kernel PPA and latest from drm-intel-nightly), updated graphics drivers from Oibaf's PPA, used Intel's Graphics Update Tool, and put magical incantations in Xorg conf files (including turning DRI off), but ultimately to no avail. System environment: -- system architecture: x86_64 -- kernel: 4.10.0-994.201702012102 (latest on http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly/) -- xserver-xorg-video-intel: 2:2.99.917+git1702011933.9fe04a~gd~y (from Oibaf) -- Linux distribution: Ubuntu (also tried Fedora) -- Motherboard model: Gigabyte H270N-WIFI -- Display connector: HDMI Additional info: Let me know if there's anything else I should run.
Created attachment 129308 [details] blue fuzz BTW, if it helps, I've noticed the black parts of the screen develop a blue fuzz just before the screen flashes. See example image of glxgears.
Finally managed to fix it! Turns out when I use Ubuntu in BIOS mode (rather than UEFI) it works perfectly. I'm guessing it's some compatibility issue with my Gigabyte H270N-WIFI motherboard. Had no idea EFI problems could cause strange display issues like this. If you know where to report the UEFI issue, please let me know. Otherwise I'm just happy it's fixed.
(In reply to viveksjain from comment #2) > Finally managed to fix it! Turns out when I use Ubuntu in BIOS mode (rather > than UEFI) it works perfectly. I'm guessing it's some compatibility issue > with my Gigabyte H270N-WIFI motherboard. Had no idea EFI problems could > cause strange display issues like this. > > If you know where to report the UEFI issue, please let me know. Otherwise > I'm just happy it's fixed. Probably caused by the OEM (intentionally or unintentionally) creating a different VBT (Video BIOS Table) for UEFI and legacy boots, and only testing with what Windows uses i.e. UEFI. This is not unusual.
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.