https://forums.lenovo.com/t5/Linux-Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-Suspend-to/m-p/4163130/highlight/true#M11492 reports s2idle consuming 2.5x more power than S3 on this laptop. That's _after_ manual effort (powertop tuning and of course dealing with Thunderbolt). There are many similar reports. This is why (e.g.) Arch Linux recommends using https://github.com/fiji-flo/x1carbon2018s3 to override DSDT on this laptop, with s2idle only as a secondary option. For people using Linux inside Qubes, s2idle doesn't wake up at all on this laptop, and the only workaround people have found is S3. I think it's fair to describe this as s2idle not working. Outside the Xen context I'd almost agree with "s2idle works but it consumes more power" as a description, except that I'd say "much more power". > It does not say "work around BIOS bug" but instead that Windows treats > the two exclusively and I suppose they prefer Modern Standby over S3. Microsoft claims that Windows will choose Modern Standby over S3 when the BIOS announces both: https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/modern-standby-faqs But Lenovo says "When ACPI table was changed to support S3, Windows Modern Standby doesn't work". I don't see how this can be reconciled with the documentation. Lenovo is saying that there's a Windows bug, so, as a workaround, Lenovo's BIOS provides wrong information (namely that the laptop doesn't support S3). This patch fixes the wrong information. ---Dan
Attachment:
signature.asc
Description: PGP signature
