I was running KDE Neon on ThinkBook 15 G2 and had deep sleep working after adding mem_sleep_default=deep to GRUB_CMDLINE. It worked for a while until it didn’t. I didn’t do anything other than running regulat updates. Since couple weeks back, when going to sleep, it shows BIOS Recovery progress bar or something and restarts.
I switched to Debian and the behavior is the same. S2 sleep is next to useless as it drains something like 10% battery / hour, and the lap top is warm to touch.
Yeah, my sleep schedule is pretty bad since the holiday… Oh, Oooooh.
I was up until 2am last night because the air felt “wrong”
This talk introduces sleepgraph, a tool that might help you debug your s2ram issues.
The talk may also convince you that, for your specific hardware, s2idle might be better than s2ram:
running sleepgraph crashes the computer same way deep sleep does 😖
You still had deep sleep until now? Lucky you. To me Dell forbided S3 way earlier.
So… Bios update broke deep sleep, because fuck you, that’s why?
For everyone I think
Is deep sleep the same thing as hibernation? Hibernation is broken for me even on new EndeavourOS install on two different laptops.
No, hibernation saves state to disk, and turns the computer off, drawing no power. Deep sleep is what was for me just sleep until recently: it uses power to keep data in ram, so it’s faster to wake up than hibernation. The amount of power used is really small, so unless you don’t use your lap top for a couple of days, it won’t deplete the battery. New hardware has this new “S2 Idle” state, that is basically an “On” state minus the screen and it’s OS’s job to try to use as little power as possible usually by telling each and every device to chill as much as possible (this is my understanding, but don’t quote me on this). On Windows, with the first party device drivers, this sorta works OK + OS drops to deep sleep or hibernation depending on battery or something.
specs?
It’s 2021 Lenovo ThinkBoot 15 G2 Intl with Intel i3-1115G4, 8GB onboard ram, integrated GPU and two NVME slots.
Here are some lines from dmidecode if they mean anything to anyone:
Getting SMBIOS data from sysfs. SMBIOS 3.3.0 present. Handle 0x0000, DMI type 0, 26 bytes BIOS Information Vendor: LENOVO Version: F8CN42WW(V2.05) Release Date: 06/28/2021 Address: 0xE0000 Runtime Size: 128 kB ROM Size: 16 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 2.42 Firmware Revision: 2.42 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: LENOVO Product Name: 20VE Version: ThinkBook 15 G2 ITL SKU Number: LENOVO_MT_20VE_BU_idea_FM_ThinkBook 15 G2 ITL Family: ThinkBook 15 G2 ITL Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: LENOVO Product Name: LNVNB161216 Version: SDK0J40700 WINso cat /sys/power/mem_sleep or whatever outputs with the brackets on deep?
Yeah, if the bracket is on deep, it crashes and enter the BIOS recovery thingy. If it’s s2idle, it does what it says on the tin.
have you updated EFI/BIOS recently? maybe S3 sleep is not supported on your system anymore and instead you get suspend-to-idle as S0ix (Modern Standby) notoriously shitty under linux. sometimes you can flip it back in EFI/BIOS
I have a Windows dual boot, and Windows did install some updates, and Lenovo site indicates that the latest BIOS version was released mid November, so that could be it.
