You are not logged in.
I have an RX 6800, very randomically (I'd say 1 time over 4-5) the screen goes off as soon as the WM is launched. I can see correctly the motherboard boot logo, then the bootloader menu but when it comes to i3 the screen just turns off. I use .xinitrc to startx with autologin.
The PC is actually working in background, I blindly open a terminal and issue a reboot and everything works. Switching virtual terminal doesn't bring the screen back.
I have no error whatsoever in dmesg/journalctl or xorg log, the only thing that could be somehow related is a warning that I've always got since the beginning regarding the GPU:
kernel: amdgpu 0000:09:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
kernel: [drm] psp command (0x22) failed and response status is (0x80000310)
kernel: amdgpu 0000:09:00.0: amdgpu: SMU driver if version not matched
kernel: [drm] REG_WAIT timeout 1us * 100000 tries - mpc2_assert_idle_mpcc line:480
kernel: [drm] REG_WAIT timeout 1us * 100000 tries - mpc2_assert_idle_mpcc line:480The same happens (always randomically) when resuming from sleep, but I usually just shutdown.
Any idea?
Last edited by Matt3o (2021-09-02 08:42:15)
Offline
Potentially loading race with the kernel module, does enabling https://wiki.archlinux.org/title/Kernel … _KMS_start help?
Offline
Potentially loading race with the kernel module, does enabling https://wiki.archlinux.org/title/Kernel … _KMS_start help?
thanks for your reply, I have early KMS enabled
Offline
I use .xinitrc to startx with autologin
Try disabling autologin to verify whether issue occurs before starting X .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
tried to disable autologin, it worked so far but I'll need to wait a few days to be certain. It seems it happens mostly when booting up from a cold system. If I just reboot 10 times in a row the issue rarely presents itself. I'll report back, thanks for your help.
Offline
so... I'm still not 100% sure but it seems the issue was vga=current in the kernel parameters. I added (and forgot about it) the parameter following the instructions for a quiet boot here, it was more of an experiment than a real need for it, in fact I disabled most of "silent boot" things but left the vga=current. Since when I removed that parameter everything seems to be working. I'll wait another couple of days to be certain before setting the thread as SOLVED.
Offline