You are not logged in.
I already checked this post https://bbs.archlinux.org/viewtopic.php?id=249418 and changed `MODULES=(radeon)` and `mkinitcpio -P` but that also didn't help.
I have a AMD CPU & GPU both. I don't see any errors in `journalctl -b -u sddm` or anything relevant in `journalctl -b`.
How do I investigate this and fix this?
`journalctl -b -u sddm` : https://bpa.st/7GHLI
Last edited by adityagupta1089 (2023-04-23 22:40:21)
Offline
systemctl status sddm # before you restart it and post the journal.
The symptoms smell a lot like early kms, though - do you even use the radeon module (or amdgpu)?
lsmod | grep -E '(radeon|amdgpu)'Offline
systemctl status sddm # before you restart itand post the journal.
The symptoms smell a lot like early kms, though - do you even use the radeon module (or amdgpu)?lsmod | grep -E '(radeon|amdgpu)'
http://0x0.st/HKNV.txt for the last command
and http://0x0.st/HKNf.txt for the journalctl log
Offline
Did you look at the grep?
Now look at
lspci -kOffline
I think amdgpu is in use, lspci -k shows that here: 0x0.st/HKNt.txt
Offline
Thanks, changed the module to `amdgpu` in mkinitcpio.conf and it worked! Thank you for your prompt replies and helping me out. Is the the preferred solution or just a workaround around something major?
Offline
The kms HOOK should™ have caught that, but some form of early kms is necessary in this setup because systemd starts the graphical.target unconditionally and early.
(I guess editing the service and depending it on /sys/class/drm/card0 might do as well, but has no benefits)
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline