Where did you find that at bud?

@wintermute42 @spinachbb

The original author on Arch Linux Wiki probably got the wrong impression from this thread. In fact the original thread author @Aaron0 explicitly pointed out that:

> 1, acpi.ec_no_wakeup=1 is a S2idle feature, not for S3. S3 is not supported on Lenovo official BIOS.

> 2, patching DSDT to enable S3 power consumption is not tested, so I don't have the answer.

And I think S3 will cause some wakeup issues on some devices.

> S2idle with acpi.ec_no_wakeup=1 already got low power consumption, Intel committed that S2idle will consume as much power as S3 with less wakeup time and less resume/wakeup issues.

> For now it should a little more than S3 and acceptable.

on page 7.

If I understand what you are saying and based on the most recent edits to the Arch wiki https://wiki.archlinux.org/index.php/Lenovo_ThinkPad_X1_Carbon_(Gen_6), I think there’s even more confusion. “S2idle” isn’t really a power state. That actually means “suspend to idle” (i.e. “to” was abbreviated as “2”). 

See the docs at https://www.kernel.org/doc/Documentation/power/states.txt where s2idle is related to ACPI S0 states. 

To achieve S0i3, all devices need to support low power mode or they need to be disabled before sleep (e.g. related kernel modules removed). Using powertop, you can tune the power settings for many devices. The important thing to notice is how much time is spent in Package C state 10 (pc10) during sleep which is the lowest power state and a prerequisite for S0i3. 

HAHAH! Look what I just found in the BIOS - a reference the s3 sleep method they stripped functionality for, under security > internal device access > internal storage tamper detection. This is on a 3rd gen thinkpad x1 yoga. 

I wonder what on earth was happening on the engineering teams when they decided to cripple their machines by removing s3 - clearly they weren't even communicating it across everyone. 

:smileyvery-happy: Lenovo, what were you thinking???

Seconding the `S2idle with acpi.ec_no_wakeup=1 ` process, on "sleep" it got me to "5.9 days" to empty, predicted by `upower --monitor-detail`

To do it, in ubuntu or debian, press the windows key and type "terminal," press enter. (Open terminal)

do

sudo gedit /etc/default/grub

Enter your password when prompted. 

You will see a text editor with some text that starts like 

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

If you don't, stop the guide here and go learn more about linux or post a question on stackoverflow or something, that's what I had to do very recently :P 

You will see a line like "GRUB_CMDLINE_LINUX_DEFAULT"

It probably looks like this right now: 

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

GEDIT works like any normal text editor (notepad), so click in there and change it to look like

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi.ec_no_wakeup=1"

Press ctrl+s to save (or click save in the top right), then close GEDIT. 

In your terminal, type

sudo update-grub

Then, restart your machine. 

To test if it works, try doing

upower --monitor-detail

in your terminal, and letting it run in a dedicated terminal window for a while as you browse the internet or something WITH YOUR LAPTOP UNPLUGGED. 

Then, with your laptop unplugged and leaving that terminal window open, try closing the lid of your laptop and going for a walk, 5, ten minutes. 

Open the lid, get your machine on again (I have to press the power button now), login, and compare the "time to empty" or the "energy-rate" of the recent logs to the previous ones (when you were using the machine). Hopefully, you see a significantly decreased difference. 

Either way, join me in regularly pestering Lenovo on social media to fix the thing they broke for no reason. 

Here it is

Do you know if this has rolled out to mint yet?

I don't know. I had some bad experience with BIOS update. I haven't tried this one yet...

Please be careful when using the ubuntu firmware updater. There is no announcement from ubuntu about supporting x1 bios updates and this update software is quite new and probably not tested that well as the official update software.

A wrong bios update can still brick your ~2k €/$ device! Thus, I dont trust this ubuntu updater and wouldn't use it!

I would only consider the official ways to update your bios! In the case that something went wrong, it's the fault of lenovo and it would be a warrenty case. But if the ubuntu bios updater bricks your system, i quess that this is not covered by the warrenty and you probably have to pay a motherboard replacement by yourself. There is no otherway to repair a damaged bios! (please correct me if there is a recovery bios chip on the mobo)

You can check the official ways to update your bios on the lenovo support website. Moreover, there is a changelog available:

CHANGES IN THIS RELEASE
  Version 1.27

[Important updates]
- Update includes a security fix.

[New functions or enhancements]
- Support TPM firmware update by utility.

[Problem fixes]
  Nothing.

  As you can see bios 1.27 only has security updates, probably for the new spectre kind attacks. So nothing related to this issue here!

Agree. Better to wait for official announcement of Linux tools