On Friday 25 November 2005 20:03, Ted Unangst wrote: > maybe, speedstep can only be set to fast and slow, and the driver > won't move things if it thinks nothing is changing. maybe there's a > bug, maybe you need to fiddle it up and down some to make it actually > work, but 0 and 100 are the only settings that really mean anything.
It would seem nothing is happening: $ sysctl hw | tail -2 hw.cpuspeed=1296 hw.setperf=100 $ md5 -t MD5 time trial. Processing 10000 10000-byte blocks... Digest = 52e5f9c9e6f656f3e1800dfa5579d089 Time = 0.691865 seconds Speed = 144536867.741539 bytes/second $ sudo sysctl -w hw.setperf=0 hw.setperf: 100 -> 0 $ sysctl hw | tail -2 hw.cpuspeed=1296 hw.setperf=0 $ md5 -t MD5 time trial. Processing 10000 10000-byte blocks... Digest = 52e5f9c9e6f656f3e1800dfa5579d089 Time = 0.693320 seconds Speed = 144233542.952749 bytes/second $ sudo sysctl -w hw.setperf=80 hw.setperf: 0 -> 80 $ sysctl hw | tail -2 hw.cpuspeed=750 hw.setperf=80 $ md5 -t MD5 time trial. Processing 10000 10000-byte blocks... Digest = 52e5f9c9e6f656f3e1800dfa5579d089 Time = 0.695775 seconds Speed = 143724623.621142 bytes/second Is there any way to determine from the dmesg if speedstep is detected? --- Lars Hansson
