Raspberry Pi Safe Overclocking

31 Shares Google+ 28 Facebook 1 Twitter 1 LinkedIn 1 31 Shares ×

Safe/Stable Raspberry Pi Overclocking

Disclaimer: My recommendations are based on testing done with various configurations on two Raspberry Pi Model B version 2 boards. Both run Arch Linux ARM 24/7 without issue. Be warned, as with most hardware and software modifications, individual results may vary.

For the last month or two I’ve been playing around with overclocking my Raspberry Pi boards. I’m unbelievably obsessed with performance tuning. As such, even before starting various Pi projects, my main focus has been on squeezing-out noticeable performance gains without compromising stability. Today, I’d like to share my /boot/config.txt settings and hopefully get some feedback as to how they perform on your Raspberry Pi.

Raspberry Pi Safe Overclock – config.txt

Select a gpu_mem config option below based on if you are using a desktop manager vs just shell.

No GUI (eg. command line only)

With GUI (eg. OpenELEC, lxde, etc)

The reason I call these settings “safe” is because they don’t void the warranty and also I’ve had no crashes or reboots while using them. Refer to this page for explanations.

Benchmark Results

Here are my nbench benchmark results using the above settings on the Arch-WiPi image…

As a bonus, if you are just searching for modest speed improvements without any risk to hardware, then use these settings:

You can uncomment “arm_freq_min=400″, “core_freq_min=100″ and sdram_freq_min=300 if your Pi will be on but idle for extended periods (eg 24/7). This will allow it to use less resources when idle and as a result lower temperatures.

If for some reason something goes wrong and you can’t boot, don’t wipe your card. Instead, simply remove it from Pi > plug into your Linux computer > browse to /boot/config.txt to find and correct any errors/typos in config or revert changes.

Note that the *freq_min settings only work for setting below-default values. So for example to set a arm_freq_min higher than the default minimum of 700Mhz, one would have to VOID WARRANTY by adding  force_turbo=1. Don’t do this unless your project involves pushing the limits and make sure you have a plan in place to manage higher temps.



Looking for extreme speed?!

… Try my current config.txt settings for Openelec Xbmc…


[Blog image courtesy geektopia.es]

31 Shares Google+ 28 Facebook 1 Twitter 1 LinkedIn 1 31 Shares ×


No comments yet.

Leave a Reply

31 Shares Google+ 28 Facebook 1 Twitter 1 LinkedIn 1 31 Shares ×