You are not logged in.
Pages: 1
I'm using a HP Pavilion g6, here's what lshw has to say, and my screen doesn't turn on after resume from "sudo systemctl suspend". I can flick over to another TTY and (blindly) log in and execute commands, but my screen won't turn back on. (Edit - something similar happens for "systemctl hibernate" - except this time, the screen just turns off and it never powers down).
I know that pm-suspend has "sleep quirks" for this (though I never figured out what mine were), but what can I do to remedy this in systemctl?
Last edited by Score_Under (2013-07-27 18:34:08)
Offline
You could try an older kernel as the latest ones seem to give problems.
I have just downgraded the kernel on my desktop for the reason that you have and all is OK.
Offline
What version of the kernel did you downgrade to?
Offline
Kernel 3.9.7-1 at the moment as the last 2 or 3 wouldn't resume.
Offline
I imagine if you figured out what pm-suspend did, you could get systemd to do that by crafting a suitable unit file and having the relevant systemd target "want" it.
You should be able to figure out what pm-suspend did from the logs/journal, I think.
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Even easier than using native units to enable sleep quirks (once you figure out what they are) would be to simply port the scripts provided by pm-utils/pm-quirks to the systemd-sleep format.
Offline
Pages: 1