Hi. I did the suggested echo and, if I clearly understood, switched to s2idle mode without deep-mode.
For tests I use 4.19.28 on Debian-like system (Parrot OS).
If the system defaults to use S2I, then itâs better to stick with it.
Lots of ODM/OEM donât really test S3.
So S3 is the same as S2 but with deep mode enabled?
The default switches to s2idle based on FADT flag and _DSM on relative new kernels.
Are those some SSDT flags?
It actually sounds weird to me, why restarting touchpad after deep suspend affects it work. I mean, if it starts sucessfully at boot, why it doesn't after suspend? Can we debug it somehow?
Regards,
Vladislav.
Apr 23, 2019, 12:47 PM by kai.heng.feng@xxxxxxxxxxxxx:
at 17:40, <hotwater438@xxxxxxxxxxxx> <hotwater438@xxxxxxxxxxxx> wrote:
Hi. Thank's for a hint!
So catting this file gives me next content:
s2idle [deep]
Which kernel version do you use?
Most systems preload with Windows 8.1 should default to use s2idle.
So I suppose I have s2idle with deep-mode available?
I've tried to select deep by creating mem_sleep_default file, but I can't (Permission error).
Could you explain how do I switch suspend mode in Linux, if you know?
# echo s2idle > /sys/power/mem_sleep
And to be honest, I don't think that's a correct fix of touchpad problem.
Can we somehow cut off the power by hands or send a signal to a system to shut off a touchpad? Or there are no approaches like that?
I donât think itâs possible.
Kai-Heng
Regards,
Vladislav.
Apr 23, 2019, 12:08 PM by mika.westerberg@xxxxxxxxxxxxxxx:
On Tue, Apr 23, 2019 at 11:00:48AM +0200, hotwater438@xxxxxxxxxxxx wrote:
Hi.
Honestly, I can't find any information about my acpi suspend type.
There are no options in my BIOS to change it, and I can't determine
which exactly I have. But I suppose I have a S3 because I have suspend
issue.
Can I somehow determine it in Linux? I did a research but found nothing
on the internet.
You can read the default mode from /sys/power/mem_sleep. "s2idle" means,
well suspend-to-idle and "deep" means S3.