I installed Ubuntu 21.04 today. According to mem_sleep mine is defaulting to deep. Verified I don’t have the setting in the /etc/default/grub. Not sure why I am seeing a different behavior. Probably worth checking step 4a before doing the rest.
Updating with my findings: after disabling deep and letting it go back to s2idle, I no longer have issues with resume.
Unfortunately the battery drain issue is back when disabling [deep]. It sounds like I’ll just have to keep it plugged in while asleep until this bug is fixed.
Right, I got it backwards, and people were polite and helpful in correcting me. For the uninitiated, it’s not obvious how to interpret that string. Here’s how I understand it now:
example of deep sleep disabled:
[jeremy@fwfedora ~]$ cat /sys/power/mem_sleep
[s2idle] deep
[jeremy@fwfedora ~]$
Kubuntu 21.04 kernel 5.11.0-25 Wifi and Bluetooth worked out of the box. Although I was able to install libfprint and fprintd from source and register my fingerprint with fprintd-enroll, I could not get fingerprint auth to work for login. (I think this has something to do with lack of fingerprint auth support with KDE plasma?)
I’m also using Windows 10 as a guest OS in a VMWare virtual machine that’s working well so far.
@tombo@nebkor On Mint xfce 20.2 I’ve noticed something a little odd about waking from suspend, that almost all of the time when I drag my finger across the touchpad while it is awakening there is some sort of random issue with it when it is awake (all the way from non-responsive to responsive but not registering multi-touch to wrong speed), but when I leave it untouched it comes back on with a normally functioning touchpad (hopefully this does not jinx it…). Maybe there is something about receiving input while coming back online that confuses it?
@ezhik So got my hands on the drive and actually it’s a 1TB Rocket 4 Plus.
Did a clean install of 21.04, left everything at the default except LVM w/ encryption (including free space). Updated, rebooted, enabled deep sleep, rebooted, and put to sleep.
I did a few tests of 5-15 minutes each and it resumed with no obvious issues. Checking journalctl shows no “read-only” errors. Does it matter how long it is asleep for you?