<br><br><div class="gmail_quote">On Sun, Sep 12, 2010 at 11:30 PM, Ben Armstrong <span dir="ltr"><<a href="mailto:synrg@sanctuary.nslug.ns.ca">synrg@sanctuary.nslug.ns.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 12/09/10 07:13 PM, Daniel Harris wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The above commands work with the correct output as indicated above but unless I am doing something stupid nothing changes. The desktop aplet remains at 800MHz and cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq = 800000. Again if I change it with the applet I can get the cpu to change to 1600000.<br>
</blockquote>
<br></div>
The applet can only report what SpeedStep setting the CPU reports. That doesn't accurately reflect the effective speed of the CPU which is a multiple of bus speed. But we can determine that there was a change by indirect means (aside from directly reading cpufv):<br>
<br>
Run three trials at each of the settings of this crude benchmark:<br>
<br>
time sh -c "echo '2^2^20' | bc > /dev/null"<br>
<br>
Or else use find & use some bona fide CPU benchmark.<br><font color="#888888">
<br>
Ben<br>
<br>
</font></blockquote></div>OK I was doing something stupid the cpu test indicate all is working perfectly. Its the applet that is wrong.<br><br>Thanks for walking me through that.<br><br>Dan<br>