Hi folks
It used to be at one time that recommended overclocks were in the default config.txt, but that seems like it might not be the case.
Most references now point to using rpi-config, but there's also no documentation that I can find to say what settings that sets currently.
The installation that I have doesn't have rpi-config and I don't really want to install a whole OS just so I can run rpi-config to find out the settings.
Could someone tell me what the various options are that are set on a pi 2? I did find a graphic screenshot here and there that might have some pi2 settings in it, but that doesn't tell me for sure that there aren't settings used that aren't shown.
Anyways, can anyone help me out by pointing me to where this is documented, or failing that just laying out what "default" settings for a pi2 are being used?
Thanks
-
- Posts: 14406
- Joined: Fri Mar 09, 2012 7:36 pm
- Location: Vallejo, CA (US)
Re: Default recommended pi 2 overclock settings
By and large, the newer Pis don't have any "recommended" overclock settings. They're running close to their limits already. There *may* be some "head room" for overclocking an older, Pi2Bv1.1. On the newer version, the Pi2Bv1.2, SoCs are only tested to run at 900MHz, even though the same part number is on the Pi3B and defaults to 1.2GHz there. This may be a case of "binning", where the Pi2Bv1.2 boards get chips that failed at the higher clock speed.
- DougieLawson
- Posts: 40821
- Joined: Sun Jun 16, 2013 11:19 pm
- Location: A small cave in deepest darkest Basingstoke, UK
- Contact: Website Twitter
Re: Default recommended pi 2 overclock settings
Except for the ones defined in raspi-config.W. H. Heydt wrote: ↑Sat Jan 12, 2019 1:44 amBy and large, the newer Pis don't have any "recommended" overclock settings.
Code: Select all
do_overclock() {
if ! is_pione && ! is_pitwo; then
whiptail --msgbox "This Pi cannot be overclocked." 20 60 2
return 1
fi
if [ "$INTERACTIVE" = True ]; then
whiptail --msgbox "\
Be aware that overclocking may reduce the lifetime of your
Raspberry Pi. If overclocking at a certain level causes
system instability, try a more modest overclock. Hold down
shift during boot to temporarily disable overclock.
See http://elinux.org/RPi_Overclocking for more information.\
" 20 70 1
if is_pione; then
OVERCLOCK=$(whiptail --menu "Choose overclock preset" 20 60 10 \
"None" "700MHz ARM, 250MHz core, 400MHz SDRAM, 0 overvolt" \
"Modest" "800MHz ARM, 250MHz core, 400MHz SDRAM, 0 overvolt" \
"Medium" "900MHz ARM, 250MHz core, 450MHz SDRAM, 2 overvolt" \
"High" "950MHz ARM, 250MHz core, 450MHz SDRAM, 6 overvolt" \
"Turbo" "1000MHz ARM, 500MHz core, 600MHz SDRAM, 6 overvolt" \
3>&1 1>&2 2>&3)
elif is_pitwo; then
OVERCLOCK=$(whiptail --menu "Choose overclock preset" 20 60 10 \
"None" "900MHz ARM, 250MHz core, 450MHz SDRAM, 0 overvolt" \
"High" "1000MHz ARM, 500MHz core, 500MHz SDRAM, 2 overvolt" \
3>&1 1>&2 2>&3)
fi
else
OVERCLOCK=$1
true
fi
if [ $? -eq 0 ]; then
case "$OVERCLOCK" in
None)
clear_overclock
;;
Modest)
set_overclock Modest 800 250 400 0
;;
Medium)
set_overclock Medium 900 250 450 2
;;
High)
if is_pione; then
set_overclock High 950 250 450 6
else
set_overclock High 1000 500 500 2
fi
;;
Turbo)
set_overclock Turbo 1000 500 600 6
;;
*)
whiptail --msgbox "Programmer error, unrecognised overclock preset" 20 60 2
return 1
;;
esac
ASK_TO_REBOOT=1
fi
}
set_overclock() {
set_config_var arm_freq $2 $CONFIG &&
set_config_var core_freq $3 $CONFIG &&
set_config_var sdram_freq $4 $CONFIG &&
set_config_var over_voltage $5 $CONFIG &&
if [ "$INTERACTIVE" = True ]; then
whiptail --msgbox "Set overclock to preset '$1'" 20 60 2
fi
}
clear_overclock () {
clear_config_var arm_freq $CONFIG &&
clear_config_var core_freq $CONFIG &&
clear_config_var sdram_freq $CONFIG &&
clear_config_var over_voltage $CONFIG &&
if [ "$INTERACTIVE" = True ]; then
whiptail --msgbox "Set overclock to preset 'None'" 20 60 2
fi
}
Any language using left-hand whitespace for syntax is ridiculous
Any DMs sent on Twitter will be answered next month.
Fake doctors - are all on my foes list.
Any requirement to use a crystal ball or mind reading will result in me ignoring your question.
Any DMs sent on Twitter will be answered next month.
Fake doctors - are all on my foes list.
Any requirement to use a crystal ball or mind reading will result in me ignoring your question.
Re: Default recommended pi 2 overclock settings
Thanks Doug, much appreciated.DougieLawson wrote: ↑Sat Jan 12, 2019 10:03 amExcept for the ones defined in raspi-config.W. H. Heydt wrote: ↑Sat Jan 12, 2019 1:44 amBy and large, the newer Pis don't have any "recommended" overclock settings.
That's got numbers for RPi2B. The 3B, 3B+ & 3A+ are set to the highest possible overclocking by default.Code: Select all
do_overclock() { if ! is_pione && ! is_pitwo; then whiptail --msgbox "This Pi cannot be overclocked." 20 60 2 return 1 fi if [ "$INTERACTIVE" = True ]; then whiptail --msgbox "\ Be aware that overclocking may reduce the lifetime of your Raspberry Pi. If overclocking at a certain level causes system instability, try a more modest overclock. Hold down shift during boot to temporarily disable overclock. See http://elinux.org/RPi_Overclocking for more information.\ " 20 70 1 if is_pione; then OVERCLOCK=$(whiptail --menu "Choose overclock preset" 20 60 10 \ "None" "700MHz ARM, 250MHz core, 400MHz SDRAM, 0 overvolt" \ "Modest" "800MHz ARM, 250MHz core, 400MHz SDRAM, 0 overvolt" \ "Medium" "900MHz ARM, 250MHz core, 450MHz SDRAM, 2 overvolt" \ "High" "950MHz ARM, 250MHz core, 450MHz SDRAM, 6 overvolt" \ "Turbo" "1000MHz ARM, 500MHz core, 600MHz SDRAM, 6 overvolt" \ 3>&1 1>&2 2>&3) elif is_pitwo; then OVERCLOCK=$(whiptail --menu "Choose overclock preset" 20 60 10 \ "None" "900MHz ARM, 250MHz core, 450MHz SDRAM, 0 overvolt" \ "High" "1000MHz ARM, 500MHz core, 500MHz SDRAM, 2 overvolt" \ 3>&1 1>&2 2>&3) fi else OVERCLOCK=$1 true fi if [ $? -eq 0 ]; then case "$OVERCLOCK" in None) clear_overclock ;; Modest) set_overclock Modest 800 250 400 0 ;; Medium) set_overclock Medium 900 250 450 2 ;; High) if is_pione; then set_overclock High 950 250 450 6 else set_overclock High 1000 500 500 2 fi ;; Turbo) set_overclock Turbo 1000 500 600 6 ;; *) whiptail --msgbox "Programmer error, unrecognised overclock preset" 20 60 2 return 1 ;; esac ASK_TO_REBOOT=1 fi } set_overclock() { set_config_var arm_freq $2 $CONFIG && set_config_var core_freq $3 $CONFIG && set_config_var sdram_freq $4 $CONFIG && set_config_var over_voltage $5 $CONFIG && if [ "$INTERACTIVE" = True ]; then whiptail --msgbox "Set overclock to preset '$1'" 20 60 2 fi } clear_overclock () { clear_config_var arm_freq $CONFIG && clear_config_var core_freq $CONFIG && clear_config_var sdram_freq $CONFIG && clear_config_var over_voltage $CONFIG && if [ "$INTERACTIVE" = True ]; then whiptail --msgbox "Set overclock to preset 'None'" 20 60 2 fi }