Comment 158 for bug 1958019

(In reply to DavidLenovo from comment #144)
> (In reply to Vincent Morel from comment #141)
> > Thanks for all those precious infos! Just to make things more complicated,
> > PopOs use systemd-boot and not grub.
> > Anyway I was able to activate 'deep' sleep with this command:
> >
> > sudo kernelstub -a "mem_sleep_default=deep"
> >
> > and after reboot I have:
> > cat /sys/power/mem_sleep
> > s2idle [deep]
> >
> >
> > But my computer is not able to exit from sleep now. It goes into deep sleep
> > (I see the led in sleeping mode) but as soon as I press a key the computer
> > turn off. I have to turn it on and it boots...
> >
> > I also try to do it by adding mem_sleep_default=deep in
> > /boot/efi/loader/entries/pop_OS-current.conf (that's where you put option
> in
> > systemd-boot)
> >
> > Same result... I'll try a totally different distribution when I have time
> > (not ubuntu based) to see if I can do it.
>
> (In reply to wave from comment #142)
>
> > Did you have to patch the DSDT table in order to get S3 sleep and if yes
> did
> > the patch apply cleanly?
> >
> > Does the problem also occur if you do
> > systemctl hibernate
> > explicitly?
>
> Your sure your have to hibernate ?
> For me in S2 or S3 hibernate (suspend to disk) is the same.
> But sleeping : suspend to ram, is not the same in S2 and S3.
>
> For me I boot, and I make a sleep (suspend to ram) to enable speaker and
> brightness hotkeys.
>
> Your tutorial (Wave) have a script with : rtcwake -m mem -s 1 that it is :
> suspend to memory.
>
> @Vincent Morel : could you try sleep (suspend to ram) (not to disk) ?

You're right, my bad, sorry. Hibernating takes too much time to wake up, I think that's the reason why it doesn't activate sound (my brightness keys do work after suspend to disk/hibernate). Should do
systemctl suspend
instead, this should trigger S3 sleep.