Hi,
I just installed Alpine 16 on an old Raspberry PI B.
I want to use the ondemand governor and set the freq between 100 and 700.
Unfortunately it looks like the arm_freq_min is ignored.
if I set :
arm_freq=700
arm_freq_min=500
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
returns 700000 only
But if I set
arm_freq=500
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
returns 700000 500000
Strange isn't it ? Did I misunderstand something? Or is there a bug in the
fernel/firmware ?
On Sun May 29, 2022 at 1:16 AM CEST, Jerome Marc wrote:
> Hi,>> I just installed Alpine 16 on an old Raspberry PI B.> I want to use the ondemand governor and set the freq between 100 and 700.> Unfortunately it looks like the arm_freq_min is ignored.> if I set :> arm_freq=700> arm_freq_min=500>> cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies> returns 700000 only>> But if I set> arm_freq=500>> cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies> returns 700000 500000>> Strange isn't it ? Did I misunderstand something? Or is there a bug in the> fernel/firmware ?https://www.raspberrypi.com/documentation/computers/config_txt.html is
your friend :)
i don't remember which gen the Pi B is from (i assume 1?), but it is not
recommended to ever set the minimum below the default, nor are there any
real power savings from it (and it's not supported). so, just keep it at
the default of 700.
as for where the issue lies, it's in the rpi firmware that reads the
values and applies things- if it ignores it, then it's just ignored,
unrelated to the kernel.
Hi Alice,
Thank you very much. You are perfectly right however I investigated and
found interesting results. Yes it's a PI 1B model that I used for years as
a media center.
I want to use it as a home gateway (smart home and various network
services) therefore it will be online 24/24 7/7 this is the reason why I
wanted to limit energy consumption as much as possible...
First of all, arm_freq_min has been disabled in the latest firmwares.
Basically you cannot set a value lower than the factory value. But there is
a workaround : if you set arm_freq with a low value you get a similar
result. Don't tell it loud else the firmware devs could block this as well.
I applied these settings :
arm_freq =100
gpu_freq_min=100
gpu_mem=32
initial_turbo=60
And I activated the conservative governor
All is working fine : At idle cpu and gpu are running at 100 and on load
they run at standard levels.
I verified the gains with a wattmeter and I was very disappointed :-).
Basically the gain was about 0.1 watt (drop from 2.3 to 2.2). The measure
was done at the wall with ethernet connected. Disconnecting the ethernet
cable made the power consumption drop to about 1.5w
Yes, it's disappointing. I was hoping to be close to 1w. The RPI 1B is
quite power hungry because of a poorly designed power circuit, that's it.
However I think I reduced the heat which is a good thing. The system is
still snappy despite running at low freq when idling. Didn't have any
crashes so far.
I even tried to reduce the voltage at idle using over_voltage_min=-4 but
this led to mmc errors in the log and the SD card was corrupted.
Jerome
Le dim. 29 mai 2022 à 04:14, alice <alice@ayaya.dev> a écrit :
> On Sun May 29, 2022 at 1:16 AM CEST, Jerome Marc wrote:> > Hi,> >> > I just installed Alpine 16 on an old Raspberry PI B.> > I want to use the ondemand governor and set the freq between 100 and 700.> > Unfortunately it looks like the arm_freq_min is ignored.> > if I set :> > arm_freq=700> > arm_freq_min=500> >> > cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies> > returns 700000 only> >> > But if I set> > arm_freq=500> >> > cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies> > returns 700000 500000> >> > Strange isn't it ? Did I misunderstand something? Or is there a bug in> the> > fernel/firmware ?>> https://www.raspberrypi.com/documentation/computers/config_txt.html is> your friend :)>> i don't remember which gen the Pi B is from (i assume 1?), but it is not> recommended to ever set the minimum below the default, nor are there any> real power savings from it (and it's not supported). so, just keep it at> the default of 700.>> as for where the issue lies, it's in the rpi firmware that reads the> values and applies things- if it ignores it, then it's just ignored,> unrelated to the kernel.>