Ubuntu – Suspend to Ram – Thinkpad X1 Carbon 2017, Ubuntu 17.04

17.04suspendthinkpad

Hy folks

I'm a long time MacOS user and i just switched to GNU/Linux. My X1 Carbon arrived one week ago. Config: i7-7600, 16GB, 512GB. I know how to use a Terminal, i also know some CLI commands. But as it is for now – i don't know much about Linux internals.

Ubuntu Gnome 17.04 is my Distro of choice. I did try a few other Distros (Ubuntu Unity, openSUSE w. KDE, Xubuntu, Linux Mint). I feel most comfortable with Ubuntu Gnome.

The installation went without problems and everything seems to work well. I have three partitions (/boot/efi, / and /home). WiFi, Keyboard and Keyboard-light, Bluetoth are working out of the box. Battery life is awesome, > 10 hours with browser, writing and some youtube.

The only problem is suspend to ram. It's not working. On my macs i always used to close the lid (monitor) when i was not using them. Power management on Macs is really stable. I could pick up my machine, open the lid and after a few seconds continue to work exactly where i stopped. I hope there is a way to configure my Thinkpad to behave this way. When i close the lid now, it suspends (screen turns black, keyboard light turns of, i get a blinking red little dot on Thinkpad logo on the front of Monitor). When i open the lid everything freezes. Screen stays black, keyboard is not working. I have to hard reset / power off the machine.

How do i fix this? Are there any X1 Carbon users here which get this working?

Thanks in advance, i appreciate any help.

Update, 21.04.2017

I got a suggestion to try a live usb Ubuntu 16.04 iso. I tried and resume on suspend works. Then i tried Ubuntu 17.04 and Ubuntu Gnome 17.04 – and here also resume on suspend works out of the box. When i boot normal, do some stuff, close the lid the system suspends (blinking light shows that). When i open the lid, system is frozen – screen is black and keyboard is unresponsive.

My config:

Thinkpad X1 Carbon 5th. Gen (2017)
- Kernel: 4.10.0-19-generic
- CPU: Intel i7-7600U @ 2.8GHz
- Memory: 2x8GB LPDDR3 SK Hynix
- BIOS: 1.16
- VGA: Intel HD 620 (using driver = i915)
- SSD: NVME Samsung SM961/PM961
- WiFi: Intel 8265/8275
- Audio: Intel (using driver = snd_hda_intel)

Any help would be appreciated.

Best Answer

Could be related to a new power safe feature. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184

So far I'm running ok with the suggested workaround that prevents deeper power safe states. I modified /etc/default/grub the line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=6000 " and then make it active with "sudo update-grub " Se also accepted answer here: EXT4-fs error after Ubuntu 17.04 upgrade

Related Solutions

Ubuntu – Ubuntu 15.04 Suspend doesn’t run `pm-suspend`

Update: Found a nicer solution using systemd with no external scripts. Create and enable the following service:

[Unit]
Description=Save brightness on suspend
DefaultDependencies=no
RequiresMountsFor=/var/lib/systemd/backlight
Before=sleep.target
StopWhenUnneeded=yes

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/lib/systemd/systemd-backlight save acpi_video0
ExecStop=/lib/systemd/systemd-backlight load acpi_video0
TimeoutSec=90s

[Install]
WantedBy=sleep.target

Ubuntu 16.04 Note: The target backlight device name should be prefixed with "backlight:" (e.g. backlight:acpi_video0).

Enable by executing: systemctl enable suspend-save-backlight.service (or whatever you call it). Note that acpi_video0 is the name of the backlight symlink in /sys/class/backlight which is used to control the display brightness, might vary on different systems.

The above uses systemd's systemd-backlight executable to save and load the brightness before suspend and after resume respectively (inspired from /lib/systemd/system/systemd-backlight@.service which saves/loads brightness on restart/boot).

Old Solution (links a systemd service to my pm-utils suspend hook)

Found the problem. According to this ArchWiki article:

systemd does not use pm-utils to put the machine to sleep when using systemctl suspend, systemctl hibernate or systemctl hybrid-sleep; pm-utils hooks, including any custom hooks, will not be run. However, systemd provides two similar mechanisms to run custom scripts on these events.

So the right way to do it with systemd (which is used by default in 15.04) is to create the following service files which execute my brightness control script in /etc/pm/sleep.d/ as follows:

/etc/systemd/system/root-suspend.service:

[Unit]
Description=Local system suspend actions
Before=sleep.target

[Service]
Type=simple
ExecStart=-/etc/pm/sleep.d/nvidiabl_brightness suspend

[Install]
WantedBy=sleep.target

/etc/systemd/system/root-resume.service:

[Unit]
Description=Local system resume actions
After=suspend.target

[Service]
Type=simple
ExecStart=-/etc/pm/sleep.d/nvidiabl_brightness resume

[Install]
WantedBy=suspend.target

Then run the following to enable these services:

systemctl enable root-suspend.service
systemctl enable root-resume.service

Refer to the linked article for more details.

Ubuntu – Suspended Ubuntu 17.04 , when “wake up” does full reboot

Lets first check your file system for errors.

To check the file system on your Ubuntu partition...

boot to the GRUB menu
choose Advanced Options
choose Recovery mode
choose Root access
at the # prompt, type sudo fsck -f /
repeat the fsck command if there were errors
type reboot

Best Answer

Related Solutions

Ubuntu – Ubuntu 15.04 Suspend doesn’t run `pm-suspend`

Ubuntu – Suspended Ubuntu 17.04 , when “wake up” does full reboot

Related Question