On Monday, January 6, 2020 at 12:43:40 AM UTC-3, Claudia wrote: > > January 6, 2020 3:14 AM, [email protected] <javascript:> wrote: > > > On Sunday, January 5, 2020 at 9:49:42 PM UTC-5, Guerlan wrote: > >> can you tell me how you figured this out? I've been trying to fix a > suspend bug in mine and It'd be > >> helpful to know how you debugged things > > > > Mostly trial and error, trying all the things listed above. Two little > tricks to use: > > > > 1. Look at the end of journalctl right before it tries to suspend. This > is where I saw that it was > > going into s2idle, which then brought me to this thread: > > > https://groups.google.com/forum/#!msg/qubes-users/TmGDlkluJgM/1BFsQZWNDAAJ;context-place=forum/qubes > > users This Dell did not have the lack of S3 that the new Thinkpads have, > but it did still try to > > use s2idle. > > /sys/power/mem_sleep will list supported modes, with the default in > brackets. You can echo to it to set the default at runtime, or use the boot > parameter. >
[lz@dom0 ~]$ cat /sys/power/mem_sleep s2idle [deep] What does this mean? It means that it *detected* only s2idle or that my system does not support suspend to RAM? I've used Ubuntu and Fedora and lid closing always worked, I just don't know if it was idle or to ram or other thing. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/bc364066-1824-413d-afd1-e3c148ad7a53%40googlegroups.com.
