Jul 06 08:43:11 IdeaPad kscreen_backend_launcher[937]: kscreen.xrandr: XRandR::setConfig
Jul 06 08:43:11 IdeaPad kscreen_backend_launcher[937]: kscreen.xrandr: Requested screen size is QSize(1920, 1080)
Jul 06 08:43:11 IdeaPad kscreen_backend_launcher[937]: kscreen.xrandr: Needed CRTCs: 1
Jul 06 08:43:11 IdeaPad kscreen_backend_launcher[937]: kscreen.xrandr: Actions to perform:
Primary Output: false
Jul 06 08:43:11 IdeaPad kscreen_backend_launcher[937]: kscreen.xrandr: Change Screen Size: false
Jul 06 08:43:11 IdeaPad kscreen_backend_launcher[937]: kscreen.xrandr: Disable outputs: false
Jul 06 08:43:11 IdeaPad kscreen_backend_launcher[937]: kscreen.xrandr: Change outputs: false
Jul 06 08:43:11 IdeaPad kscreen_backend_launcher[937]: kscreen.xrandr: Enable outputs: false
Jul 06 08:43:11 IdeaPad kscreen_backend_launcher[937]: kscreen.xrandr: XRandR::setConfig done!
Gonna update the thread title because of this information. Probably isn't a kernel issue, but a KDE Plasma issue.
]]>Also I just got the issue again, I got the journalctl of the previous state, and I got
[drm] pstate TEST_DEBUG_DATA: 0x3EFE0000
pasted over and over at the end of the logs, right where the screen blackening occurred, and looking up the error, it appears that it isn't a unique issue, and other AMD APU, even previous gen users are experiencing a similar issue
https://forum.endeavouros.com/t/amd-apu … 10/12499/5
sudo journalctl -b-1 | curl -F 'f:1=<-' ix.io
you'll get a link.
]]>sudo journalctl -b -1 |cat
Check/post a journal log when you get the issue
sudo journalctl -b
If you can get it from the current boot, otherwise add -1 for the boot prior to your current one if you're forced to reboot. https://wiki.archlinux.org/title/List_o … n_services
]]>