On Fri, Feb 27, 2009 at 12:12 PM, Troy Dawson <[log in to unmask]> wrote: > I guess I didn't specify this. > This is for AMD processors only, specifically those with powernow. > The cpuspeed *doesn't* have a kernel module, but the new 2.6.18-128 does > have a new kernel module specifically called powernow-k8. > This cpuspeed needs to get pushed out with the last kernel errata that we > pushed out. But I want to make sure that it actually fixes the problem that > people are having before I push it out. > Troy [ I don't have an AMD machine running SL, so this was tested with CentOS-5.2 ] [root@apollo ~]# cat /proc/cpuinfo | grep model model : 67 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ [root@apollo ~]# uname -mr 2.6.18-128.1.1.el5 x86_64 <-- installed from SL5.3RC1 [root@apollo ~]# /sbin/modprobe powernow-k8 [root@apollo ~]# lsmod Module Size Used by cpufreq_ondemand 42449 1 powernow_k8 58073 1 freq_table 40889 2 cpufreq_ondemand,powernow_k8 [root@apollo ~]# /sbin/service cpuspeed status cpuspeed is stopped [root@apollo ~]# /sbin/service cpuspeed start Enabling ondemand cpu frequency scaling: [ OK ] [root@apollo cpufreq]# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors ondemand userspace performance [root@apollo cpufreq]# rpm -q cpuspeed cpuspeed-1.2.1-3.el5.x86_64 As you can see, I have not updated to cpuspeed-1.2.1-5. So, it seems to be working fine with cpuspeed-1.2.1-3. Akemi