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: Sun, 11 Jun 2017 23:57:15 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0973664623==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id F35C489FF6 for ; Sun, 11 Jun 2017 23:57:14 +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 --===============0973664623== Content-Type: multipart/alternative; boundary="14972254342.E27965cA.29380"; charset="UTF-8" --14972254342.E27965cA.29380 Date: Sun, 11 Jun 2017 23:57:14 +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 #56 from Eike --- (In reply to iuno from comment #52) > It could be fixed by increasing the default display clock: > https://people.freedesktop.org/~cbrill/dri-log/index. > php?channel=3Dradeon&highlight_names=3Dagd5f;grmat&date=3D2017-01-03 >=20 >=20 > @Eike: you have a faulty monitor, please don't suggest people here to send > theirs back because there certainly *is* a software issue. >=20 > @Jonas: Did you try forcing the mclock to high? It doesn't require a high= er > core dpm state but should fix your problem. Sorry to correct you, but my monitor has not been faultier than any other MG279Q that was bought before 2017. I already had TWO other MG279Qs before = this one, both had the problem I described. The ROG forum thread I have linked s= hows the SAME artifacts I have described and these have definitely been fixed on multiple platforms by the mentioned firmware update. BTW I have tried the mclock increase before RMAing my monitor and it did not work at all. Please differentiate between the artifacts I described (left half of the sc= reen is offset to the right, a vertical stripe that should be in the middle is displayed at the left side of the screen) and other artifacts which could in fact be caused by a low mclock or other problems. The described artifacts might be fixable by software (e.g. Windows with cer= tain driver combinations does show these artifacts, but does not with others), b= ut ARE CAUSED by the faulty MG279Q firmware. I have not found any combination of OS and drivers that caused these proble= ms on the fixed monitor, but found several on multiple "not fixed" MG279Qs in = the past. --=20 You are receiving this mail because: You are the assignee for the bug.= --14972254342.E27965cA.29380 Date: Sun, 11 Jun 2017 23:57:14 +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 # 56 on bug 93826<= /a> from Eike
(In reply to iuno from comment #52)
> It could be fixed by increasing the default disp=
lay clock:
> https=
://people.freedesktop.org/~cbrill/dri-log/index.
> php?channel=3Dradeon&highlight_names=3Dagd5f;grmat&date=3D2017=
-01-03
>=20
>=20
> @Eike: you have a faulty monitor, please don't suggest people here=
 to send
> theirs back because there certainly *is* a software issue.
>=20
> @Jonas: Did you try forcing the mclock to high? It doesn't require=
 a higher
> core dpm state but should fix your problem.

Sorry to correct you, but my monitor has not been faultier than any other
MG279Q that was bought before 2017. I already had TWO other MG279Qs before =
this
one, both had the problem I described. The ROG forum thread I have linked s=
hows
the SAME artifacts I have described and these have definitely been fixed on
multiple platforms by the mentioned firmware update.

BTW I have tried the mclock increase before RMAing my monitor and it did not
work at all.

Please differentiate between the artifacts I described (left half of the sc=
reen
is offset to the right, a vertical stripe that should be in the middle is
displayed at the left side of the screen) and other artifacts which could in
fact be caused by a low mclock or other problems.

The described artifacts might be fixable by software (e.g. Windows with cer=
tain
driver combinations does show these artifacts, but does not with others), b=
ut
ARE CAUSED by the faulty MG279Q firmware.

I have not found any combination of OS and drivers that caused these proble=
ms
on the fixed monitor, but found several on multiple "not fixed" M=
G279Qs in the
past.


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