<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - radeon (amdgpu) DisplayPort loss of max-resolution on DP monitor (after monitor power saving / idle)" href="https://bugs.freedesktop.org/show_bug.cgi?id=107731#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - radeon (amdgpu) DisplayPort loss of max-resolution on DP monitor (after monitor power saving / idle)" href="https://bugs.freedesktop.org/show_bug.cgi?id=107731">bug 107731</a> from <a class="email" href="mailto:alexdeucher@gmail.com" title="Alex Deucher <alexdeucher@gmail.com>"> Alex Deucher</a> <pre>(In reply to L.S.S. from <a href="show_bug.cgi?id=107731#c9">comment #9</a>) > Just tested... it seems if I connect to the monitor directly the problem > doesn't occur. > > Guess the KVM does play a part in this. However, I still need the KVM as > I've four PCs connected to this monitor. > > It's not a major issue as switching it back and forth would put the system > back to the correct resolution, and it currently doesn't have any serious > impacts. Just that I'm wondering why this problem is only happening on AMD > video cards and not on nVidia video cards. Possibly different behavior in the the hw or hw settings on what is considered a short vs. long pulse for DP.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>