Reason for this bug is a missing default setting in karmic.
1. In user gconf the apps/gnome-power-manager/cpufreq tree is missing completely
2. sysfsutils are not installed by default
3. The gnome-cpu applet cannot save changes permanently
We have a undefined state after boot, the kernel dont know what to do and goes crazy.
If a userspace daemon like powernowd is installed or sysfsutils with following conf the situation can be cleared.
#
# /etc/sysfs.conf - Configuration file for setting sysfs attributes.
#
# The sysfs mount directory is automatically prepended to the attribute paths.
#
# Syntax:
# attribute = value
# mode attribute = 0600 # (any valid argument for chmod)
# owner attribute = root:wheel # (any valid argument for chown)
#
# Examples:
#
# Always use the powersave CPU frequency governor
# devices/system/cpu/cpu0/cpufreq/scaling_governor = powersave
devices/system/cpu/cpu0/cpufreq/scaling_governor = ondemand
Reason for this bug is a missing default setting in karmic.
1. In user gconf the apps/gnome- power-manager/ cpufreq tree is missing completely
2. sysfsutils are not installed by default
3. The gnome-cpu applet cannot save changes permanently
We have a undefined state after boot, the kernel dont know what to do and goes crazy.
If a userspace daemon like powernowd is installed or sysfsutils with following conf the situation can be cleared.
# system/ cpu/cpu0/ cpufreq/ scaling_ governor = powersave system/ cpu/cpu0/ cpufreq/ scaling_ governor = ondemand
# /etc/sysfs.conf - Configuration file for setting sysfs attributes.
#
# The sysfs mount directory is automatically prepended to the attribute paths.
#
# Syntax:
# attribute = value
# mode attribute = 0600 # (any valid argument for chmod)
# owner attribute = root:wheel # (any valid argument for chown)
#
# Examples:
#
# Always use the powersave CPU frequency governor
# devices/
devices/
This bug duplicates to: 460064, 475706, 434255