Summary
The system improperly suspends with varying results based on the running kernel:
-
Running the Fedora 44 Cinnamon Live CD kernel 6.19.10-300.fc44 with software rendering does not turn off the screen when asked to suspend and simply displays the greeter until the mouse/keyboard is used to re-enter the Live CD environment.
-
Kernels 6.19.8.3-surface and 7.1.8-200.fc44 with proprietary nvidia drivers appear to suspend correctly and turns off all screens. Attempting to wake up the system is unsuccessful through mouse and keyboard input. Screen will display again using the Power button, and makes Caps Lock and Number Lock indicator lights function on the keyboard, but dmesg output indicates the power button press may have begun system shutdown instead of waking up from suspend. System's attempt to shutdown appears to have failed as all displays are still on with nothing displayed and keyboard appears functional.
Device
Steps taken / diagnosis
- Attempt to suspend system using the desktop environment or systemctl suspend
- On vanilla Fedora kernels using software rendering, the system returns to the greeter and does not appear to suspend.
- On vanilla Fedora kernels and 6.19.8.3-surface with the proprietary nvidia driver the system turns off all displays and appears to suspend.
- Attempt to wake system by using the keyboard, mouse, touch input, pen, or power button
- On vanilla Fedora kernels using software rendering, the system already appears awake and interactions are normal.
- On vanilla Fedora kernels and 6.19.8.3-surface with the proprietary nvidia driver the display backlights will turn on and keyboard appears functional (Caps Lock and Number Lock indicator lights appear operative) but nothing will display. Unable to power off the system except by holding down the power button.
[s2idle] appears to be the only available sleep state on the Fedora vanilla kernels when checking /sys/power/mem_sleep. Running S0ix Selftest Tool with -s and -r parameters on 7.1.8-200.fc44 fail. Attempting to place system into s2idle via rtcwake -m freeze -s 15 as recommended by s0ix-selftest-tool.sh -s fails.
Attempts to disable Modern Standby/S0ix to utilize S3 (deep sleep) instead appear impossible as UEFI/BIOS has no option to disable Modern Standby/S0ix.
Expected behaviors
The system should be able to power down components to a suspend state, and should wake up as normal once any input interaction occurs. Additionally, for systems running with the proprietary nvidia driver, the system should run scripts to properly wake up the GPU.
Notes
- Waking up the proprietary nvidia driver after suspend may be out of scope of the linux-surface project and other resources may be helpful to get the system to properly wake from suspend.
- I am happy to provide additional logs and check /sys/power/mem_sleep from kernel 6.19.8.3-surface to assist, and will be able to do so starting next week, 24 August 2026.
Reactions are currently unavailable
Summary
The system improperly suspends with varying results based on the running kernel:
Running the Fedora 44 Cinnamon Live CD kernel 6.19.10-300.fc44 with software rendering does not turn off the screen when asked to suspend and simply displays the greeter until the mouse/keyboard is used to re-enter the Live CD environment.
Kernels 6.19.8.3-surface and 7.1.8-200.fc44 with proprietary nvidia drivers appear to suspend correctly and turns off all screens. Attempting to wake up the system is unsuccessful through mouse and keyboard input. Screen will display again using the Power button, and makes Caps Lock and Number Lock indicator lights function on the keyboard, but dmesg output indicates the power button press may have begun system shutdown instead of waking up from suspend. System's attempt to shutdown appears to have failed as all displays are still on with nothing displayed and keyboard appears functional.
Device
Steps taken / diagnosis
[s2idle] appears to be the only available sleep state on the Fedora vanilla kernels when checking /sys/power/mem_sleep. Running S0ix Selftest Tool with -s and -r parameters on 7.1.8-200.fc44 fail. Attempting to place system into s2idle via rtcwake -m freeze -s 15 as recommended by s0ix-selftest-tool.sh -s fails.
Attempts to disable Modern Standby/S0ix to utilize S3 (deep sleep) instead appear impossible as UEFI/BIOS has no option to disable Modern Standby/S0ix.
Expected behaviors
The system should be able to power down components to a suspend state, and should wake up as normal once any input interaction occurs. Additionally, for systems running with the proprietary nvidia driver, the system should run scripts to properly wake up the GPU.
Notes