[SOLVED] Slackware64 13.37 suspend sort of works.

blue_k · 04-26-2011, 06:27 AM

EDIT:
I am now using 13.37. Look at my post below.

Hi,

I am using Slackware64 13.1 and every time I try to suspend my computer it looks like it "goes through the motions," but then it just goes back to the session lock screen. Here is the pm-suspend.log file.

Code:

Initial commandline parameters: 
Sat Apr 23 10:14:42 EDT 2011: Running hooks for suspend.
/usr/lib64/pm-utils/sleep.d/00logging suspend suspend:Linux Phoenix_Slack 2.6.33.4 #2 SMP Tue Sep 21 17:28:38 CDT 2010 x86_64 Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz GenuineIntel GNU/Linux
Module                  Size  Used by
snd_seq_dummy           1487  0 
snd_seq_oss            29884  0 
snd_seq_midi_event      5620  1 snd_seq_oss
snd_seq                52643  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
rfcomm                 36491  8 
snd_pcm_oss            39907  0 
snd_mixer_oss          15975  1 snd_pcm_oss
ipv6                  273462  16 
sco                     8635  2 
bridge                 49287  0 
stp                     1600  1 bridge
llc                     3801  2 bridge,stp
bnep                   10967  2 
l2cap                  33695  16 rfcomm,bnep
pcmcia                 30280  0 
pcmcia_core            29487  1 pcmcia
lp                     10049  0 
ppdev                   6315  0 
parport_pc             21015  0 
parport                29923  3 lp,ppdev,parport_pc
btusb                  11402  2 
bluetooth              49470  9 rfcomm,sco,bnep,l2cap,btusb
rfkill                 15860  3 bluetooth
usbhid                 37516  0 
hid                    75699  1 usbhid
fuse                   59927  3 
nvidia              10078982  38 
processor              29915  4 
snd_emu10k1           138990  2 
snd_rawmidi            19201  1 snd_emu10k1
snd_ac97_codec        113239  1 snd_emu10k1
ac97_bus                1230  1 snd_ac97_codec
snd_pcm                71871  3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec
snd_seq_device          5459  5 snd_seq_dummy,snd_seq_oss,snd_seq,snd_emu10k1,snd_rawmidi
snd_timer              19466  3 snd_seq,snd_emu10k1,snd_pcm
snd_page_alloc          7145  2 snd_emu10k1,snd_pcm
snd_util_mem            2384  1 snd_emu10k1
snd_hwdep               6420  1 snd_emu10k1
snd                    57142  15 snd_seq_oss,snd_seq,snd_pcm_oss,snd_mixer_oss,snd_emu10k1,snd_rawmidi,snd_ac97_codec,snd_pcm,snd_seq_device,snd_timer,snd_hwdep
thermal                12550  0 
rtc_cmos                9278  0 
agpgart                29705  1 nvidia
thermal_sys            14118  2 processor,thermal
soundcore               5839  1 snd
ohci1394               28585  0 
ehci_hcd               36824  0 
i2c_i801                8598  0 
ieee1394               74340  1 ohci1394
rtc_core               14766  1 rtc_cmos
button                  4922  0 
xhci                   43458  0 
i2c_core               18679  2 nvidia,i2c_i801
psmouse                47158  0 
wmi                     6275  0 
serio_raw               4654  0 
rtc_lib                 1922  1 rtc_core
hwmon                   1449  1 thermal_sys
sg                     25890  0 
e1000e                150522  0 
emu10k1_gp              1812  0 
evdev                   9114  14 
gameport                8424  2 emu10k1_gp
ext4                  330381  3 
mbcache                 5770  1 ext4
jbd2                   71201  1 ext4
             total       used       free     shared    buffers     cached
