From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97896] RADEON DisplayPort - Monitor shows out of range in some modes
Date: Wed, 20 Dec 2017 21:06:22 +0000 [thread overview]
Message-ID: <bug-97896-502-yAlvIPnC0h@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97896-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 792 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97896
--- Comment #5 from Stefan Müller-Klieser <stefan.mueller-klieser@web.de> ---
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=0.
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.
[-- Attachment #1.2: Type: text/html, Size: 1617 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:[~2017-12-20 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 13:18 [Bug 97896] RADEON DisplayPort - Monitor shows out of range in some modes bugzilla-daemon
2016-09-22 13:19 ` bugzilla-daemon
2016-09-22 13:19 ` bugzilla-daemon
2016-09-22 13:19 ` bugzilla-daemon
2016-09-22 13:19 ` bugzilla-daemon
2017-12-20 21:06 ` bugzilla-daemon [this message]
2019-11-19 9:18 ` 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-97896-502-yAlvIPnC0h@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