<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_CLOSED bz_closed"
title="CLOSED FIXED - Native screen resolution not working correctly over HDMI LSPCON (i915)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107503#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_CLOSED bz_closed"
title="CLOSED FIXED - Native screen resolution not working correctly over HDMI LSPCON (i915)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=107503">bug 107503</a>
from <span class="vcard"><a class="email" href="mailto:nicholas.stommel@gmail.com" title="Nicholas Stommel <nicholas.stommel@gmail.com>"> <span class="fn">Nicholas Stommel</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=141030" name="attach_141030" title="dmesg-drm-tip">attachment 141030</a> <a href="attachment.cgi?id=141030&action=edit" title="dmesg-drm-tip">[details]</a></span>
dmesg-drm-tip
Well, it seems I spoke too soon. This issue is *very* much still present on
drm-tip, but for some odd reason I could not reproduce it with drm.debug=0x1e.
Fredrik from <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1570392">https://bugzilla.redhat.com/show_bug.cgi?id=1570392</a> was also
unable to reproduce the bug using the "drm.debug=0x1e" kernel parameter.
Without using the debugging parameter, the incorrect native resolution bug most
certainly happens.
-- Occurrence: Happens roughly over a third of the time, resolution is
incorrect on boot.
-- Chipset: Intel® Core™ i7-7700T CPU using Intel® HD Graphics 630 (Kaby Lake
GT2)
-- System architecture: x86_64
-- Kernel version (drm-tip) 4.18.0-994-generic
-- Linux distribution: Ubuntu 18.04.1 LTS (also confirmed on Fedora 28, appears
distro-independent)
-- Machine: HP Elitedesk 800 G3 DM 35W
-- Display connector: LSPCON HDMI
I have attached the dmesg from boot without the drm.debug=0x1e kernel
parameter, I will keep trying to see if I can replicate the bug with this
parameter to get the full debugging dmesg. Here you can clearly see in the
dmesg sans debugging parameter the lines:
[drm:lspcon_wait_mode [i915]] *ERROR* LSPCON mode hasn't settled
[drm:intel_dp_get_link_train_fallback_values [i915]] *ERROR* Link Training
Unsuccessful</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>