[Bug 89805] New: [GM45 DP-DVI dongle] KMS often does not set native display resolution
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Mar 28 13:43:14 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=89805
Bug ID: 89805
Summary: [GM45 DP-DVI dongle] KMS often does not set native
display resolution
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: andreas.sturmlechner at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 114684
--> https://bugs.freedesktop.org/attachment.cgi?id=114684&action=edit
20150328-2050_4.0.0-rc5+-start_dmesg-ignorelid_wrong-res.log
This is a followup to bug 58876. My setup is a Thinkpad X200s (lid closed)
sitting on an Ultrabase docking station, connected to a 1920x1200 DVI monitor
by means of a DP-DVI dongle. 4.0.0 is the first kernel version since 3.7 that
always seems to detect my external display: What previously most of the time
ended with a black screen / standby now seems to have been replaced with KMS
not setting the correct resolution. In the end KDE adjusts this correctly
anyway, so this behaviour is already a big improvement, but it would be nice to
get this ironed out as well.
I usually have to set i915.panel_ignore_lid=0 so that KMS is able to use all of
the external screen estate and make it not align a limited output to the upper
and left side, this setting also affects outcome with this bug:
If i915.panel_ignore_lid=0, then some very low standard resolution is set.
else, the LVDS panel's native resolution seems to be set for the external
screen.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150328/04b3494f/attachment.html>
More information about the intel-gfx-bugs
mailing list