You are not logged in.
Problem:
In Gnome (3.36.5 + Wayland), when the screen goes blank after a set timeout, the monitor goes into a "standby mode" (or something like that). But when a keyboard button is pressed or mouse is moved, the monitor wakes up but says there is no signal (it is connected via DisplayPort). To get an image on the monitor, I have to either unplug the DP cable, or turn the monitor off (manually from its power button) and turn it back on again. Switching to different TTY with Alt+Ctrl+F1...F7 doesn't do anything. Gnome Shell is on TTY2 and GDM Login Screen on TTY1, others drop me to terminal.
And I cannot find errors anywhere. I've looked through /var/log/* files, dmesg, journalctl, systemctl, and ~/*, there are no errors (or even events!) produced when the monitor is supposed to be waking up.
I've had this installation since 2018-02-06 and I've updated it daily.
$ awk -F "[[ ]" 'NR==1 {print $2;}' /var/log/pacman.log
2018-02-06This problem only started with upgrade to Linux 5.8.x. It doesn't manifest in 5.7.x or earlier nor in LTS 5.4.x. My work around has been to switch to LTS instead of the main stable. I've now lost the 5.7.x from the /var/cache/pacman/pkg as it keeps only the last 3 versions and we are on 5.8.3 already (I've got 5.8.1, 5.8.2 and 5.8.3 in the cache).
Hardware info:
Vega 64, Ryzen 1800x, Prime X370-Pro, Samsung LC32HG70QQUXEN with ver 1019.2 Firmware
Blank Screen Settings in Gnome:
Settings -> Power -> Power Saving -> Blank Screen
or:
Settings -> Privacy -> Screen Lock -> Blank Screen Delay
Some things I've tried:
Changing the Blank Screen delay time makes no difference to the behaviour. Neither does the automatic screen lock make any difference.
I've tried the Dynamic power management for ATI/AMD, I've tried all the levels, and even rebooted between the settings.
I've tried different Mesa versions and it made no difference.
I've read through the bug reports for linux, mesa, linux-lts and linux-zen in the Arch packages to see if anyone has reported this. I've also tried searching the forums.
Added/removed amdgpu to /etc/mkinitcpio.conf inside MODULES() line (I saw this on an unrelated thread on the forums).
Only thing that made a difference was to downgrade the kernel to any version before 5.8
I've also tried a bunch of other stuff that I'm forgetting now.
Gnome is started by systemd gdm.service at boot.
I really want to find an error message, so I can either resolve the problem or submit a bug report, but I'm at a loss where this could reported. Where else could I look for error messages?
Last edited by anon5 (2020-08-29 09:21:56)
Offline
Linux 5.8.4 update fixed the issue. Whoever fixed it: thank you!
Linux 5.8.5 (the latest as of writing) still has it fixed and the problem hasn't come back!
Anyone on 5.8.1 - 5.8.3, the fix is to update to 5.8.4 or 5.8.5 (and possibly any later kernel too).
Last edited by anon5 (2020-08-29 09:23:26)
Offline