You are not logged in.
Hi,
It's the first time I've ever tried to use it: just waited for KDE 4.2 .
Situation as follows:
(1) PowerDevil is running, according to Service Manager
(2) Power Management (by default) looks alive: everything enabled, configured, etc.
(3) Shutdown dialog (Ctrl-Alt-Del) contains just three options: Logout, Turn Off Computer and Restart Computer
(4) In addition, Leave menu contains Suspend to RAM and Suspend to Disk.
Suspend menu entries have no effect on anything; looks like something needs turning on... Any ideas?
Last edited by Llama (2009-02-02 11:29:17)
Offline
I haven't tried to implement suspend on my laptop yet, but I'd be interested in that too.
I suppose suspend needs to be set up separately. Check these wiki entries for a start :
http://wiki.archlinux.org/index.php/Suspend_to_Disk
http://wiki.archlinux.org/index.php/Suspend_to_RAM
what goes up must come down
Offline
Does pm-suspend work if started from the cli? Normally there is nothing that needs to be configured (except adding the resum=/dev/sdX param to your grub config if you want to use suspend to disk. But working suspend depends on you hardware; with some graphic adapters or mainboards this just does not work.
Offline
i have the same issue here, but solved when add my user to "power" group.
Offline
Thanks, Cypher! After adding myself to power group it started to show signs of life. Still, I'm not happy. Both pm-suspend utility and Suspend to RAM button give me a black but lighted from underneath screen (after a good while). I've no idea what to do next; so far hard reset is the only option known to me . Suspend to Disk works pretty much the same (no turning off). I do have "resume" option in my /boot/grub/menu.lst:
kernel /boot/vmlinuz26 root=/dev/disk/by-label/Root vga=773 resume=/dev/disk/by-label/Swap ro
Probably I don't know how to use the available options. Any suggestions? I really want what used to be "hibernation", but it isn't in the options. I really need help ...
Offline
If you failed to add yourself to the power group in the first place you may want to go through this wiki page:
http://wiki.archlinux.org/index.php/Laptop
which points specifically to this:
http://wiki.archlinux.org/index.php/Pm-utils
That should see you right - it did me.
never trust a toad...
::Grateful ArchDonor::
::Grateful Wikipedia Donor::
Offline
Do you mean that the relevant KDE 4 GUIs are implemented over pm-utils?
Offline
Well, it worked a treat on my T41 with KDE 4.2
never trust a toad...
::Grateful ArchDonor::
::Grateful Wikipedia Donor::
Offline
Do you mean that the relevant KDE 4 GUIs are implemented over pm-utils?
I think they are. I started playing with suspend to ram (it worked) and suspend to disk (it didn't work - actually, my laptop suspended but didn't resume, it just booted normally) when I saw this thread. All I did then was to add my user to the power group (I don't think this was necessary anyways) and the resume entry to the boot menu and everything worked like a charm.
Offline
I've read the Wiki; it appears I did everything by the book.
User is added to the power group;
/boot/grub/menu.lst:
kernel /boot/vmlinuz26 root=/dev/disk/by-label/Root vga=773 resume=/dev/disk/by-label/Swap ro
/usr/libs/pm-utils/defaults:
##########################################################
# DO NOT EDIT THIS FILE! #
# #
# Add files in /etc/pm/config.d/ instead! #
##########################################################
# Default method to power down the system when hibernating.
# If commented out, the system will use the kernel default as a
# default value.
#
# Check /sys/power/disk for valid values. The default value
# will be surrounded by [square brackets].
# HIBERNATE_MODE="shutdown"
# Whether we need to post the video card when resuming from
# hibernate. You should not normally need to set this.
# In the future pm-utils will get this setting from HAL.
#
# Valid values are "no" and "yes"
# HIBERNATE_RESUME_POST_VIDEO="no"
# The default sleep/wake system to use. Valid values are:
# kernel The built-in kernel suspend/resume support.
# Use this if nothing else is supported on your system.
# uswsusp If your system has support for the userspace
# suspend programs (s2ram/s2disk/s2both), then use this.
# tuxonice If your system has support for tuxonice, use this.
#
# The system defaults to "kernel" if this is commented out.
# SLEEP_MODULE="kernel"
# These variables will be handled specially when we load files in
# /etc/pm/config.d.
# Multiple declarations of these environment variables will result in
# their contents being concatenated instead of being overwritten.
# If you need to unload any modules to suspend/resume, add them here.
# SUSPEND_MODULES=""
# If you want to keep hooks from running, add their names here.
# HOOK_BLACKLIST=""
# If you want to unconditionally add parameters to the commandline,
# add them here.
# ADD_PARAMETERS=""
# If you want to ignore commandline parameters, add them here.
# DROP_PARAMETERS=""
# If you need to synchronize the system clock across a suspend/resume or
# hibernate/thaw cycle, set this variable.
# NEED_CLOCK_SYNC="true"
There's nothing in /etc/pm/config.d;
But working suspend depends on you hardware; with some graphic adapters or mainboards this just does not work.
I experimented with hibernation several months ago (KDEmod 3). It worked, albeit without much grace; that's why I decided to wait till it gets sorted out under KDE 4. Now it's even worse ...
PS Doing # pm-hibernate I can tell that it is not writing the state to disk: no disk activity, just a curfew imposed on me after a while .
Any suggestions?
Last edited by Llama (2009-01-29 11:34:52)
Offline
Here;
Unfortunately, while after the correction
# hibernate
works, the KDE buttons (doesn't) work as before...
Last edited by Llama (2009-02-02 11:31:58)
Offline
Hey all,
I'm having a similar issue. I've been using this arch install for several months with LXDE and suspend works fine. However, today I decided to give KDE 4.2 a shot and ran into some trouble. All power management utilities appear to be running and I can successfully run pm-suspend from a terminal, but when selecting "suspend to RAM" from the "leave" menu or from the battery monitor panel applet, nothing happens.
So, the problem for me appears to be KDE 4.2 specific. I'm probably missing some piece of additional setup required. Anyone have any ideas?
Offline