[Bug 908747] New: Monitor resolution maxing out at 1920x1200 for Intel Integrated Graphics Controller i915
http://bugzilla.opensuse.org/show_bug.cgi?id=908747 Bug ID: 908747 Summary: Monitor resolution maxing out at 1920x1200 for Intel Integrated Graphics Controller i915 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: bnc-team-screening@forge.provo.novell.com Reporter: bam@NightStorm.com QA Contact: sndirsch@suse.com Found By: --- Blocker: --- Created attachment 616207 --> http://bugzilla.opensuse.org/attachment.cgi?id=616207&action=edit Zip file of lsmod, lspci, and xrandr output capture from 13.1 and 13.2 boots I have a Dell U2713HM no longer recognized at full 2560x1440 resolution in openSuSE 13.2, instead it is maxing out at 1920x1200. I vaguely recall that this was also an issue when 13.1 came out and I think a kernel upgrade later fixed it. If it is of any use I'm attaching lspci, lsmod, and xrandr output from both 13.1 and 13.2 in a zip file. You can see that the 13.1 recognizes the full resolution whereas 13.2 does not. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908747 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sndirsch@suse.com, | |tiwai@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908747 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bam@NightStorm.com Flags| |needinfo?(bam@NightStorm.co | |m) --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- Could you install openSUSE 13.1 kernel on the 13.2 system and boot with it. Does the problem disappears? If yes, it's a kernel regression. In that case, try to boot both kernels with drm.debug=0x0e boot option, take the dmesg outputs on both, and attach to Bugzilla, together with /var/log/Xorg.0.log files. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908747 --- Comment #2 from Bruce Mallett <bam@NightStorm.com> --- Created attachment 616425 --> http://bugzilla.opensuse.org/attachment.cgi?id=616425&action=edit Xorg.0.log files for both 3.11 and 3.16 kernel boot-ups in a 13.2 openSuSE environment. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908747 --- Comment #3 from Bruce Mallett <bam@NightStorm.com> --- For some reason adding an attachment after entering a comment discarded the comment. Here is the jist of what I said in that now-lost comment: The 3.11 kernel under 13.2 is an excellent experiment, the monitor did get the correct resolution and xrandr works as it did under 13.1. I am attaching a zip of the two boot-ups. During the boot I went into advanced options, hit "e", and then added "drm.debug=0x0e" right before the "showopts" parameter on the vmlinuz line. Then hit F10 to boot. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908747 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@suse.com Component|X11 3rd Party Driver |Kernel Assignee|bnc-team-screening@forge.pr |kernel-maintainers@forge.pr |ovo.novell.com |ovo.novell.com QA Contact|sndirsch@suse.com |qa-bugs@suse.de Flags|needinfo?(bam@NightStorm.co | |m) | --- Comment #4 from Bernhard Wiedemann <bwiedemann@suse.com> --- info was provided in comment 2 and 3 - seems to be a kernel regression -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908747 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(bam@NightStorm.co | |m) --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- The requested kernel messages aren't included in the zip file. Could you attach them? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908747 --- Comment #6 from Bruce Mallett <bam@NightStorm.com> --- Created attachment 616473 --> http://bugzilla.opensuse.org/attachment.cgi?id=616473&action=edit Kernel msgs after bootup of 3.11 & 3.16 dmesg logs with drm.debug=0x0e Oops. Here are the two dmesg outputs. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908747 --- Comment #7 from Takashi Iwai <tiwai@suse.com> --- How are you connecting the monitor with 2560x1440? Is it over HDMI or DVI? Judging from the log, the new mode validator prunes this mode by some reason, usually due to the too high clock. Also, could you check whether the problem persists with the recent kernels in OBS Kernel:stable and Kernel:HEAD repos? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908747 --- Comment #8 from Bruce Mallett <bam@NightStorm.com> --- The 2560x1440 is on a DVI connection while the 1920x1200 on an HDMI. I'll do the kernel check later. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908747 Egbert Eich <eich@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eich@suse.com --- Comment #9 from Egbert Eich <eich@suse.com> --- What does 'xrandr -q' report? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908747 --- Comment #10 from Takashi Iwai <tiwai@suse.com> --- Then it's the result of the recent "fix". The driver became more strict and prunes the invalid modes for DVI. Some monitors allow higher clocks than specification (like yours), but these are filtered out now. As a workaround, you can still add the mode manually via xrandr, and use it explicitly. For example, % cvt -r 2560 1440 # 2560x1440 59.95 Hz (CVT 3.69M9-R) hsync: 88.79 kHz; pclk: 241.50 MHz Modeline "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync % xrandr --newmode "2560x1440" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync % xrandr --output HDMI1 --mode 2560x1440 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908747 --- Comment #11 from Takashi Iwai <tiwai@suse.com> --- See below for details https://bugzilla.kernel.org/show_bug.cgi?id=72961 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908747 --- Comment #12 from Egbert Eich <eich@suse.com> --- (In reply to Takashi Iwai from comment #10)
Then it's the result of the recent "fix". The driver became more strict and prunes the invalid modes for DVI. Some monitors allow higher clocks than specification (like yours), but these are filtered out now.
The reasoning behind this is a bit more complicated even: DVI does support these modes, this is why the monitor lists them in the EDID on a DVI connector. On DVI these modes are however only specified for dual link which Intel doesn't support. For single link DVI has a clock limit of 165MHz. HDMI is compatible with single link DVI, however has a higher clock limit. The intel driver uses this higher clock limit (on most chips) if it detects an HDMI sink. Then it depends if the monitor supports these modes over its HDMI port.
As a workaround, you can still add the mode manually via xrandr, and use it explicitly. For example,
This workaround will work for X, not console - the kernel allows all modes (even invalid ones) to be specified from user space. This way one can sneak in a mode which should not work according to the specs but still works on a certain piece of hardware. But since the driver no longer takes modes from the EDID the mode needs to be added explicitely, -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908747 --- Comment #13 from Bruce Mallett <bam@NightStorm.com> --- Thanks everyone. I can get by with the xrandr mode business and now have something that works after putting the following in my .bash_profile (appropriate place?): if [[ "$DISPLAY" = ":0" ]] then xrandr --newmode "2560x1440R" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync xrandr --addmode HDMI1 2560x1440R xrandr --output HDMI1 --mode 2560x1440R fi Works and gets me a proper dual monitor desktop. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=908747 Stefan Dirsch <sndirsch@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |CONFIRMED -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com