User talk:Sarunas

Hi - your page on getting ubuntu running on the X60s was very useful.

I have a x60s as well but I'm seeing different results for cpu frequency scaling. Initially I see the same in cpufreq-info where the second processor gets stuck at 1.6 GHz. When I remove powersaved and insert the modules speedste_centrino and freq_table my available governers go away

# cpufreq-info 
cpufrequtils 0.4: cpufreq-info (C) Dominik Brodowski 2004
Report errors and bugs to linux@brodo.de, please.
analyzing CPU 0:
  driver: centrino
  CPUs which need to switch frequency at the same time: 0
  hardware limits: 1000 MHz - 1.67 GHz
  available frequency steps: 1.67 GHz, 1.33 GHz, 1000 MHz
  available cpufreq governors: performance
  current policy: frequency should be within 1000 MHz and 1.67 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 1.67 GHz (asserted by call to hardware).
analyzing CPU 1:
  driver: centrino
  CPUs which need to switch frequency at the same time: 1
  hardware limits: 1000 MHz - 1.67 GHz
  available frequency steps: 1.67 GHz, 1.33 GHz, 1000 MHz
  available cpufreq governors: performance
  current policy: frequency should be within 1000 MHz and 1.67 GHz.
                  The governor "performance" may decide which speed to use
                  within this range.
  current CPU frequency is 1.67 GHz (asserted by call to hardware).

So as you can see all I have is "performance" which is no good for running off the battery. Out of curiosity what available governers do you see, do you mind giving me a dump of what modules you have loaded?

Thanks --Jarv 03:33, 26 April 2006 (CEST)

Jarv, CPU frequency governors are compiled as modules in Flight6 stock kernel(s), except for performance governor:

~# grep GOV config-2.6.15-20-686 
 CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
 # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set
 CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
 CONFIG_CPU_FREQ_GOV_POWERSAVE=m
 CONFIG_CPU_FREQ_GOV_USERSPACE=m
 CONFIG_CPU_FREQ_GOV_ONDEMAND=m
 CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m

I believe they always loaded automatically on system start, i.e. I did nothing additionally:

 ~# lsmod|grep cpu
 cpufreq_userspace       6496  0
 cpufreq_stats           6688  0
 cpufreq_powersave       1920  0
 cpufreq_conservative     9000  0
 cpufreq_ondemand        7752  2
 freq_table              4928  2 cpufreq_stats,speedstep_centrino

I did install sysfsutils and added two lines into /etc/sysfs.conf to set the governor to ondemand:

 devices/system/cpu/cpu0/cpufreq/scaling_governor=ondemand
 devices/system/cpu/cpu1/cpufreq/scaling_governor=ondemand

Please note there was an error in sysfs path in my original post, I missed the /system/ part. cpufreq-info in my case:

 ~# cpufreq-info
 cpufrequtils 0.4: cpufreq-info (C) Dominik Brodowski 2004
 Report errors and bugs to linux@brodo.de, please.
 analyzing CPU 0:
  driver: centrino
  CPUs which need to switch frequency at the same time: 0
  hardware limits: 1000 MHz - 1.50 GHz
  available frequency steps: 1.50 GHz, 1000 MHz
  available cpufreq governors: userspace, powersave, conservative, ondemand, performance
  current policy: frequency should be within 1000 MHz and 1.50 GHz.
                 The governor "ondemand" may decide which speed to use
                 within this range.
  current CPU frequency is 1000 MHz (asserted by call to hardware).
 analyzing CPU 1:
  driver: centrino
  CPUs which need to switch frequency at the same time: 1
  hardware limits: 1000 MHz - 1.50 GHz
  available frequency steps: 1.50 GHz, 1000 MHz
  available cpufreq governors: userspace, powersave, conservative, ondemand, performance
  current policy: frequency should be within 1000 MHz and 1.50 GHz.
                  The governor "ondemand" may decide which speed to use
                 within this range.
  current CPU frequency is 1000 MHz (asserted by call to hardware).

Sarunas 09:19, 26 April 2006 (EDT)

working now

thanks! the combination of getting the right modules in there and fixing sysfs made it work, I'm now scaling the processor correctly and got another 2 hours out of my battery which is fantastic.--Jarv 20:13, 26 April 2006 (CEST)