From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107731] radeon (amdgpu) DisplayPort loss of max-resolution on DP monitor (after monitor power saving / idle)
Date: Tue, 19 Mar 2019 19:18:02 +0000 [thread overview]
Message-ID: <bug-107731-502-VjqjbO0VIL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107731-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 849 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107731
--- Comment #10 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to L.S.S. from comment #9)
> 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.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1835 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-19 19:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 1:37 [Bug 107731] radeon (amdgpu) DisplayPort loss of max-resolution on DP monitor (after monitor power saving / idle) bugzilla-daemon
2018-08-29 1:38 ` bugzilla-daemon
2019-03-10 7:44 ` bugzilla-daemon
2019-03-10 7:48 ` bugzilla-daemon
2019-03-10 7:56 ` bugzilla-daemon
2019-03-11 16:07 ` bugzilla-daemon
2019-03-17 8:08 ` bugzilla-daemon
2019-03-18 20:08 ` bugzilla-daemon
2019-03-19 10:52 ` bugzilla-daemon
2019-03-19 13:50 ` bugzilla-daemon
2019-03-19 18:27 ` bugzilla-daemon
2019-03-19 19:18 ` bugzilla-daemon [this message]
2019-03-22 17:28 ` bugzilla-daemon
2019-05-22 0:58 ` bugzilla-daemon
2019-05-22 2:20 ` bugzilla-daemon
2019-10-03 16:40 ` bugzilla-daemon
2019-11-19 8:50 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-107731-502-VjqjbO0VIL@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).