Have a look in
/var/log/messages. All errors and warnings are
logged there by default. You may additionally want to set up
verbosity: set DEBUG variable to 7 or even to 15 in
/etc/powersave/common and restart the powersave
service/daemon to isolate the error. Messages are again logged
If you experience ACPI related problems (normally logged in dmesg, or missing directories in /proc/acpi) (try: dmesg |grep -i acpi and watch out for errors).
Please visit the homepage of your laptop vendor and update your BIOS. Nag your vendor to stick to the newest ACPI specifications in their BIOS!
If they still occur you could try to find out why by debugging ACPI parts of your system (see ACPI_Debugging and to override your DSDT (see: DSDT).
See in the kernel source if your processor is supported:
(You need to install the kernel-source package)
and if you need a special module or module option (see Cpufreq). If you need
a special module/option use following variables:
/etc/powersave/cpufreqconfig file to set them.
As older a battery as worse its capacity. But it may still work suitable, only the values delivered to the OS may be wrong.
See section above.
This is a feature, not a bug.
The processor's frequency is lowered if supported and
the processor is idle.
cat /dev/zero > /dev/null &
The system's load should then be on 100% and the
processor should run at highest speed (see
If you encounter following error using the powersave binary: Could not connect to daemon. Is the daemon running? Are you privileged to connect to the powersave daemon?
You probably have a DBus connection problem.
Check the security config file for the powersave daemon in
the DBus configuration (default:
Try to restart the DBus daemon.
powersave -c. If POWERSAVE is returned your CPU always runs
on lowest frequency.
A slow system could of course have totally other reasons. Check your system (top, ps, ...).
Have a look in
/proc/acpi/processor/*/throttling. If the state
is not T0 even your CPU load is high disable
throttling in your scheme configuration files (see Schemes).
Another reason could be that you use the p4-clockmod module
lsmod |grep p4).
You should not do that. Throttling is done through another
interface. Using both slows down the CPU unpredictable.
Be sure this module is not used in
or loaded in any other way.