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, 21 Mar 2019 22:42:57 +0000 [thread overview]
Message-ID: <bug-110217-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2083 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110217
Bug ID: 110217
Summary: RX580: screen turns black or flickers until forced
reconfiguration
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: numzer0@yandex.ru
Created attachment 143754
--> https://bugs.freedesktop.org/attachment.cgi?id=143754&action=edit
dmesg output
I have a Radeon RX560 and VGA monitor (with broken EDID) connected via a cheap
HDMI-to-VGA converter (with its own broken EDID).
The system starts up normally. During boot up, it should change display
resolution as specified in the kernel command line (`video=1280x1024-32@75`,
monitor native). Screen turns black instead, and resolution remains unchanged.
But after I plug HDMI out and in, the monitor gets new resolution and shows
console login prompt, as expected. (X isn’t configured to start at bootup).
Then, when I `startx`, it chooses the same resolution but wrong frequency (85
Hz, too much for my monitor). That’s probably due to converter supplying the
EDID. After I run `xrandr --rate 75`, it switches to the correct mode.
I wouldn’t even mention such small nuisance, but if I specify exactly the same
mode (as reported by `xrandr --verbose`) explicitly (as a `Modeline`), it works
but flickers, despite the `TearFree` option enabled. Moreover, when the monitor
is turned off and then on, it wakes up in the same mode *but flickers.*
Changing mode back and forth (`xrandr --output HDMI-A-0 --preferred ; xrandr
--rate 75`) helps.
I usually have `compton` running. Without it, flicker is tolerable but still
present.
OS: Arch Linux
Kernel: Linux 5.0.1-arch1-1-ARCH
X driver: xf86-video-amdgpu 19.0.0-1
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3496 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 reply other threads:[~2019-03-21 22:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 22:42 bugzilla-daemon [this message]
2019-03-21 22:43 ` [Bug 110217] RX580: screen turns black or flickers until forced reconfiguration 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
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@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).