GUI fails to show back up after waking up from sleep.

Quardah · 2023-10-10 16:43:57

Hi.

I am using KDE on P16s. I am using the amdgpu driver because the alternative gives poor results with this hardware.

I found this thread but i am having a different issue : https://bbs.archlinux.org/viewtopic.php?id=288250

When waking from sleep, the screen do wake up and i can see the backlight showing. The mouse cursor is working, and it's KDE's cursor. But i am not prompted for a login or anything. The screen remain showing a black background and i have to hard shutdown. Maybe SDDM?

It does not happen everytime but when it happens i lose everything because i found no other way than a hard shutdown. This is recent behavior. I did several updates in the past few months so i can't pinpoint exactly when it started happening.

What should i do to debug this issue?

[main@P16s ~]$ sudo lshw -c video
  *-display                 
       description: VGA compatible controller
       product: Rembrandt [Radeon 680M]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 0
       bus info: pci@0000:04:00.0
       logical name: /dev/fb0
       version: d1
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi msix vga_controller bus_master cap_list fb
       configuration: depth=32 driver=amdgpu latency=0 mode=1920x1200 resolution=2560,1600 visual=truecolor xres=1920 yres=1200
       resources: iomemory:80-7f iomemory:80-7f irq:39 memory:8b0000000-8bfffffff memory:8c0000000-8c01fffff ioport:1000(size=256) memory:80800000-8087ffff

seth · 2023-10-10 20:55:29

I am using the amdgpu driver because the alternative gives poor results with this hardware.

Are you taklking about xf86-video-amdgpu? There're no alternatives to the amdgpu kernel module for your GPU.

i found no other way than a hard shutdown

mouse cursor is working, and it's KDE's cursor

1. try to suspend the compositor (SHIFT+Alt+F12)
2. try to switch to another TTY (ctrl+alt+F2,F3,F4,…)
3. https://wiki.archlinux.org/title/Keyboa … el_(SysRq)

In any event, please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General - you also seem to be scaling the output?

Quardah · 2023-10-10 21:54:05

seth wrote:

I am using the amdgpu driver because the alternative gives poor results with this hardware.
Are you taklking about xf86-video-amdgpu? There're no alternatives to the amdgpu kernel module for your GPU.
i found no other way than a hard shutdown
mouse cursor is working, and it's KDE's cursor
1. try to suspend the compositor (SHIFT+Alt+F12)
2. try to switch to another TTY (ctrl+alt+F2,F3,F4,…)
3. https://wiki.archlinux.org/title/Keyboa … el_(SysRq)
In any event, please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General - you also seem to be scaling the output?

Hi and thanks for the quick reply.

I recall using no drivers as in using modesetting instead, but i had crashes with firefox and overall bad performances with multiple monitors.

I don't think i am scalling the output? Can you point what is letting you believe this?

Next time i have this behaviour i will switch to another TTY and save the Xorg log file as you mentioned. Right now it has nothing because the file has been created after the last crash probably on reboot.

seth · 2023-10-11 06:32:25

Try modesetting again and esp. post your xorg log (w/ and w/o xf86-video-amdgpu)

configuration: depth=32 driver=amdgpu latency=0 mode=1920x1200 resolution=2560,1600 visual=truecolor xres=1920 yres=1200

Quardah · 2023-10-11 16:15:46

seth wrote:

Try modesetting again and esp. post your xorg log (w/ and w/o xf86-video-amdgpu)
configuration: depth=32 driver=amdgpu latency=0 mode=1920x1200 resolution=2560,1600 visual=truecolor xres=1920 yres=1200

I have three monitors two of them being 2560x1600 and one of them sideways being 1200x1920. I only did place them in KDE settings, i have no explicitly tried scaling them up.

I did not get a crash this morning.

Quardah · 2023-10-18 14:39:41

seth wrote:

post your xorg log

I got the issue this morning. I managed to unbug the issue doing the following :

1 - Login into another TTY (CTRL + ALT + F5)
2 - systemctl suspend
3 - wake the system
4 - sddm showed up

I think the problem lies in sddm not showing up properly on wake always reliably. Because the cursor shows up all the time but not the login prompt and the background. I notice that sddm always "fades in" from a black background on wake, but it seems like something this fade in hangs and i am left with nothing. suspending and rewaking retriggers the fade in and allows me to log back in.

These are the last line of my Xorg.0.log file. These are repeated several times :

