Waking/resuming from sleep/suspend

dt30 · December 24, 2024, 5:24pm

Sometime after I installed 15.6, it usually does not restore the display after sleeping. Whether it ever did, I do not remember, but it did with 15.5. I use the standard power settings of switch the screen off after 10 minutes, and suspend (sleep) session after 15 minutes. Rarely, it does redisplay the screen when pressing a key.

I found that pressing a key, will resume the computer, but the display remains blank. I found that pressing any Ctrl+Alt+F key besides F2 would bring up the display, and then pressing Ctrl+Alt+F2 will resume my display session. So on resume, I’ve been pressing the Ctrl+Alt+Fn momentarily, then Ctrl+Alt+F2. It’d be nice not to.

One time, I must have came back between the 10 and 15 minutes as the computer was still running, but the display was blank. I pressed a key, but it did not resume. So I have now unchecked the screen switching off, but that did not make a difference. Sleep probably turns it off at the 15 minutes anyway.

I have since installed 15.6 on another partition on the same drive to test if it resumes okay. It does as expected. I could proceed with setting up everything on the new partition, but that’s quite a bit of work and I’m afraid that if I install or change some certain something, it will fail to resume. It seems like it should be a simple fix. I have tried a new user on the original 15.6 and it still fails to resume the display.

> /sbin/lspci -nnk|  egrep 'VGA|3D|Display' -A3
07:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c9)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8809]
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu

inxi -GSa on the original 15.6:
(notice for whatever reason a difference between this and the new partition is this has the “Resume=”. I have removed this on grub booting but it did not help. It also has the “snd_hda_codec_hdmi…” which I fail to remember why that’s there.

> inxi -GSa
System:
  Host: localhost.localdomain Kernel: 6.4.0-150600.23.30-default arch: x86_64
    bits: 64 compiler: gcc v: 7.5.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.4.0-150600.23.30-default
    root=UUID=fd945f62-b18e-4aa9-a67c-b51c43f10b61
    resume=/dev/disk/by-uuid/3915a6e6-5a7a-41c8-ad62-d2adc6970285
    splash=silent preempt=full quiet security=apparmor
    snd_hda_codec_hdmi.enable_silent_stream=0 mitigations=auto
  Desktop: KDE Plasma v: 5.27.11 tk: Qt v: 5.15.12 wm: kwin_x11 vt: 2
    dm: SDDM Distro: openSUSE Leap 15.6
Graphics:
  Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
    vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5 code: Vega
    process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s ports: active: HDMI-A-1 empty: DP-1
    bus-ID: 07:00.0 chip-ID: 1002:1638 class-ID: 0300 temp: 25.0 C
  Display: x11 server: X.Org v: 1.21.1.11 with: Xwayland v: 24.1.1
    compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 model: Gigabyte G24F 2
    serial: 23490B004737 built: 2023 res: 1920x1080 dpi: 93 gamma: 1.2
    size: 527x296mm (20.75x11.65") diag: 595mm (23.4") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL v: 4.6 Mesa 23.3.4 renderer: AMD Radeon Graphics (radeonsi
    renoir LLVM 17.0.6 DRM 3.57 6.4.0-150600.23.30-default) direct-render: Yes

15.6 on the new partition

System:
  Host: localhost.localdomain Kernel: 6.4.0-150600.23.30-default arch: x86_64
    bits: 64 compiler: gcc v: 7.5.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.4.0-150600.23.30-default
    root=UUID=62aafc3d-a6f8-4938-8f84-0e8f9e3561e6 nosplash preempt=full
    quiet security=apparmor mitigations=auto
  Desktop: KDE Plasma v: 5.27.11 tk: Qt v: 5.15.12 wm: kwin_x11 vt: 2
    dm: SDDM Distro: openSUSE Leap 15.6
Graphics:
  Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
    vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-5 code: Vega
    process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s ports: active: HDMI-A-1 empty: DP-1
    bus-ID: 07:00.0 chip-ID: 1002:1638 class-ID: 0300 temp: 24.0 C
  Display: x11 server: X.Org v: 1.21.1.11 with: Xwayland v: 24.1.1
    compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 model: Gigabyte G24F 2
    serial: 23490B004737 built: 2023 res: 1920x1080 hz: 60 dpi: 93 gamma: 1.2
    size: 527x296mm (20.75x11.65") diag: 595mm (23.4") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: OpenGL v: 4.6 Mesa 23.3.4 renderer: AMD Radeon Graphics (radeonsi
    renoir LLVM 17.0.6 DRM 3.57 6.4.0-150600.23.30-default) direct-render: Yes

dt30 · December 24, 2024, 5:35pm

One other thing I remember is when I tried a display port cable, it did resume from suspend, but not on the HDMI cable.

Svyatko · December 26, 2024, 4:29pm

Try to upgrade BIOS.

dt30 · December 26, 2024, 5:47pm

I did. With “2.Resolved CPU exception when adjusting items like ““When system is in sleep, hibernate, or soft off states”” in certain languages.” on the bios update, kind of makes one think it could work. But I think it is a wording for certain languages. And would be odd for it to work on one partition and not the other, but could be something odd with the system.

Anyway, it didn’t resume the display when I put it to sleep.

dt30 · January 13, 2025, 1:04am

Okay, I finished setting up 15.6 on the second partition. It sleeps and resumes as should be expected. I’ve let it time out and go to sleep and did manual sleeps. Rebooted several times and have installed all the software I know of that was on the first partition. I’ve set my System Settings as much as know the same way. The only thing different is the resume= on the grub line. I have temporarily edited it out when booting the first partition, but it didn’t help. Not sure how to get it in the second partition other than, I think it’s the swap partition, and so could manually add it.

With the first partition, I have to press Alt+F something followed by Alt+F2 to resume the display. With the second partition, I just press any key.

Is there a way to compare what is different between the two partitions that might be causing the problem with the first partition?

GrandDixence2 · January 13, 2025, 12:22pm

Please check “suspend to RAM” (ACPI S3 => suspend):

# systemctl suspend

and “suspend to disk” (ACPI S4 => hibernation):

# systemctl hibernate

and publish the results.

https://wiki.archlinux.org/title/Power_management/Suspend_and_hibernate

https://www.kernel.org/doc/html/latest/admin-guide/pm/sleep-states.html

dt30 · January 13, 2025, 4:23pm

systemctl suspend on the first partition did the same as a manual suspend which required me to do the Alt+F key to get the display back

systemctl hibernate took a bit longer and when I pressed a key, rebooted and then went directly to where I left off without showing the grub menu and with the display screen visible. No Alt+F key needed.

I tried the systemctl suspend on the second partition and it suspends and on keypress brings the display back just fine. I didn’t try the hibernate on the second partition and appeared fine. I had tried the hibernate through the normal power / session menu and when it resumed, it showed the grub menu which was set to boot the old partition including resume= . I let it boot and it came back to the second partition state. If that’s confusing, I figure it might be confusing to the computer so didn’t want to try it again. Probably okay, as the second partition must have wrote it to the swap partition, but on restart, didn’t have the resume from it’s menu so when the first menu item had the resume on the entry, it knew how to resume. If I enter the resume= line for the second partition grub entry, I expect it to work as expected.

I looked at the two links, but didn’t know what to get from them. I couldn’t find anything about display not showing.