diff options
Diffstat (limited to 'source/ap/pm-utils/README.SLACKWARE')
| -rw-r--r-- | source/ap/pm-utils/README.SLACKWARE | 33 |
1 files changed, 12 insertions, 21 deletions
diff --git a/source/ap/pm-utils/README.SLACKWARE b/source/ap/pm-utils/README.SLACKWARE index 7f91f2282..1bbfbfe81 100644 --- a/source/ap/pm-utils/README.SLACKWARE +++ b/source/ap/pm-utils/README.SLACKWARE @@ -1,5 +1,5 @@ README.SLACKWARE -20101229 - rworkman@slackware.com +20130512 - rworkman@slackware.com =============================================================================== PLEASE READ THIS ENTIRE FILE BEFORE REPORTING PROBLEMS OR ASKING FOR HELP! @@ -29,7 +29,7 @@ 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.35.10-smp + image = /boot/vmlinuz-generic-smp-3.8.13-smp initrd = /boot/initrd.gz append = "resume=/dev/sda2" root = /dev/sda1 @@ -43,7 +43,7 @@ Stanza in /etc/lilo.conf should look something like this: RESUMEDEV="/dev/sda2" mkinitrd command invocation would be this: - mkinitrd -c -k 2.6.35.10-smp -F + mkinitrd -c -k 3.8.13-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 @@ -60,7 +60,11 @@ 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 :-) */ + at all any more. Hopefully you won't be in the minority :-) + Addendum: it's now been about three years since the above text was + written, and I've had zero reports of hardware requiring additional + quirks. Just FYI. :-) +*/ If it doesn't work by default for you, consider having a look at http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-index.html @@ -97,11 +101,10 @@ also available; none of these will cause the suspend to fail: The default powersave hooks are in /usr/lib(64)/pm-utils/power.d/ -- if you need to override any parameters set in those, you can do so with same-named -files in /etc/pm/power.d/ (populated with only the parameters you wish to -change). As an example, if you wanted to change the hdparm setting for -your hard drive's power management setting: rather than copying the entire -contents of /usr/lib(64)/pm-utils/power.d/harddrive to /etc/pm/power.d/ and -editing the copy, you could place only these two lines: +files in /etc/pm/power.d/ As an example, if you wanted to change the hdparm +setting for your hard drive's power management setting, you would copy the +entire file at /usr/lib(64)/pm-utils/power.d/harddrive to /etc/pm/power.d/ +and edit the copy to reflect your needs, e.g.: DRIVE_POWER_MGMT_BAT=128 # edit value as desired DRIVE_POWER_MGMT_AC=128 # edit value as desired @@ -111,20 +114,8 @@ chmod +x) in order to be used by pm-utils; otherwise, they will be ignored. ============================================================================== -One way to contribute to pm-utils indirectly is by writing and sending any -needed hooks scripts to upstream projects; as an example, the hook that -ships with wicd was contributed by me. Ideally, the pm-utils package should -have a very minimum number of hooks shipped with it, as they should ship with -the package to which the hook pertains; for example, the grub package would -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 / |