Package: cpufrequtils
Version: 007-1

After setting the governer "userspace", I am able to assign all cpu frequencies 
except 1.07GHz on the Intel Atom processor for the Dell Mini 9.

root@box:/home/neybis# cpufreq-set -g userspace -c 0
root@box:/home/neybis# cpufreq-set -f 800MHz -c 0
root@box:/home/neybis# cpufreq-info -c 0
cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpuf...@vger.kernel.org, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0 1
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 1.60 GHz
  available frequency steps: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
  available cpufreq governors: userspace, powersave, conservative, ondemand, 
performance
  current policy: frequency should be within 800 MHz and 1.60 GHz.
                  The governor "userspace" may decide which speed to use
                  within this range.
  current CPU frequency is 800 MHz (asserted by call to hardware).
  cpufreq stats: 1.60 GHz:17.22%, 1.33 GHz:37.18%, 1.07 GHz:0.07%, 800 
MHz:45.52%  (2021)
root@box:/home/neybis# cpufreq-set -f 1.6GHz -c 0
root@box:/home/neybis# cpufreq-info -c 0
cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpuf...@vger.kernel.org, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0 1
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 1.60 GHz
  available frequency steps: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
  available cpufreq governors: userspace, powersave, conservative, ondemand, 
performance
  current policy: frequency should be within 800 MHz and 1.60 GHz.
                  The governor "userspace" may decide which speed to use
                  within this range.
  current CPU frequency is 1.60 GHz (asserted by call to hardware).
  cpufreq stats: 1.60 GHz:17.20%, 1.33 GHz:37.00%, 1.07 GHz:0.07%, 800 
MHz:45.72%  (2022)
root@box:/home/neybis# cpufreq-set -f 1.33GHz -c 0
root@box:/home/neybis# cpufreq-info -c 0
cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpuf...@vger.kernel.org, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0 1
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 1.60 GHz
  available frequency steps: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
  available cpufreq governors: userspace, powersave, conservative, ondemand, 
performance
  current policy: frequency should be within 800 MHz and 1.60 GHz.
                  The governor "userspace" may decide which speed to use
                  within this range.
  current CPU frequency is 1.33 GHz (asserted by call to hardware).
  cpufreq stats: 1.60 GHz:17.45%, 1.33 GHz:36.93%, 1.07 GHz:0.07%, 800 
MHz:45.55%  (2023)
root@box:/home/neybis# cpufreq-set -f 1.07GHz -c 0
root@box:/home/neybis# cpufreq-info -c 0
cpufrequtils 007: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpuf...@vger.kernel.org, please.
analyzing CPU 0:
  driver: acpi-cpufreq
  CPUs which run at the same hardware frequency: 0 1
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 10.0 us.
  hardware limits: 800 MHz - 1.60 GHz
  available frequency steps: 1.60 GHz, 1.33 GHz, 1.07 GHz, 800 MHz
  available cpufreq governors: userspace, powersave, conservative, ondemand, 
performance
  current policy: frequency should be within 800 MHz and 1.60 GHz.
                  The governor "userspace" may decide which speed to use
                  within this range.
  current CPU frequency is 1.33 GHz (asserted by call to hardware).
  cpufreq stats: 1.60 GHz:17.39%, 1.33 GHz:37.14%, 1.07 GHz:0.07%, 800 
MHz:45.40%  (2023)
root@box:/home/neybis#



I did no configuration after installing the necessary packages. Everything 
worked out of the box. Not sure what could cause this. Maybe its not grabbing 
the arguments properly or the driver is not fully functional. : /

Reply via email to