[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: cpufreq not loaded in amd64?



On Thu, 2010-09-30 at 05:34 +0000, s. keeling wrote:
> Damon L. Chesser <damon@damtek.com>:
> >  For some reason, I don't have cpufreq scaling enabled:
> 
> Well that's pretty damned sad.  :-P  I really don't get cpufreq*
> myself.  Methinks it's far too young software.
> 
> >  damon@dam-main:~$ sudo powernowd -d
> >  PowerNow Daemon v1.00, (c) 2003-2008 John Clemens
> >  /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus: No such file or
> >  directory
> >  err=2Found 2 scalable units:  -- 1 'CPU' per scalable unit
> >  /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq: No such file or
> >  directory
> > [snip]
> >  damon@dam-main:~$ sudo lsmod |grep cpufreq
> >  cpufreq_stats           2659  0 
> >  cpufreq_userspace       1992  0 
> >  cpufreq_conservative     5162  0 
> >  cpufreq_powersave        902  0 
> > 
> >  damon@dam-main:~$ sudo lsmod |grep powernow
> >  damon@dam-main:~$ 
> > 
> >  Oops, no powernow-k* listed.
> > 
> >  root@dam-main:/home/damon# modprobe powernow-k8
> >  FATAL: Error inserting powernow_k8
> >  (/lib/modules/2.6.32-5-amd64/kernel/arch/x86/kernel/cpu/cpufreq/powernow-k8.ko): No such device
> > 
> >  dmesg |grep cpu -i shows (only in part)
> > 
> >  [   18.891118] powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core
> >  Processor 4800+ processors (2 cpu cores) (version 2.20.00)
> > 
> >  so after googling, I see this problem pop up, but the "newest" one is at
> >  least a year old and I don't see a solution.  
> 
> (0) infidel /home/keeling_ uname -a
> Linux infidel 2.6.32-bpo.5-amd64 #1 SMP Fri Jun 11 23:33:19 UTC 2010 x86_64 GNU/Linux
> (0) infidel /home/keeling_ lsmod | grep power
> cpufreq_powersave        902  0
> powernow_k8            10978  0
> processor              30135  1 powernow_k8
> 
> >  What do I need to do?
> 
> Damned good question.  What do lm-sensors do there?
> 
> (0) [root] infidel /root_ sensors
> acpitz-virtual-0
> Adapter: Virtual device
> temp1:       +74.0°C  (crit = +105.0°C)
> 
> My sandbox is far more expressive:
> 
> (0) infidel /home/keeling_ ssh phreaque sensors
> emc6d100-i2c-0-2e
> Adapter: SMBus I801 adapter at fc00
> in0:         +0.00 V  (min =  +0.00 V, max =  +3.32 V)   ALARM
> in1:         +1.50 V  (min =  +0.00 V, max =  +2.99 V)
> in2:         +3.27 V  (min =  +0.00 V, max =  +4.38 V)
> in3:         +5.08 V  (min =  +0.00 V, max =  +6.64 V)
> in4:        +12.00 V  (min =  +0.00 V, max = +15.94 V)
> in5:         +0.00 V  (min =  +0.00 V, max =  +4.38 V)
> in6:         +0.02 V  (min =  +0.00 V, max =  +1.99 V)
> in7:         +0.00 V  (min =  +0.00 V, max =  +2.39 V)
> fan1:       1480 RPM  (min =    0 RPM)
> fan2:          0 RPM  (min =    0 RPM)
> fan3:          0 RPM  (min =    0 RPM)
> fan4:          0 RPM  (min =    0 RPM)
> temp1:        +0.0°C  (low  = -127.0°C, high = +127.0°C)
> temp2:       +40.0°C  (low  = -127.0°C, high = +127.0°C)
> temp3:       +47.0°C  (low  = -127.0°C, high = +127.0°C)
> cpu0_vid:   +1.525 V
> 
> >  cat /etc/debian_version 
> >  squeeze/sid
> 
> 5.0.6
> 
> Lenny.  Que pasa mon?  :-)

Hey S. Keeling.  Thanks for the replay, always nice to hear from you
going back to the Libranet days.  However, I figured this one out.  User
error.  My bios had "Cool and Quite" turned off.  I did not catch that,
I was looking for some other bios settings.  I really am not a big fan
of cpufreq scaling, however, I figure it saves my on the power bill, but
I keep forgetting to turn it off when I fire up a vm (vms hate cpu freq
scaling).  Just trying to do my small part to keep Canada cool by not
heating up the US SE.
> 
> -- 
> Any technology distinguishable from magic is insufficiently advanced.
> (*)    http://blinkynet.net/comp/uip5.html      Linux Counter #80292
> - -    http://www.faqs.org/rfcs/rfc1855.html    Please, don't Cc: me.
> 
> 

-- 
Damon
damon@damtek.com


Reply to: