<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Sometimes does not detect 60Hz Full HD mode for external display, switching to 60 Hz with interlace" href="https://bugs.freedesktop.org/show_bug.cgi?id=104934#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Sometimes does not detect 60Hz Full HD mode for external display, switching to 60 Hz with interlace" href="https://bugs.freedesktop.org/show_bug.cgi?id=104934">bug 104934</a> from <a class="email" href="mailto:Martin@Lichtvoll.de" title="Martin Steigerwald <Martin@Lichtvoll.de>"> Martin Steigerwald</a> <pre>(In reply to Jani Saarinen from <a href="show_bug.cgi?id=104934#c2">comment #2</a>) > First of all. Sorry about spam. > This is mass update for our bugs. > > Sorry if you feel this annoying but with this trying to understand if bug > still valid or not. As of 4.16-rc6 this bug is still valid. I found a work-around. When I move the DisplayPort cable from DP2 to DP3 or wise versa *while* the session is running, the 60 Hz resolution is always detected and I can activate it again. What can also happen that one Plasma session gets is right and when I open up another Plasma session via SDDM in the other one only the interlaced mode is detected. So the one session has the 60 Hz resolution, while the other just has the interlaced one, yet still with the same cable and at the same time (minus delay for switching between sessions via Ctrl-Alt-F7/8). I tried with four cables already. However, I have a cable where this appeared more rarely (no scientific measurement, just personal impression). Curiously it was the longest one with 5 meters. So I ordered another cable like this, but just 2 meters and will test it as well. Since for a long time with previous kernels I did not see this issue and since the issue always goes away when moving the Displayport cable between DP2 and DP3, I still think that it is not or at least not solely a cabling issue.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>