From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111913] AMD Navi10 GPU powerplay issues when using two DisplayPort connectors
Date: Wed, 09 Oct 2019 00:24:16 +0000 [thread overview]
Message-ID: <bug-111913-502-Vq09WjXmH7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111913-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1142 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111913
--- Comment #9 from Andrew Sheldon <asheldon55@gmail.com> ---
(In reply to Stefan Rehm from comment #8)
> In my case the resolution of both monitors is 2560x1440
You could try overclocking (or underclocking) one or both monitors to see if
the bug still exists, using:
https://github.com/kevinlekiller/cvt_modeline_calculator_12
I recommend using the "-b" option which uses reduced blanking V2 mode, but you
could experiment with different options.
Then to use it:
xrandr --output <monitor output> --newmode <modeline name> <modeline details
from cvt>
xrandr --output <monitor output> --addmode <monitor output> <modeline name>
xrandr --output <monitor output> --mode <modeline name>
Modeline name being whatever you like.
You'll probably have to launch X with one of the monitors disconnected (as the
bug may trigger before you can apply the modeline change). I believe the amdgpu
DDX has support for specifying modelines, but I don't know the syntax off the
top of my head.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2171 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-10-09 0:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 8:17 [Bug 111913] AMD Navi10 GPU powerplay issues when using two DisplayPort connectors bugzilla-daemon
2019-10-07 8:22 ` bugzilla-daemon
2019-10-07 8:28 ` bugzilla-daemon
2019-10-07 18:46 ` bugzilla-daemon
2019-10-07 19:06 ` bugzilla-daemon
2019-10-07 22:52 ` bugzilla-daemon
2019-10-08 12:02 ` bugzilla-daemon
2019-10-08 13:56 ` bugzilla-daemon
2019-10-08 15:39 ` bugzilla-daemon
2019-10-09 0:24 ` bugzilla-daemon [this message]
2019-10-09 18:39 ` bugzilla-daemon
2019-10-13 13:07 ` bugzilla-daemon
2019-10-19 11:24 ` bugzilla-daemon
2019-11-19 9:57 ` 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-111913-502-Vq09WjXmH7@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).