From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 97896] RADEON DisplayPort - Monitor shows out of range in some modes Date: Wed, 20 Dec 2017 21:06:22 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0792497607==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 4D2706E53D for ; Wed, 20 Dec 2017 21:06:22 +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 --===============0792497607== Content-Type: multipart/alternative; boundary="15138039820.bb3178D7.9761"; charset="UTF-8" --15138039820.bb3178D7.9761 Date: Wed, 20 Dec 2017 21:06:22 +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=3D97896 --- Comment #5 from Stefan M=C3=BCller-Klieser --- I have probably the same issue on 4.14.5. My setup works fine with Redmond = OS. This thread helped me to find the workaround under Linux with radeon.audio= =3D0. One additional information about the issue: The out of range error probably comes from a complete miscalculation of the pixel clock. Edid of the monitor is fine, but in the error case, every pixel clock, the radeon wants to setup, is completely off from the edid modes. I checked by comparing the pixel clocks reported by the monitor with the one radeon reports. I can test patches or post more debug info. Cheers. --=20 You are receiving this mail because: You are the assignee for the bug.= --15138039820.bb3178D7.9761 Date: Wed, 20 Dec 2017 21:06:22 +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

Comment= # 5 on bug 97896<= /a> from Stefan M=C3=BCll= er-Klieser 
I have probably the same issue on 4.14.5. My setup works fine =
with Redmond OS.
This thread helped me to find the workaround under Linux with radeon.audio=
=3D0.
One additional information about the issue:
The out of range error probably comes from a complete miscalculation of the
pixel clock. Edid of the monitor is fine, but in the error case, every pixel
clock, the radeon wants to setup, is completely off from the edid modes. I
checked by comparing the pixel clocks reported by the monitor with the one
radeon reports. I can test patches or post more debug info. Cheers.

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