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: Wed, 05 Oct 2016 08:33:20 +0000 [thread overview]
Message-ID: <bug-96868-502-kMh3aktx58@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96868-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 809 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=96868
--- Comment #9 from iuno@posteo.net ---
I have the same problem with my Hawaii card and my WQHD 144 Hz monitor. It is
not X related and the effect is visible on the framebuffer console, too.
120 Hz setting does flicker like seen in comment 7.
144 Hz setting has a flickering vertical bar a few pixels wide on the left
side, a vertical bar in the center of the screen and overall blurred image.
The OSD of the monitor shows that the input is 2568 pixels wide, has a 214 KHz
horizontal and 139 Hz vertical refresh rate. When using with Intel GPU (which
works correctly) it shows 2560 px, 222 KHz and 144 Hz.
Tried both radeon (linux 4.7.6) and amdgpu (linux 4.8)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1747 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-10-05 8:33 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 [this message]
2016-11-26 19:38 ` bugzilla-daemon
2016-11-26 21:02 ` bugzilla-daemon
2016-11-29 15:41 ` bugzilla-daemon
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-kMh3aktx58@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).