diff options
Diffstat (limited to 'source/ap/pm-utils/README.SLACKWARE')
| -rw-r--r-- | source/ap/pm-utils/README.SLACKWARE | 42 |
1 files changed, 24 insertions, 18 deletions
diff --git a/source/ap/pm-utils/README.SLACKWARE b/source/ap/pm-utils/README.SLACKWARE index 07162439..26ff48d8 100644 --- a/source/ap/pm-utils/README.SLACKWARE +++ b/source/ap/pm-utils/README.SLACKWARE @@ -1,5 +1,5 @@ README.SLACKWARE -20090414 - rworkman@slackware.com +20100319 - rworkman@slackware.com =============================================================================== PLEASE READ THIS ENTIRE FILE BEFORE REPORTING PROBLEMS OR ASKING FOR HELP! @@ -29,21 +29,21 @@ it works at all. Here's the short version of using suspend to disk: Stanza in /etc/lilo.conf should look something like this: - image = /boot/vmlinuz-generic-smp-2.6.29.1-smp + image = /boot/vmlinuz-generic-smp-2.6.33.1-smp initrd = /boot/initrd.gz - append = "resume=/dev/hda2" - root = /dev/hda1 - label = Slackware + append = "resume=/dev/sda2" + root = /dev/sda1 + label = genericsmp.s read-only /etc/mkinitrd.conf should look something like this: MODULE_LIST="jfs" - ROOTDEV="/dev/hda1" + ROOTDEV="/dev/sda1" ROOTFS="jfs" - RESUMEDEV="/dev/hda2" + RESUMEDEV="/dev/sda2" mkinitrd command invocation would be this: - mkinitrd -c -k 2.6.29.1-smp -F + mkinitrd -c -k 2.6.33.1-smp -F All of the above assumes at least a cursory understanding of what those commands and parameters do. If it's not clear, don't attempt it on a @@ -51,14 +51,17 @@ system that you can't easily reinstall without concern. ============================================================================== -If it works for you, and/or you want to automate it a bit, you'll find -some sample acpi event declarations and scripts here: - http://rlworkman.net/conf/acpi/ -A better option is to use the power manager daemon included with your choice -of desktop environment (both kde and xfce have one). +Once you confirm that a suspend and resume cycle works as expected, you might +automate the process with some acpi magic, but a better option is to use the +power manager daemon included with your choice of desktop environment (both +kde and xfce have one). ============================================================================== +/* TODO: these links are now dead. That's mostly okay, because the vast + majority of the hardware out there these days doesn't require any quirks + at all any more. Hopefully you won't be in the minority :-) */ + If it doesn't work by default for you, consider having a look at http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-index.html for some debugging hints. Pay particular attention to this page: @@ -76,14 +79,14 @@ needed to add for successful suspend/resume to rworkman@slackware.com If you need the system to do certain operations before going to sleep and then undo them (or perhaps do something new) when waking back up, pm-utils supports something called "hooks." The hooks installed by packages (not only -pm-utils itself) should be in /usr/lib/pm-utils/sleep.d/, while any hooks +pm-utils itself) should be in /usr/lib(64)/pm-utils/sleep.d/, while any hooks installed by the local system administrator (e.g. things that are only an issue on that one machine) should be in /etc/pm/sleep.d/. Looking at some of the existing hooks should give you a decent idea of their capabilities; as a head start, the functions used in the hooks are declared -in /usr/lib/pm-utils/functions, which is inherited elsewhere by -/usr/lib/pm-utils/pm-functions. Note that an error exit code on any hook +in /usr/lib(64)/pm-utils/functions, which is inherited elsewhere by +/usr/lib(64)/pm-utils/pm-functions. Note that an error exit code on any hook will cause the sleep operation to fail, so if you don't care whether your hook executes successfully, be sure to return an exit code of 0 (success) if you don't want the suspend operation to fail. Some other exit codes are @@ -101,15 +104,18 @@ ship its own hook. KNOWN ISSUES +/* TODO: remove? I've gotten *zero* mails about either of these since + we've been shipping pm-utils */ + **** If you encounter either of these, mail rworkman@slackware.com **** If your alsa drivers don't correctly save and restore state across a sleep / resume cycle (due to a buggy driver), then you will need to add the drivers to a custom file named /etc/pm/config.d/defaults (create the file if it does not exist already) in a variable named "SUSPEND_MODULES" - see the file at -/usr/lib/pm-utils/defaults for proper format. +/usr/lib(64)/pm-utils/defaults for proper format. -The /usr/lib/pm-utils/sleep.d/90clock does not run by default. It added +The /usr/lib(64)/pm-utils/sleep.d/90clock does not run by default. It added over a second to suspend, and the vast majority of hardware does not need it to keep the clocks in sync. If you need this hook, you can set the NEED_CLOCK_SYNC environment variable in a custom /etc/pm/config.d/defaults |