I have a Raspberry Pi 4 aarch64 running DietPi v7.0.2. I’m trying to overclock it to 2.1Ghz, but it won’t boot past the preset profiles at 1.9 GHz.
I already tried reduce to 2.0Ghz and adjust overvolt to 5 and then 6, but nothing happened.
Can somebody please enlighten me on what I’m missing? I only changed settings on /boot/config. Is there another place?
What do you mean with “it won’t boot past…”?
If it does not boot, then I bet 2.0 GHz is simply too high for your board. As it’s not stable, we don’t have it as preset .
Or do you mean that it still sticks with 1.9 GHz, even you changed the config file to clock higher? In this case please show your config.txt.
I mean that I simply won’t boot. I saw some discussions, including this forum that the boar can hold up to 2147 MHz if you have the proper cooling system (which I have). They even mentioned this tutorial.The only thing that I haven’t done is this command sudo apt updatesudo apt dist-upgradesudo rpi-update, because I fear that things may conflict in the future with a dietpi-update.
If I set the clock through the presets menu, it will boot, but if I try to change the arm_freq value to 2100 direct in the config file, the board won’t boot. I really don’t know how the system works beyond setting the the values, so I have a theory this values might be conflicting somehow with the expected values set in the config file.
In case I run the sudo apt updatesudo apt dist-upgradesudo rpi-update command mentioned above, what could the consequences in the future updates?
And here is my config file as requested:
# Docs: https://www.raspberrypi.org/documentation/configuration/config-txt/
# If you get no picture, set the following to "1" to apply most compatible HDMI settings.
# Uncomment to adjust the HDMI signal strength if you have interferences, blanking, or no display.
# - Values from "0" to "11" are allowed, use values above "7" only if required, e.g. with very long HDMI cable.
# - Default on first RPi1 A/B is "2", else "5", on RPi4 this setting is ignored.
# Uncomment if HDMI display is not detected and composite is being outputted.
# Uncomment to disable HDMI even if plugged, e.g. to force composite output.
# Uncomment to force a console size. By default it will be display's size minus overscan.
# Uncomment to enable SDTV/composite output on RPi4. This has no effect on previous RPi models.
# SDTV mode
# Uncomment to force a specific HDMI mode (this will force VGA).
# Uncomment to force an HDMI mode rather than DVI. This can make audio work in DMT (computer monitor) modes.
# Set "hdmi_blanking=1" to allow the display going into standby after 10 minutes without input.
# With default value "0", the display shows a blank screen instead, but will not go into standby.
# NB: With "1" some applications (e.g. Kodi, OMXPlayer) cannot prevent display standby due to missing DPMS signal.
# Set to "1" if your display has a black border of unused pixels visible.
# Uncomment the following to adjust overscan. Use positive numbers if console goes off screen, and negative if there is too much border.
#-------RPi camera module-------
#-------GPU memory splits-------
#-------Boot splash screen------
# NB: Enabled for 1st run only. If you want to keep this setting, please set CONFIG_SERIAL_CONSOLE_ENABLE=1 in dietpi.txt before 1st boot.
Installation of rpi-update will not change anything at first stage. You just install the tool itself. However, if you would run it afterwards, you will be bumped to next Raspberry Pi OS kernel (development)
Thank you for the explanation! So I think it is safer to stay out of the development kernel.
rpi-update is generally not recommended indeed, as long as it does not contain a specific fix for a specific issue you face with the stable kernel. It’s a tool to test bleeding edge unstable development kernel and firmware versions.
Try to increase the ARM frequency in smaller steps, e.g
1950 Mhz first and overvoltage 5 if that does not boot. You may also want to test disabling initial turbo, if it helps as then the max frequency is not applied directly at boot. Every chip is different, so while some may work fine with even 2100 Mhz, others may not even with 2000 Mhz.
DietPi-Config btw checks for and applies the exact same config.txt settings, so it does not conflict with manual changes.