[Edgy] powersaved and kpowersave ->issues under KDE

similar issue is bug #61011

With latest updates problems 1) and 3) seem to have been fixed.

Same issue installing klaptop instead of kpowersave. Issues 1) and 3) are confirmed.

Issues 1. and 3. are completely unrelated, this is why they were probably addressed by other updates.

Regarding speedstep not being enabled, please clarify what does "not enabled" mean? Is module not loaded? Does CPU frequency scalling work?

I would need to get more data:
- attach output of dmesg after the boot
- attach output of lsmod after the boot
- attach output of lsmod after running powersaved restart

>>Issues 1. and 3. are completely unrelated, this is why
>>they were probably addressed by other updates.

I reinstalled kpowersave and the 3 issues came back all together, so they seem correlated either to the lack of kde-guidance-powermanager or to the presence of kpowersave (or klaptop). So issue 1 and 3 are no more fixed.

>>what does "not enabled" mean?
I don't remember the behavior when I filed the bug (some week ago). Now kernel speed-step module is loaded but 'performance' is the only scaling_available_governor

$ cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
performance

I will provide you the infos.

$ sudo /etc/init.d/powersaved restart
 * Stopping power management daemon powersaved [fail]
 * Starting power management daemon powersaved [fail]
##########################################################
# ACPI system but acpid not running. #
# Please install acpid package, then restart powersaved! #
##########################################################

Now I can't get powersaved started, see bug #64646 for more infos and please let's continue there.

Sorry, but the bugs are quite old and related to 2 different periods and we're messing them up. Consider this bug obsolete, I will add there other info.

After boot, cpufreq modules are not loaded. After powersaved, they are loaded:

cpufreq_ondemand 8876 0
cpufreq_userspace 5408 0
cpufreq_powersave 2944 0

Not sure why this does not happen on boot.

Me too! Same bug.

Please, soahil, also add your comment to bug #64646. Thanks.

I also had the second problem, see my bug report (FIX included) Bug #68423

I have seen all the same problems.
I'm not quite sure what the problem with the small fonts are, but I left the kde-guidance-powermanagment installed so that my fonts will stay correct.

For the second problem the problem i that acpid needs to start before hald (which is started by the dbus script rather than it's own script for some reason).

You can test it out by stopping dbus, restarting acpid and then starting dbus again. You should get no error messages and kpowersave will start working.

The more permanent solution is to change the numbering of the startup links in the rcN.d directories so that acpid (originally S50acpid) starts before dbus (originally S20dbus).

Sorry I'm not sure about the correct nomenclature here, I'm new to (k)ubuntu and it was years since I used debian.

As of 2): I suspect that this is a bug in /etc/init.d/powersaved. I had the same problem and found that the modules are loaded, then the governours are started and then it waits 0.2 for the modules to load. I put the sleep 0.2 BEFORE the starting of the governours and voilá: it works.

[Expired for powersave (Ubuntu) because there has been no activity for 60 days.]