|
2010-11-06
, 09:49
|
|
Posts: 623 |
Thanked: 289 times |
Joined on Jan 2010
@ UK
|
#2
|
|
2010-11-06
, 12:13
|
Posts: 838 |
Thanked: 292 times |
Joined on Apr 2010
|
#3
|
|
2010-11-06
, 13:30
|
Posts: 838 |
Thanked: 292 times |
Joined on Apr 2010
|
#4
|
|
2010-11-06
, 15:56
|
|
Posts: 623 |
Thanked: 289 times |
Joined on Jan 2010
@ UK
|
#5
|
cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
|
2010-11-06
, 16:50
|
Posts: 838 |
Thanked: 292 times |
Joined on Apr 2010
|
#6
|
If straight after booting you overclock, or part of your boot process you overclock and you minimum setting is setup you will find that the kernel will not go below your that setting despite reporting it can. You can check this with:
Code:cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
kernel-config load lv
kernel-config limits 250 850
kernel-config save lv-250-850
kernel-config default lv-250-850
after issuing kernel-config show it will show:
min. frequency: 250
max. frequency 850
but in an hour or so (with no reboot) issuing the same command will show the min. frequency as 125. I tried making 2 different default kernels and the result was the same...after an arbitrary period the output of kernel-config show will revert the min. frequency to 125.
why is this happening and what is really going on behind the sceens? thanks for listening...