Bugzilla – Bug 148272
kpowersave does not show CPU frequency menu, power schemes nor suspend entries
Last modified: 2007-06-05 11:04:27 UTC
Hi, I am on 10.1m Beta3 and my kpowersave does not show power schemes, cpu frequency settings nor any suspend button. Also, the "Logoff" screen does not give the "suspend" button. powersave daemon is running, frequency scaling is enabled (Centrino) with on-demand governor (cpufreq-info says so). I have installed a customized DSDT to fix my battery status, now it all seems to work apart from the missing entries in Log Off and kpowersave menu. dmesg says cpufreq is enabled: ######### IA-32 Microcode Update Driver: v1.14 <tigran@veritas.com> IA-32 Microcode Update Driver v1.14 unregistered bootsplash: status on console 0 changed to on NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver powernow: This module only works with AMD K7 CPUs acpi-cpufreq: CPU0 - ACPI performance management activated. bootsplash: status on console 0 changed to on #########
what say powersave -c -x ? Is hal running (ps aux | grep hal)?
Hi: linux:/home/thomas # powersave -c -x DYNAMIC Acoustic Performance active AC_default_scheme Powersave battery_default_scheme Presentation AdvancedPowersave linux:/home/thomas # ps aux | grep hal root 11210 1.8 0.5 4336 2916 ? Ss 23:37 0:02 /usr/sbin/hald --daemon=yes --retain-privileges root 11381 0.0 0.1 1820 672 ? S 23:37 0:00 hald-addon-acpi root 11707 0.0 0.1 1820 620 ? S 23:37 0:00 hald-addon-storage root 13581 0.0 0.1 2820 760 pts/3 S+ 23:39 0:00 grep hal
Thomas, you forget to switch back the bug to ASSIGNED. :-( (While in NEEDINFO state, the developers won't see it...)
(In reply to comment #3) > (While in NEEDINFO state, the developers won't see it...) This is simply incorrect, we see them!
I have to admit, I'm pretty helpless ;-) Thomas, can you please log in as root and check whether this changes anything? A 'ps aux | grep dbus' could also be helpful, but I daubt this will give use new information because all the powersave command seem to produce right output.
Any news here? reproduceable with beta4 ?
In Beta4 all right!
o.k. then i close the bug