From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101290] Radeon R9 390X regression - No output (CVT) or corruption (CVT-R) at 4096x2160@60Hz over DisplayPort
Date: Sat, 03 Jun 2017 17:21:57 +0000 [thread overview]
Message-ID: <bug-101290-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1745 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101290
Bug ID: 101290
Summary: Radeon R9 390X regression - No output (CVT) or
corruption (CVT-R) at 4096x2160@60Hz over DisplayPort
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: freedesktop@nuclearsunshine.com
I had thought I had filed this bug a long time ago on here, but I can't find
it...
Graphics card: Radeon R9 390X (Saphhire 11241-04-20G)
Display: LG 31MU97 (via DisplayPort)
With Linux 4.4.x, 4096 x 2160 @ 60 Hz progressive output was working with
standard CVT timing.
With Linux 4.5.x onwards, standard CVT timing at that resolution fails (no
signal) with the following dmesg output:
kernel: [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed
kernel: [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 5 tries
CVT-R timing results in output, but with a flickering/corrupted full-height
band down the right hand side (it approximates the intended output, but pixels
seem be to be corrupt in single-pixel horizontal bands and/or flicker in
horizontal single-pixel bands) It could be complete coincidence, but the width
of the corrupt band seems to be the difference in width vs. 3840x2160, i.e.
aobut 256 pixels. With this timing there are no messages in dmesg.
There's a downstream Fedora bug report here:
https://bugzilla.redhat.com/show_bug.cgi?id=1353341
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3150 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 reply other threads:[~2017-06-03 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 17:21 bugzilla-daemon [this message]
2017-06-05 2:41 ` [Bug 101290] Radeon R9 390X regression - No output (CVT) or corruption (CVT-R) at 4096x2160@60Hz over DisplayPort bugzilla-daemon
2017-06-05 10:26 ` bugzilla-daemon
2019-11-19 9:29 ` 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-101290-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.