| Bug ID | 110217 |
|---|---|
| Summary | RX580: screen turns black or flickers until forced reconfigur= ation |
| 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 =
[details]
dmesg output
I have a=C2=A0Radeon RX560 and VGA monitor (with broken EDID) connected via=
a=C2=A0cheap
HDMI-to-VGA converter (with its own broken EDID).
The=C2=A0system starts up normally. During boot up, it should change display
resolution as=C2=A0specified in the=C2=A0kernel command line (`video=3D1280=
x1024-32@75`,
monitor native). Screen turns black instead, and resolution remains unchang=
ed.
But after I plug HDMI out and in, the=C2=A0monitor gets new resolution and =
shows
console login prompt, as expected. (X isn=E2=80=99t configured to=C2=A0star=
t at bootup).
Then, when I `startx`, it chooses the=C2=A0same resolution but wrong freque=
ncy (85
Hz, too much for my monitor). That=E2=80=99s probably due to=C2=A0converter=
supplying the
EDID. After I run `xrandr --rate 75`, it switches to=C2=A0the=C2=A0correct =
mode.
I wouldn=E2=80=99t even mention such small nuisance, but if I specify exact=
ly the same
mode (as reported by `xrandr --verbose`) explicitly (as a=C2=A0`Modeline`),=
it works
but flickers, despite the=C2=A0`TearFree` option enabled. Moreover, when th=
e 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
Created attachment 143755 [detai=
ls]
Xorg log
Created attachment 143756 [d=
etails]
Xorg config
If I uncomment the proper `Output-...` option, Xorg starts in the correct m=
ode
but with flicker. That=E2=80=99s true both for `amdgpu` and `modesetting` d=
rivers IIRC.
| What | Removed | Added |
|---|---|---|
| Attachment #143754 mime type | text/x-log | text/plain |
| What | Removed | Added |
|---|---|---|
| Attachment #143755 mime type | text/x-log | text/plain |
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 =E2=80=9Cconnected=E2=80=9D *until* I = connect a=C2=A0monitor to the=C2=A0converter. Then, everything works but HDMI port is displayed as =E2=80=9Cdisconnected=E2=80=9D in xrandr. After updating the system, flicker seems to happen in X only, despite the =E2=80=9CTearFree=E2=80=9D option. Virtual consoles work well, albeit use t= he 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=E2=80= =99t help, flicker continues. New X instances flicker as well.=20 New kernel: Linux 5.1.2-arch1-1-ARCH New X driver: xf86-video-amdgpu 19.0.1-1
Just downgraded xf86-video-amdgpu back to 19.0.0-1. The flicke= r disappeared.
The flicker seems to be due to https://bugs.freedesktop.org/show_bug.= cgi?id=3D102646, despite the fact Arch wiki tells that affects 120+=C2=A0Hz only (my monitor runs at=C2=A075 Hz). At le= ast fixing clocks fixes the problem.
| What | Removed | Added |
|---|---|---|
| Status | NEW | RESOLVED |
| Resolution | --- | MOVED |
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this = link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/733.