Mem:       3067856    1449192    1618664          0      49816     949828
-/+ buffers/cache:     449548    2618308
Swap:      6291448          0    6291448
success.
/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:not applicable.
/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:not applicable.
/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.
Sat Apr 23 10:14:42 EDT 2011: performing suspend
/usr/lib64/pm-utils/pm-functions: line 295: echo: write error: No such file or directory
Sat Apr 23 10:14:43 EDT 2011: Awake.
Sat Apr 23 10:14:43 EDT 2011: Running hooks for resume
/usr/lib64/pm-utils/sleep.d/99video resume suspend:success.
/usr/lib64/pm-utils/sleep.d/98video-quirk-db-handler resume suspend:success.
/usr/lib64/pm-utils/sleep.d/95led resume suspend:not applicable.
/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:not applicable.
/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.
Sat Apr 23 10:14:43 EDT 2011: Finished.

My computer specs are:

Motherboard: Asus P8P67 Pro
CPU: Intel 2500K
Sound Card: Creative Sound Blaster Audigy 2 ZS Gamer
GPU: EVGA Nvidia GTX 470
GPU Driver: Proprietary Nvidia drivers
Kernel: Generic kernel included on the Slackware64 13.1 install DVD

My computer is also not overclocked.

Any help would be greatly appreciated.

Alien Bob · 04-26-2011, 09:09 AM

It looks like you are running a custom kernel you compiled yourself?
The line where the error occurs has this command:

Quote:

echo -n "mem" >/sys/power/state

.
The "write error: No such file or directory" may indicate that you compiled a kernel without

Quote:

CONFIG_HOTPLUG_CPU=y

Eric

blue_k · 04-26-2011, 10:03 PM

Alien Bob, this is the generic kernel included on the Slackware64 13.1 install DVD. This is not a custom kernel.

blue_k · 04-28-2011, 05:40 AM

I have just updated to 13.37, and now when I try to suspend using the "Sleep" button through KDE's menu, it looks like it "goes through the motions," but then it returns to the session lock screen. If I try to use pm-suspend as root through a terminal however it will successfully sleep. How can I make it sleep using the button through KDE? I have tried adding myself to the power group, but this does not help.

Alien Bob · 04-28-2011, 06:40 AM

Please explain why the post should be deleted.
You also removed all your original text in the first post instead of adding a new post at the bottom... bad practice and not nice to people who want to help.

Eric

blue_k · 04-28-2011, 06:43 AM

I have reverted back to how it was. Thank you for letting me know that this is not how it should be done. I will remember that from now on.

blue_k · 04-28-2011, 10:58 AM

I just installed 13.37 on my Eee PC 1000, and it also has the same issue of pm-suspend as root works, but the "Sleep" button in KDE does not.

x-alien · 04-28-2011, 11:03 AM

Quote:

Originally Posted by blue_k

I just installed 13.37 on my Eee PC 1000, and it also has the same issue of pm-suspend as root works, but the "Sleep" button in KDE does not.

Try to add your user to the "power" group.

blue_k · 04-28-2011, 11:45 AM

Quote:

Originally Posted by x-alien

Try to add your user to the "power" group.

I just tried that, but it did not work. The sleep button still only locks the screen. Also, shutting the lid only locks the screen even though I have told it to suspend if I close the lid.

hyperhead · 04-28-2011, 11:54 AM

I upgraded to 64bit 13.1 then went to 13.37, I decided to get hibernate to work as I was turning my laptop off for longer periods (shame) and suspend drained the battery. I fixed it, I kept notes, they are here:

http://techbutlers.co.uk/?p=315

They might help,

One thing I missed in the notes was to add the location of the swap partition to lilo.conf:

Code:

append="resume=/dev/sda5"

(location of swap partition)

Remembering to run lilo afterwards

blue_k · 04-28-2011, 12:13 PM

Thank you for your post, but I am looking to suspend to ram not to disk. Does anyone else have another idea?

blue_k · 04-28-2011, 01:01 PM

I have solved the problem. It turns out I had to reboot the system after adding myself to the power group instead of just logging out and back in. Thank you all for your help.