14

On a freshly installed and updated Ubuntu 14.04 my ThinkPad E540 suspends successfully, but won't wake back up - a full reboot is necessary. Moreover, during the suspended state the fan is constantly working on considerably higher rpm than during normal usage, even though laptop's LED indicates sleep. However, it seems that both hardware and BIOS are OK, since suspend works fine on Windows 7.

I tried out solutions offered on similar problems, most notably this (use Nvidia proprietary drivers instead of noveau) and this, yet the problem persists.

pm-suspend.log reports everything was completed with success, except this: 

Failed to connect to non-global ctrl_ifname: (null)  error: No such file or directory

This message is repeated thrice. The log ends with 'performing suspend'.

I really appreciate help with this matter.

EDIT: This procedure also didn't help.

Community
  • 1
mrvlad
  • 153

6 Answers6

10

I have this model and had this issue.

As far as I know, it isn't solved yet, but suspend/wake works as expected if you disable USB 3.0 in the BIOS.

See the bug page at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1340376.

The ports still work as USB 2.0 ports. Haven't thought about the issue in two months.

Josiah Stevenson
  • 101
5

As user Josiah Stevenson said, the problem really references USB 3 option in BIOS.

Happy to inform you, that the latest BIOS update v.2.20 fully solves this problem. You can download the update from Lenovo Downloads, flash your BIOS and use both USB 3.0 and suspend in Ubuntu.

SilverFire
  • 186
1

I am using a completely different laptop (dell inspiron 1420), but had a similar problem with 14.04. With a timeout suspend (2 hours), upon resuming, keyboard and trackpad do not work. Cannot switch to a terminal.

Workaround seems to be to manually (as suggested above) use the menu to suspend rather than a timeout (or lid closing). After a manual suspend, I wait until the hdd indicator is off and the power indicator is pulsing. I then can close the lid. Upon opening it, keyboard and trackpad work. I have tested this 5 times now.

I also have the password required from suspend option set.

I also have the same Fail statement in my pm-suspend.log. I have the fail statement whether or not I have a successful resume. For that reason, I don't think it is reflective of what is going on.

Mark D
  • 473
1

I tried many things. After finding out that hibernate works but suspend does not I changed the settings in /etc/default/acpi-support commenting out ACPI_SLEEP=true Reboot. That did the trick for me. No suspend to RAM.

αғsнιη
  • 36,350
Vinz
  • 11
0

TL;DR: you may be able to use a terminal to avoid a full reboot, but I've yet to find a real solution. For me, his only began occurring in the past week, post a round of updates.

I'm the Thinkpad S1 Yoga. Suspending from the menu is fine to resume, but suspends from closing the lid fail to resume. I can see the screen in the state it was in at suspend time, and (sometimes) move my mouse, but no keyboard input is allowed to Unity.

Ctrl-Alt-F# (F1,F2,F3,F4,F5,F6, and F7. F8 Goes to GUI interface) takes me to a terminal where I can pkill myself and re-log in, so it seems to be a problem, for me, in the X/Unity world.

I have integrated Intel graphics, so all the NVidia and AMD solutions aren't helping me :)

UPDATE: Switching to requiring a password after resuming from suspend has provided a good workaround for me that doesn't require pkill.

user3669669
  • 38
joncam
  • 179
0

I have the same problem with a Lenovo Thinkpad E540, after some research the solution that I found was the following:

1) Remove the BIOS Battery, this can be easily done without mayor tools, it only takes a small Phillips screwdriver since the BIOS battery is located under a small rectangular cap in the back of the laptop.

2) Wait around 10 seconds and reconnect the BIOS battery (this will reboot the BIOS entirely).

This procedure will make the laptop turn on normally but it will require to set up the BIOS date and any other personal configurations.

In the topic of how to solve this issue, there is a temporary solution and a possible final solution that I am still testing:

1) Like user Josiah Stevenson said, disable the USB 3.0 in the BIOS, this worked for me for around 3 months but then the problem appeared again.

2) Do an Upgrade of the BIOS; like a said before I'm still testing if this solves the problem permanently, so far it has only been a couple of days so I can't say if this procedure will solve the issue.

ubudebuserccs
  • 51