Hi everyone,
I just got a brand new PC. Here are the specs:
I'm having an issue with the Suspend feature. When I click on Suspend, or if I'm idle for about 15 minutes, the screen turns black and I return to the lock screen, but the computer doesn't actually suspend. If I'm idle for more than 30 minutes, the screen turns black, and sometimes I can't recover from it, so I have to power off the computer.
Does anyone know why my computer isn't properly entering suspended mode?
Thanks!
You could take a Look in the Settings>Energy and Settings>Privacy>Display. There You can find Settings for that and try it out.
Thanks but the issue seems to be my onboard wifi card which use ath12k_pci drivers and this driver is not in the 6.8 kernel. It's start to rollout on 6.9.
This is logs when I want to suspend
Oct 08 09:47:33 Felix-PC ModemManager[2259]: <info> [sleep-monitor-systemd] system is about to suspend
Oct 08 09:47:35 Felix-PC systemd[1]: monitor-sleep-fix.service: Found ordering cycle on suspend.target/start
Oct 08 09:47:35 Felix-PC systemd[1]: monitor-sleep-fix.service: Found dependency on systemd-suspend.service/start
Oct 08 09:47:36 Felix-PC systemd[1]: Starting NVIDIA system suspend actions...
░░ Subject: A start job for unit nvidia-suspend.service has begun execution
░░ A start job for unit nvidia-suspend.service has begun execution.
Oct 08 09:47:36 Felix-PC suspend[7914]: nvidia-suspend.service
Oct 08 09:47:36 Felix-PC logger[7914]: <13>Oct 8 09:47:36 suspend: nvidia-suspend.service
Oct 08 09:47:36 Felix-PC systemd[1]: nvidia-suspend.service: Deactivated successfully.
░░ The unit nvidia-suspend.service has successfully entered the 'dead' state.
Oct 08 09:47:36 Felix-PC systemd[1]: Finished NVIDIA system suspend actions.
░░ Subject: A start job for unit nvidia-suspend.service has finished successfully
░░ A start job for unit nvidia-suspend.service has finished successfully.
░░ Subject: A start job for unit systemd-suspend.service has begun execution
░░ A start job for unit systemd-suspend.service has begun execution.
Oct 08 09:47:36 Felix-PC systemd-sleep[7932]: Entering sleep state 'suspend'...
░░ Subject: System sleep state suspend entered
░░ The system has now entered the suspend sleep state.
Oct 08 09:47:36 Felix-PC kernel: PM: suspend entry (deep)
Oct 08 09:47:40 Felix-PC kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Oct 08 09:47:40 Felix-PC kernel: ath12k_pci 0000:05:00.0: failed to suspend core: -95
Oct 08 09:47:40 Felix-PC kernel: ath12k_pci 0000:05:00.0: PM: pci_pm_suspend(): ath12k_pci_pm_suspend+0x0/0x60 [ath12k] returns -95
Oct 08 09:47:40 Felix-PC kernel: ath12k_pci 0000:05:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1b0 returns -95
Oct 08 09:47:40 Felix-PC kernel: ath12k_pci 0000:05:00.0: PM: failed to suspend async: error -95
Oct 08 09:47:40 Felix-PC kernel: PM: Some devices failed to suspend, or early wake event detected
Oct 08 09:47:40 Felix-PC kernel: PM: suspend exit
Oct 08 09:47:40 Felix-PC kernel: PM: suspend entry (s2idle)
Oct 08 09:47:45 Felix-PC kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Oct 08 09:47:45 Felix-PC kernel: ath12k_pci 0000:05:00.0: failed to suspend core: -95
Oct 08 09:47:45 Felix-PC kernel: ath12k_pci 0000:05:00.0: PM: pci_pm_suspend(): ath12k_pci_pm_suspend+0x0/0x60 [ath12k] returns -95
Oct 08 09:47:45 Felix-PC kernel: ath12k_pci 0000:05:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x1b0 returns -95
Oct 08 09:47:45 Felix-PC kernel: ath12k_pci 0000:05:00.0: PM: failed to suspend async: error -95
Oct 08 09:47:45 Felix-PC kernel: PM: Some devices failed to suspend, or early wake event detected
Oct 08 09:47:45 Felix-PC kernel: PM: suspend exit
░░ Subject: System sleep state suspend left
░░ The system has now left the suspend sleep state.
Oct 08 09:47:56 Felix-PC systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit systemd-suspend.service has exited.
Oct 08 09:47:56 Felix-PC systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
░░ The unit systemd-suspend.service has entered the 'failed' state with result 'exit-code'.
░░ Subject: A start job for unit systemd-suspend.service has failed
░░ A start job for unit systemd-suspend.service has finished with a failure.
░░ Subject: A start job for unit suspend.target has failed
░░ A start job for unit suspend.target has finished with a failure.
Oct 08 09:47:56 Felix-PC systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
Oct 08 09:47:56 Felix-PC systemd[1]: systemd-suspend.service: Consumed 10.490s CPU time.
░░ The unit systemd-suspend.service completed and consumed the indicated resources.
Oct 08 09:47:56 Felix-PC suspend[8165]: nvidia-resume.service
Oct 08 09:47:56 Felix-PC logger[8165]: <13>Oct 8 09:47:56 suspend: nvidia-resume.service
Well, in this Case ... you could install a newer Kernel on Zorin. With the Mainline Tool for Example. Or ... If I remember right, POP OS! uses a 6.9 Kernel. So, You could try that OS.
Well switching OS is not a solution for me. I don't use my WiFi card, I just want to disable it to get rid of this error and be able to suspend again. I disabled WLAN options in my BIOS but it's still appear in the OS...
Do you have disabled it in Zorin, too?
I'm looking for a way to do it in Zorin 
Do you have any idea?
Go to the Settings and there is a Switch:
It should be the first Menu Point in the Settings. Alternatively, You could go in the Quick Settings and turn off the Toggle there.
I found the issue. My WiFi card includes Bluetooth. Wifi driver is not working, so there is no WLAN card detected in the WLAN section. But Bluetooth is working. I just had to disable bluetooth and now suspend is working.
Thanks for your help
Glad to hear that it works now.
The issue is not yet fixed. If he uses Bluetooth again i re-apears again.
The issue won't be fixed until ZorinOS updates the kernel to version 6.9 or later to support the missing drivers, which isn't expected to happen anytime soon. So, this is just a workaround. I'm happy with it.
