From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92977] Display artifacts when using MST
Date: Tue, 17 Nov 2015 08:10:23 +0000 [thread overview]
Message-ID: <bug-92977-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2496 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92977
Bug ID: 92977
Summary: Display artifacts when using MST
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: dan.doel@gmail.com
Created attachment 119730
--> https://bugs.freedesktop.org/attachment.cgi?id=119730&action=edit
image 1 - half of window uses different colors
I've been trying out the support for tiled MST monitors on Radeon drivers, and
seem to be encountering some visual anomalies that seem like they are likely to
be related to this component.
My setup is two UP2414Q monitors, which have native resolutions of 3840x2160.
Over DisplayPort 1.2, they are capable of running as two 1920x2160@60 displays
each. I have a nvidia card that is capable of driving them in this mode, so I
am reasonably sure that the hardware isn't the problem (unless it is the Radeon
card, but that seems unlikely).
First, there seems to be a color anomaly with the primary display. The right
half of the display has different colors from the left (see first image). I
noticed that this may be due to the left half displaying a different color
depth than the right. The second image shows the gnome overlay, and while the
shadows are smooth on the right, there is banding on the left. My second
monitor seems to have both sides in this reduced color mode, and enough
fiddling with settings after a boot causes both halves of the primary monitor
to be configured that way as well, but needless to say, the reduced color depth
(if that's what it is) is undesirable.
Second, the secondary monitor has some visual artifacts to the left of center
(a vertical band about an inch wide) as well as to the far right (a vertical
band around 1/4 inch wide). The third image should give some idea what it looks
like. A better photo might show that things in that region look somewhat
interlaced, and are repeated horizontally.
I apologize for the poor quality of the images, but screenshots don't capture
these artifacts, so I had to use my phone.
I'm running with packages from Fedora 23, so xorg-server 1.18.0, xf86-video-ati
7.6.0-0.4.20150729git5510cd6, kernel 4.2.5-300. If you'd like any other
information, let me know.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3897 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-11-17 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 8:10 bugzilla-daemon [this message]
2015-11-17 8:10 ` [Bug 92977] Display artifacts when using MST bugzilla-daemon
2015-11-17 8:11 ` bugzilla-daemon
2015-11-17 9:09 ` bugzilla-daemon
2015-11-17 9:10 ` bugzilla-daemon
2015-11-17 23:43 ` bugzilla-daemon
2015-11-19 3:44 ` bugzilla-daemon
2015-11-21 16:42 ` bugzilla-daemon
2019-11-20 8:03 ` 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-92977-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.