From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105177] amdgpu wrong colors with rx460 connected via hdmi
Date: Thu, 29 Mar 2018 13:25:17 +0000 [thread overview]
Message-ID: <bug-105177-502-AN3S5OTBNv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105177-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 996 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105177
--- Comment #20 from Reimar Imhof <tuxuser@quantentunnel.de> ---
I've tried drm-next-4.17-wip.
What I've seen is the same as described with the initial bug description:
When monitor is connected via hdmi I get wrong colors. This appears during boot
before the gui (x.org) gets started (frame buffer boot animation). Wrong colors
(sort of violet instead of black) also appear on frame buffer text console and
with x.org gui.
This bug appears with "amdgpu.dc=1" kernel parameter.
While running x.org I've turned the monitor off and on again. This gives
correct colors but the screen resolution goes to 1024x768. So it's no work
around.
What I've seen is: The colors are correct if I run the monitor with a yuv color
model instead of rgb.
One thing seems to be better: Every boot manged to get to the graphical login.
I've tried about 10 reboots.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1795 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:[~2018-03-29 13:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 21:04 [Bug 105177] amdgpu wrong colors with rx460 connected via hdmi bugzilla-daemon
2018-02-20 21:04 ` bugzilla-daemon
2018-02-20 21:05 ` bugzilla-daemon
2018-02-20 21:05 ` bugzilla-daemon
2018-02-20 22:02 ` bugzilla-daemon
2018-02-20 22:02 ` bugzilla-daemon
2018-02-21 21:37 ` bugzilla-daemon
2018-02-21 21:38 ` bugzilla-daemon
2018-02-21 21:39 ` bugzilla-daemon
2018-02-21 21:39 ` bugzilla-daemon
2018-02-21 21:40 ` bugzilla-daemon
2018-02-21 21:42 ` bugzilla-daemon
2018-02-21 22:04 ` bugzilla-daemon
2018-02-22 20:19 ` bugzilla-daemon
2018-02-24 10:57 ` bugzilla-daemon
2018-02-24 10:58 ` bugzilla-daemon
2018-02-24 10:59 ` bugzilla-daemon
2018-02-24 11:00 ` bugzilla-daemon
2018-03-27 15:36 ` bugzilla-daemon
2018-03-27 16:48 ` bugzilla-daemon
2018-03-29 13:25 ` bugzilla-daemon [this message]
2018-03-29 13:34 ` bugzilla-daemon
2018-04-17 18:13 ` bugzilla-daemon
2019-11-19 8: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-105177-502-AN3S5OTBNv@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