I think your problem is solved in edgy, for edgy uses the performance
governor by default. Backporting or updating the dapper packages in this
way is imo not a good idea, since it might introduce new problems. Your
report would have been a candidate for the wishlist, but since I cannot
see where we
I do have powernowd installed.
--
laptop-mode does not twiddle CPU frequency
https://launchpad.net/bugs/25226
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Sorry, mixed up sys and proc. If I remember correctly the CPU-scaling in
dapper is done by powernowd - in my dapper it worked out of the box, but
I do not have a dapper @hand any more, so I can't check it. But iirc by
default the selected govenor is userspace all the time - everything else
gets han
Yes, I use the default Dapper kernel.
I don't know where in /proc I can adjust the frequency. I can adjust the
frequency using /sys:
[EMAIL PROTECTED]:~# echo "100" >
/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
[EMAIL PROTECTED]:~# echo "120" >
/sys/devices/system/cpu/cpu0/
A few questions. Do you use the default kernel? Does setting the
governor directly via /proc/?
** Changed in: laptop-mode (Ubuntu)
Assignee: (unassigned) => a7p
Status: Unconfirmed => Needs Info
--
laptop-mode does not twiddle CPU frequency
https://launchpad.net/bugs/25226
--
ubunt