Sergii: Could you do the following: 1. Change the powernowd start script back to the original state 2. Boot your machine regularly into feisty 3. Do *NOT* log into X 4. Change to console (Ctrl-Alt-F1) 5. Log in 6. cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor (tell me the output) 7. Log into X 8. When everything is fully loaded, do 6 again (tell me the output)
I've had the same issue; My problem lies with gnome-power-manager though - because the powernowd initscript correctly sets the scaling_governor to "ondemand". When logging into X, g-p-m sets the scaling_governor to "performance", "conservative" or "powersave", depending on its settings. The question is why g-p-m never changes it to "ondemand" if Matthew already says that's a better settings if the machine supports it. Please tell me your output from above, we'll open a new bug for g-p-m if you have the same issue. -- The issues powernowd init script. https://launchpad.net/bugs/74980 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
