Hi,
i grappeded out my old Raspberry Pi 1 Model B rev 2 and gave it the latest Raspberry Pi OS Lite (32-Bit) (release date 2024-11-19).
For that i used the Raspberry Pi Imager.
I also tried out the legacy OS Lite.
With both OS i have the following problem:
arm_freq_min and arm_freq_max do not have any effect. I read out hardware frequency limits via different ways linux provides:
- cpufreq-info
- cat /sys/devices/system/cpu/cpu0/cpufreq/...
- and so on
Example:
arm_freq=700 will output a frequency range of 700 to 700 MHz (default)
arm_freq=900 will output a frequency range of 700 to 900 MHz (overclock)
arm_freq=600 will output a frequency range of 500 to 700 MHz (underclock)
>>> vcgencmd measures frequencies, which are occording to the settings.
I tried out several combinations, like only writing arm_freq_min, or only arm_freq_max or one before the other, all three, and so on.
It seems like arm_freq sets a frequency above or below the default system frequency.
Trying to override with cpufreq -f didn't change the freq bejond the limits.
So why is that? I remember, in the past people actually where able to use arm_freq_min and _max on a raspberry Pi 1B. Are these overriden somewhere in the new OSes?
The governer setting also doesn't change anything.
Any ideas?
Greets
This is the current config.txt:
i grappeded out my old Raspberry Pi 1 Model B rev 2 and gave it the latest Raspberry Pi OS Lite (32-Bit) (release date 2024-11-19).
For that i used the Raspberry Pi Imager.
I also tried out the legacy OS Lite.
With both OS i have the following problem:
arm_freq_min and arm_freq_max do not have any effect. I read out hardware frequency limits via different ways linux provides:
- cpufreq-info
- cat /sys/devices/system/cpu/cpu0/cpufreq/...
- and so on
Example:
arm_freq=700 will output a frequency range of 700 to 700 MHz (default)
arm_freq=900 will output a frequency range of 700 to 900 MHz (overclock)
arm_freq=600 will output a frequency range of 500 to 700 MHz (underclock)
>>> vcgencmd measures frequencies, which are occording to the settings.
I tried out several combinations, like only writing arm_freq_min, or only arm_freq_max or one before the other, all three, and so on.
It seems like arm_freq sets a frequency above or below the default system frequency.
Trying to override with cpufreq -f didn't change the freq bejond the limits.
So why is that? I remember, in the past people actually where able to use arm_freq_min and _max on a raspberry Pi 1B. Are these overriden somewhere in the new OSes?
The governer setting also doesn't change anything.
Any ideas?
Greets
This is the current config.txt:
Code:
# For more options and information see# http://rptl.io/configtxt# Some settings may impact device functionality. See link above for details# Uncomment some or all of these to enable the optional hardware interfaces#dtparam=i2c_arm=on#dtparam=i2s=on#dtparam=spi=on# Enable audio (loads snd_bcm2835)dtparam=audio=on# Additional overlays and parameters are documented# /boot/firmware/overlays/README# Automatically load overlays for detected camerascamera_auto_detect=1# Automatically load overlays for detected DSI displaysdisplay_auto_detect=1# Automatically load initramfs files, if foundauto_initramfs=1# Enable DRM VC4 V3D driverdtoverlay=vc4-kms-v3dmax_framebuffers=2# Don't have the firmware create an initial video= setting in cmdline.txt.# Use the kernel's default instead.disable_fw_kms_setup=1# Disable compensation for displays with overscandisable_overscan=1# Run as fast as firmware / board allowsarm_boost=1[cm4]# Enable host mode on the 2711 built-in XHCI USB controller.# This line should be removed if the legacy DWC2 controller is required# (e.g. for USB device mode) or if USB support is not required.otg_mode=1[cm5]dtoverlay=dwc2,dr_mode=host[all]arm_freq=800core_freq=500sdram_freq=600over_voltage=2Statistics: Posted by pi_noo1337 — Thu Apr 24, 2025 4:24 pm