Created attachment 126311 [details] dmesg output with drm.debug=0x0e Originally this bug was filed openSUSE's bugzilla: http://bugzilla.opensuse.org/show_bug.cgi?id=993996 Since upgrade to new kernel 4.7 in openSUSE Tumbleweed the display of my laptop is not correctly initialized anymore (find attached the dmesg output with drm.debug=0x0e). Booting with "nomodeset" helps at least to work with the system but the correct display resolution of 1400x1050 pixels cannot be used (blurry resolution). It's pretty simple hardware which worked until kernel 4.6.4. nb2:~ # lspci 00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 03) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 03) 00:1a.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev f3) 00:1f.0 ISA bridge: Intel Corporation 82801HM (ICH8M) LPC Interface Controller (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) IDE Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801HM/HEM (ICH8M/ICH8M-E) SATA Controller [AHCI mode] (rev 03) 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 03) 04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit Ethernet Controller (rev 14) 14:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61) 1c:03.0 CardBus bridge: O2 Micro, Inc. OZ711SP1 Memory CardBus Controller (rev 01) 1c:03.1 CardBus bridge: O2 Micro, Inc. OZ711SP1 Memory CardBus Controller (rev 01) 1c:03.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller (rev 02) 1c:03.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD Controller (rev 01)
I think I'm running into this on a Lenovo C50-30 all-in-one with Intel 5500 graphics: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) In my case on kernel-4.7.2-201.fc24.x86_64. Works find with 4.6.7. Likewise nomodeset helps but everything is unaccelerated.
Possibly fixed by Fixes: ea54ff400889 ("drm/i915: Ignore OpRegion panel type except on select machines") in drm-intel-fixes branch of http://cgit.freedesktop.org/drm-intel.
Ermh, ignore the "Fixes: " part.
I can confirm this patch fixes things on my Lenovo C50-30 with Intel 5500 graphics. kernel-core-4.7.3-200.jhe.fc24.x86_64
Thanks, closing.
(In reply to Jani Nikula from comment #5) > Thanks, closing. Shouldn't we wait for the original reporter to confirm, too, as he's using different hardware?
As you can see in http://bugzilla.opensuse.org/show_bug.cgi?id=993996 the fix made it into downstream openSUSE kernel and I confirmed there that it works for me.
When is this queued to arrive in 4.7?
(In reply to James from comment #8) > When is this queued to arrive in 4.7? Seems to be in v4.7.5.
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.