September 18, 20233 yr The problem persist on both Armbian 23.8 bullseye and Armbian 23.11.0-trunk.107 Bullseye After change it via armbian-config It stays the default cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 149 us. hardware limits: 408 MHz - 1.99 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.10 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 1.99 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 1.99 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.99 GHz (asserted by call to hardware). cpufreq stats: 408 MHz:0.86%, 600 MHz:9.43%, 816 MHz:3.66%, 1.10 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 1.99 GHz:86.04% (10441) analyzing CPU 1: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 149 us. hardware limits: 408 MHz - 1.99 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.10 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 1.99 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 1.99 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.99 GHz (asserted by call to hardware). cpufreq stats: 408 MHz:0.86%, 600 MHz:9.43%, 816 MHz:3.66%, 1.10 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 1.99 GHz:86.04% (10441) analyzing CPU 2: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 149 us. hardware limits: 408 MHz - 1.99 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.10 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 1.99 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 1.99 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.99 GHz (asserted by call to hardware). cpufreq stats: 408 MHz:0.86%, 600 MHz:9.43%, 816 MHz:3.66%, 1.10 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 1.99 GHz:86.04% (10441) analyzing CPU 3: driver: cpufreq-dt CPUs which run at the same hardware frequency: 0 1 2 3 CPUs which need to have their frequency coordinated by software: 0 1 2 3 maximum transition latency: 149 us. hardware limits: 408 MHz - 1.99 GHz available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.10 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 1.99 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 408 MHz and 1.99 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.99 GHz (asserted by call to hardware). cpufreq stats: 408 MHz:0.86%, 600 MHz:9.43%, 816 MHz:3.66%, 1.10 GHz:0.00%, 1.42 GHz:0.00%, 1.61 GHz:0.00%, 1.80 GHz:0.00%, 1.99 GHz:86.04% (10441)
September 28, 20233 yr I had this problem on Rpi4 board. Have a look at this https://docs.armbian.com/User-Guide_Fine-Tuning/#how-to-alter-cpu-frequency Edit /etc/default/cpufrequtils and set ENABLED=true in first line
September 28, 20233 yr Author @zetroot Thanks for the reply, just checked today and changing it via armbian-config is working again on 23.8.3
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.