From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 93826] 2560x1440 @144Hz graphic glitches and bad refresh rate Date: Mon, 19 Jun 2017 17:42:33 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0384499185==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 4671E6E1FC for ; Mon, 19 Jun 2017 17:42:33 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0384499185== Content-Type: multipart/alternative; boundary="14978941536.057C6b.7689"; charset="UTF-8" --14978941536.057C6b.7689 Date: Mon, 19 Jun 2017 17:42:33 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D93826 --- Comment #71 from Eike --- Sorry, I didn't want to get defensive. I guess you are right about the drivers, it was just funny to me that I had= the same issue on Windows 10 with the AMD drivers provided by Windows Update on install. There seems to be a problem with the drivers that does not affect all 144hz monitors and can (in the case of the Asus MG279Q) be worked around by monit= or firmware. I don't know how the firmware might change the gpu's dc clock though. I attached my verbose xrandr output including EDID. --=20 You are receiving this mail because: You are the assignee for the bug.= --14978941536.057C6b.7689 Date: Mon, 19 Jun 2017 17:42:33 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 71 on bug 93826<= /a> from Eike 
Sorry, I didn't want to get defensive.
I guess you are right about the drivers, it was just funny to me that I had=
 the
same issue on Windows 10 with the AMD drivers provided by Windows Update on
install.
There seems to be a problem with the drivers that does not affect all 144hz
monitors and can (in the case of the Asus MG279Q) be worked around by monit=
or
firmware.
I don't know how the firmware might change the gpu's dc clock though.

I attached my verbose xrandr output including EDID.

You are receiving this mail because:
  • You are the assignee for the bug.
= --14978941536.057C6b.7689-- --===============0384499185== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0384499185==--