From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96868] AMDGPU Tonga only does 2560x1440 at 120hz, switching to 144hz causes display errors, same thing used to happen with fglrx.
Date: Tue, 29 Nov 2016 15:41:28 +0000 [thread overview]
Message-ID: <bug-96868-502-xtGRAaIoYF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96868-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 544 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96868
--- Comment #12 from iuno@posteo.net ---
Yeah, forcing high clock rates seem to fix the flickering issue.
The problem is actually the memory clock. However, today, without my
intervention, the memory clock stays at max (1250 MHz) for high refresh rates,
while the core clock still goes down to 300, as it should. So this god "fixed"
indeed.
I still have the 144 Hz problem with corrupt image, though.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1454 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-11-29 15:41 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-96868-502@http.bugs.freedesktop.org/>
2016-07-11 7:24 ` [Bug 96868] AMDGPU Tonga only does 2560x1440 at 120hz, switching to 144hz causes display errors, same thing used to happen with fglrx bugzilla-daemon
2016-07-11 9:31 ` bugzilla-daemon
2016-07-11 9:32 ` bugzilla-daemon
2016-07-11 9:50 ` bugzilla-daemon
2016-07-11 9:50 ` bugzilla-daemon
2016-07-11 14:56 ` bugzilla-daemon
2016-07-11 14:57 ` bugzilla-daemon
2016-07-11 19:26 ` bugzilla-daemon
2016-07-11 19:28 ` bugzilla-daemon
2016-07-12 22:36 ` bugzilla-daemon
2016-10-05 8:33 ` bugzilla-daemon
2016-11-26 19:38 ` bugzilla-daemon
2016-11-26 21:02 ` bugzilla-daemon
2016-11-29 15:41 ` bugzilla-daemon [this message]
2017-03-18 18:31 ` bugzilla-daemon
2017-05-11 9:48 ` bugzilla-daemon
2017-05-11 13:01 ` bugzilla-daemon
2017-05-11 15:04 ` bugzilla-daemon
2017-05-11 16:41 ` bugzilla-daemon
2017-05-11 17:59 ` bugzilla-daemon
2017-05-11 18:00 ` bugzilla-daemon
2017-05-11 18:00 ` bugzilla-daemon
2017-05-11 18:00 ` bugzilla-daemon
2017-05-12 9:22 ` bugzilla-daemon
2017-05-23 21:24 ` bugzilla-daemon
2017-05-23 21:24 ` bugzilla-daemon
2017-05-23 21:25 ` bugzilla-daemon
2017-05-23 21:25 ` bugzilla-daemon
2017-05-23 21:26 ` bugzilla-daemon
2017-05-24 15:13 ` bugzilla-daemon
2017-06-14 13:28 ` bugzilla-daemon
2017-06-14 13:51 ` bugzilla-daemon
2017-07-13 3:08 ` bugzilla-daemon
2017-07-13 3:28 ` bugzilla-daemon
2017-10-04 23:22 ` bugzilla-daemon
2018-02-09 22:37 ` bugzilla-daemon
2018-03-24 11:51 ` bugzilla-daemon
2018-11-10 18:48 ` bugzilla-daemon
2018-11-10 18:51 ` bugzilla-daemon
2018-11-29 20:51 ` bugzilla-daemon
2018-11-30 1:26 ` 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-96868-502-xtGRAaIoYF@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