[162265.142] (II) AIGLX: Suspending AIGLX clients for VT switch
[162333.518] (II) AIGLX: Resuming AIGLX clients after VT switch
[162333.578] (II) AMDGPU(0): EDID vendor "ACI", prod id 9393
[162333.578] (II) AMDGPU(0): Using hsync ranges from config file
[162333.578] (II) AMDGPU(0): Using vrefresh ranges from config file
[162333.578] (II) AMDGPU(0): Printing DDC gathered Modelines:
[162333.578] (II) AMDGPU(0): Modeline "1920x1200"x0.0  154.00  1920 1968 2000 2080  1200 1203 1209 1235 +hsync -vsync (74.0 kHz eP)
[162333.578] (II) AMDGPU(0): Modeline "1920x1080"x0.0  138.50  1920 1968 2000 2080  1080 1083 1088 1110 +hsync -vsync (66.6 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1366x768"x0.0   85.50  1366 1436 1579 1792  768 771 774 798 +hsync +vsync (47.7 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1280x720"x0.0   74.25  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "720x480"x0.0   27.00  720 736 798 858  480 489 495 525 -hsync -vsync (31.5 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1920x1080i"x0.0   74.25  1920 2008 2052 2200  1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "720x576"x0.0   27.00  720 732 796 864  576 581 586 625 -hsync -vsync (31.2 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1280x720"x0.0   74.25  1280 1720 1760 1980  720 725 730 750 +hsync +vsync (37.5 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1920x1080i"x0.0   74.25  1920 2448 2492 2640  1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1920x1080"x0.0  148.50  1920 2448 2492 2640  1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync (35.2 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync (37.5 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync (37.9 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync (35.0 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync (31.5 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync +vsync (60.0 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync -vsync (56.5 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync (49.7 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync (46.9 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync (48.1 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync +vsync (67.5 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1280x960"x0.0  108.00  1280 1376 1488 1800  960 961 964 1000 +hsync +vsync (60.0 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1440x900"x0.0   88.75  1440 1488 1520 1600  900 903 909 926 +hsync -vsync (55.5 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1600x1200"x0.0  162.00  1600 1664 1856 2160  1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[162333.578] (II) AMDGPU(0): Modeline "1680x1050"x0.0  119.00  1680 1728 1760 1840  1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[162333.608] (II) event3  - Power Button: is tagged by udev as: Keyboard
[162333.608] (II) event3  - Power Button: device is a keyboard
[162333.610] (II) event4  - Video Bus: is tagged by udev as: Keyboard
[162333.610] (II) event4  - Video Bus: device is a keyboard
[162333.611] (II) event0  - Power Button: is tagged by udev as: Keyboard
[162333.611] (II) event0  - Power Button: device is a keyboard
[162333.612] (II) event2  - Sleep Button: is tagged by udev as: Keyboard
[162333.612] (II) event2  - Sleep Button: device is a keyboard
[162333.613] (II) event15 - ELAN0689:00 04F3:320C Mouse: is tagged by udev as: Mouse Pointingstick
[162333.614] (II) event15 - ELAN0689:00 04F3:320C Mouse: device is a pointer
[162333.616] (II) event16 - ELAN0689:00 04F3:320C Touchpad: is tagged by udev as: Touchpad
[162333.617] (II) event16 - ELAN0689:00 04F3:320C Touchpad: device is a touchpad
[162333.619] (II) event5  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[162333.619] (II) event5  - AT Translated Set 2 keyboard: device is a keyboard
[162333.621] (II) event17 - TPPS/2 Elan TrackPoint: is tagged by udev as: Mouse Pointingstick
[162333.621] (II) event17 - TPPS/2 Elan TrackPoint: device is a pointer
[162333.622] (II) event11 - ThinkPad Extra Buttons: is tagged by udev as: Keyboard Switch
[162333.622] (II) event11 - ThinkPad Extra Buttons: device is a keyboard
[162333.682] (II) event6  - USB Optical Mouse: is tagged by udev as: Mouse
[162333.682] (II) event6  - USB Optical Mouse: device is a pointer
[162341.027] (II) event3  - Power Button: device removed
[162341.062] (II) event4  - Video Bus: device removed
[162341.125] (II) event0  - Power Button: device removed
[162341.152] (II) event2  - Sleep Button: device removed
[162341.178] (II) event15 - ELAN0689:00 04F3:320C Mouse: device removed
[162341.242] (II) event16 - ELAN0689:00 04F3:320C Touchpad: device removed
[162341.295] (II) event5  - AT Translated Set 2 keyboard: device removed
[162341.335] (II) event17 - TPPS/2 Elan TrackPoint: device removed
[162341.388] (II) event11 - ThinkPad Extra Buttons: device removed
[162341.405] (II) event6  - USB Optical Mouse: device removed
[162341.489] (II) AIGLX: Suspending AIGLX clients for VT switch

Maybe a peripheral is causing it to hang sometimes?

seth · 2023-10-18 15:00:09

[162265.142] (II) AIGLX: Suspending AIGLX clients for VT switch
[162333.518] (II) AIGLX: Resuming AIGLX clients after VT switch

1 - Login into another TTY (CTRL + ALT + F5)

Then the WUXGA output gets re-polled.

The login screen you're seeing after the S3 isn't SDDM but kscreenlocker.
Since you can switch to a different VT, you could try to suspend the compositor from there
"qdbus org.kde.KWin /KWin toggleCompositing"
or maybe
"qdbus org.kde.KWin /Compositor suspend"
(I've no idea what KWin's dbus interface looks like these days, so maybe test that beforehand)

Arch Linux

#1 2023-10-10 16:43:57

GUI fails to show back up after waking up from sleep.

#2 2023-10-10 20:55:29

Re: GUI fails to show back up after waking up from sleep.

#3 2023-10-10 21:54:05

Re: GUI fails to show back up after waking up from sleep.

#4 2023-10-11 06:32:25

Re: GUI fails to show back up after waking up from sleep.

#5 2023-10-11 16:15:46

Re: GUI fails to show back up after waking up from sleep.

#6 2023-10-18 14:39:41

Re: GUI fails to show back up after waking up from sleep.

#7 2023-10-18 15:00:09

Re: GUI fails to show back up after waking up from sleep.

Board footer