<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - amd-staging-drm-next-git 4.16 & RX 560 DL-DVI: corruption with refreshrates >73Hz when DPM changing VRAM clock"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105300#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - amd-staging-drm-next-git 4.16 & RX 560 DL-DVI: corruption with refreshrates >73Hz when DPM changing VRAM clock"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105300">bug 105300</a>
from <span class="vcard"><a class="email" href="mailto:tempel.julian@gmail.com" title="tempel.julian@gmail.com">tempel.julian@gmail.com</a>
</span></b>
<pre>Video which shows the artifacts:
<a href="https://youtu.be/it3d6BjpZjU">https://youtu.be/it3d6BjpZjU</a>
(can also be quite worse when doing stuff)
It happens with every desktop environment with and without enabled OGL
compositor. In the video, it's KDE Plasma on Xorg.
But there is no difference with a Wayland session, the artifacts there are the
same.
You are correct that the display's own edid information doesn't know any other
refreshrate than 59.95Hz.
However, these Korean import display's are very often used with higher
refreshrates because their panels allow this without incompatible scaler in
between. With the old display stack, I can even set 85Hz without any issues.
75Hz is also not very uncommon for some 2560x1440p IPS displays, I suppose
there is the realistic possibility that also displays which have a 2560x1440
75Hz resolution in their original edid are affected by this bug (since the old
stack isn't affected, I'm quite sure it's some kind of bug).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>