From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110217] RX580: screen turns black or flickers until forced reconfiguration
Date: Thu, 23 May 2019 18:25:23 +0000 [thread overview]
Message-ID: <bug-110217-502-FsNLgpsl0V@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110217-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1022 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110217
--- Comment #3 from numzer0@yandex.ru ---
New information:
1. Screen turns black at module insertion, be it during bootup or later. But
resuming from hibernation works.
2. On the system, the converter I use is problematic itself. When I connect it
to another PC, HDMI port is shown as “connected” *until* I connect a monitor to
the converter. Then, everything works but HDMI port is displayed as
“disconnected” in xrandr.
After updating the system, flicker seems to happen in X only, despite the
“TearFree” option. Virtual consoles work well, albeit use the same mode (i.e.
no mode change on VT switch). Not sure was that the case earlier.
Also, after last hibernation, the old trick with resetting mode didn’t help,
flicker continues. New X instances flicker as well.
New kernel: Linux 5.1.2-arch1-1-ARCH
New X driver: xf86-video-amdgpu 19.0.1-1
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1815 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-23 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 22:42 [Bug 110217] RX580: screen turns black or flickers until forced reconfiguration bugzilla-daemon
2019-03-21 22:43 ` bugzilla-daemon
2019-03-21 22:48 ` bugzilla-daemon
2019-03-25 10:15 ` bugzilla-daemon
2019-03-25 10:15 ` bugzilla-daemon
2019-05-23 18:25 ` bugzilla-daemon [this message]
2019-05-23 18:29 ` bugzilla-daemon
2019-05-23 19:09 ` bugzilla-daemon
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-110217-502-FsNLgpsl0V@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;
as well as URLs for NNTP newsgroup(s).