LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Laptop and Netbook (http://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/)
-   -   Getting Lenovo W510 to go to Sleep/Suspend to RAM (http://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/getting-lenovo-w510-to-go-to-sleep-suspend-to-ram-812694/)

dimm0k 06-07-2010 12:14 PM

Getting Lenovo W510 to go to Sleep/Suspend to RAM
 
I have a new install of Slackware 13.1 on a Lenovo W510 notebook and am having trouble getting this machine to Sleep. If I use the Sleep option in KDE the system goes through the motions, but never actually suspends to RAM. The only thing that happens is the screen blanks, not even going into powersave mode. Hardware wise everything should be sound because it works fine in Windows 7.

The following is what is logged to pm-suspend.log

/usr/lib64/pm-utils/sleep.d/00powersave suspend suspend:success.
/usr/lib64/pm-utils/sleep.d/01grub suspend suspend:not applicable.
/usr/lib64/pm-utils/sleep.d/49bluetooth suspend suspend:success.
/usr/lib64/pm-utils/sleep.d/55NetworkManager suspend suspend:success.
/usr/lib64/pm-utils/sleep.d/75modules suspend suspend:not applicable.
/usr/lib64/pm-utils/sleep.d/90clock suspend suspend:not applicable.
/usr/lib64/pm-utils/sleep.d/94cpufreq suspend suspend:success.
/usr/lib64/pm-utils/sleep.d/95led suspend suspend:success.
/usr/lib64/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:success.
/usr/lib64/pm-utils/sleep.d/99video suspend suspend:kernel.acpi_video_flags = 0
success.
Fri Jun 4 20:33:31 EDT 2010: performing suspend
/usr/lib64/pm-utils/pm-functions: line 295: echo: write error: No such file or directory
Fri Jun 4 20:33:33 EDT 2010: Awake.
Fri Jun 4 20:33:33 EDT 2010: Running hooks for resume
/usr/lib64/pm-utils/sleep.d/99video resume suspend:Couldn't get a file descriptor referring to the console
Couldn't get a file descriptor referring to the console
Returned exit code 1.
/usr/lib64/pm-utils/sleep.d/98video-quirk-db-handler resume suspend:success.
/usr/lib64/pm-utils/sleep.d/95led resume suspend:success.
/usr/lib64/pm-utils/sleep.d/94cpufreq resume suspend:success.
/usr/lib64/pm-utils/sleep.d/90clock resume suspend:not applicable.
/usr/lib64/pm-utils/sleep.d/75modules resume suspend:success.
/usr/lib64/pm-utils/sleep.d/55NetworkManager resume suspend:success.
/usr/lib64/pm-utils/sleep.d/49bluetooth resume suspend:success.
/usr/lib64/pm-utils/sleep.d/01grub resume suspend:not applicable.
/usr/lib64/pm-utils/sleep.d/00powersave resume suspend:success.
/usr/lib64/pm-utils/sleep.d/00logging resume suspend:success.


Running 'echo mem > /sys/power/state' and 'echo disk > /sys/power/state' while in KDE looks like it actually goes through the motions of going into Sleep or Hibernate, but then it wakes up by itself with the following message:
-su: echo: write error: Input/output error

zordrak 06-08-2010 07:28 AM

First question is, is the user your running KDE as in the "power" group? If not then add it and reboot.

dimm0k 06-08-2010 01:20 PM

Thanks for the reply zordrak! To answer your question, yes, it is part of the power group. Because the hardware works properly under Windows and because users of this notebook don't seem to be having this issue, I decided to boot off of a KUbuntu live CD to see if I would have the same success. Seems like Ubuntu users other than myself have this particular notebook. Anyway it worked fine under KUbuntu after creating /etc/pm/config.d/unload_module and adding the SUSPEND_MODULES="xhci" line. I had done the same under Slackware and found it really odd that lsmod did NOT show, while it did in KUbuntu. That's when it hit me, I was using the "huge" kernel and xhci most likely was built into the kernel rather than as a module! While I have not yet switched over to the generic kernel, I'm completely certain doing so or compiling my own kernel will fix this so I will close this post as SOLVED!


All times are GMT -5. The time now is 10:17 PM.