Introducing turbo mode: up to 50% more performance for free

Since launch, we’ve supported overclocking and overvolting your Raspberry Pi by editing config.txt. Overvolting provided more overclocking headroom, but voided your warranty because we were concerned it would decrease the lifetime of the SoC; we set a sticky bit inside BCM2835 to allow us to spot boards which have been overvolted.

We’ve been doing a lot of work to understand the impact of voltage and temperature on lifetime, and are now able to offer a “turbo mode”, which dynamically enables overclock and overvolt under the control of a cpufreq driver, without affecting your warranty. We are happy that the combination of only applying turbo when busy, and limiting turbo when the BCM2835’s internal temperature reaches 85°C, means there will be no measurable reduction in the lifetime of your Raspberry Pi.

You can now choose from one of five overclock presets in raspi-config, the highest of which runs the ARM at 1GHz. The level of stable overclock you can achieve will depend on your specific Pi and on the quality of your power supply; we suggest that Quake 3 is a good stress test for checking if a particular level is completely stable. If you choose too high an overclock, your Pi may fail to boot, in which case holding down the shift key during boot up will disable the overclock for that boot, allowing you to select a lower level.

What does this mean? Comparing the new image with 1GHz turbo enabled, against the previous image at 700MHz, nbench reports 52% faster on integer, 64% faster on floating point and 55% faster on memory.

Previous image (2012-08-16-wheezy-raspbian):

BYTEmark* Native Mode Benchmark ver. 2 (10/95)
Index-split by Andrew D. Balsa (11/97)
Linux/Unix* port by Uwe F. Mayer (12/96,11/97)

TEST : Iterations/sec. : Old Index : New Index
 : : Pentium 90* : AMD K6/233*
NUMERIC SORT : 222.08 : 5.70 : 1.87
STRING SORT : 31.659 : 14.15 : 2.19
BITFIELD : 7.1294e+07 : 12.23 : 2.55
FP EMULATION : 44.808 : 21.50 : 4.96
FOURIER : 2188.1 : 2.49 : 1.40
ASSIGNMENT : 2.6545 : 10.10 : 2.62
IDEA : 671.41 : 10.27 : 3.05
HUFFMAN : 414.2 : 11.49 : 3.67
NEURAL NET : 2.9586 : 4.75 : 2.00
LU DECOMPOSITION : 77.374 : 4.01 : 2.89
=====================ORIGINAL BYTEMARK RESULTS=====================
Baseline (MSDOS*) : Pentium* 90, 256 KB L2-cache, ...
=========================LINUX DATA BELOW==========================
L2 Cache :
OS : Linux 3.1.9+
C compiler : arm-linux-gnueabihf-gcc
libc : static
Baseline (LINUX) : AMD K6/233*, 512 KB L2-cache, gcc, ..
* Trademarks are property of their respective holder.

New image, with 1GHz turbo enabled:

BYTEmark* Native Mode Benchmark ver. 2 (10/95)
Index-split by Andrew D. Balsa (11/97)
Linux/Unix* port by Uwe F. Mayer (12/96,11/97)

TEST : Iterations/sec. : Old Index : New Index
 : : Pentium 90* : AMD K6/233*
NUMERIC SORT : 340.8 : 8.74 : 2.87
STRING SORT : 47.52 : 21.23 : 3.29
BITFIELD : 1.05e+08 : 18.01 : 3.76
FP EMULATION : 66.32 : 31.82 : 7.34
FOURIER : 3431 : 3.90 : 2.19
ASSIGNMENT : 4.5311 : 17.24 : 4.47
IDEA : 991.67 : 15.17 : 4.50
HUFFMAN : 615.08 : 17.06 : 5.45
NEURAL NET : 4.76 : 7.65 : 3.22
LU DECOMPOSITION : 135.12 : 7.00 : 5.05
=====================ORIGINAL BYTEMARK RESULTS=====================
Baseline (MSDOS*) : Pentium* 90, 256 KB L2-cache, ...
=========================LINUX DATA BELOW==========================
L2 Cache :
OS : Linux 3.2.27+
C compiler : arm-linux-gnueabihf-gcc
libc : static
Baseline (LINUX) : AMD K6/233*, 512 KB L2-cache, gcc, ..
* Trademarks are property of their respective holder.

Other changes to the latest firmware include:

Temperature and frequency widgets

You can enable a core temperature widget for the lxde taskbar to see how close to 85°C you get (in the UK, it’s not very), and a cpufreq widget that will show the current ARM frequency when you hover over it. See here for more details.

USB interrupt rate reduction

We have enabled Gordon’s “FIQ Fix” in the USB driver, which reduces the USB interrupt rate, improving general performance by about 10%.

WiFi is now supported out of the box

If your WiFi driver is supported by the default linux tree, or is based on the popular RTL8188CUS chipset, then WiFi should work out of the box. Boot the image with the WiFi dongle plugged in (a powered hub is recommended). Run startx and select “WiFi Config”. You can scan for wireless networks and enter your wireless password and connect from the GUI. No need to install additional packages or scripts.

Improved analogue audio

Analogue audio quality has been improved.

Extra software installed by default

SmartSim and PenguinsPuzzle are pre-installed.

If you are using an older wheezy image, you can upgrade: “sudo apt-get update && sudo apt-get upgrade” will get almost all these improvements.

Thanks to MrEngman for his amazing work supporting users with various WiFi dongle, Dorian Peake for the cpufreq and temperature drivers, and Dmitry Dudkin for his work on the USB and SD card drivers.

Alex has started a forum thread for further discussion – pile in!


Steve avatar

Excellent news! This should certainly come in handy for those really pushing the pi to its limits.

Any word on when/if additional CODEC support would be dropping? T

Steve avatar

Oh dear, I appear to have lost half of my comment. It basically said that some people who had been watching GIT had noticed potentially more to come down the line?

James avatar

I knew I shouldn’t have thrown that liquid nitrogen out! dang…

Maarten Baert avatar

Great! Does ‘Improved analog audio’ mean you’ve completely solved the distortion (‘noise’ or ‘clicking’) issues?

Interesting how you can get a 64% performance increase for floating-point after increasing the clock rate by 43% – how is that possible?

Tom avatar


eben avatar

The USB fix is a major contributor. Also, the system bus frequency in turbo mode is doubled to 500MHz.

dom avatar

When in turbo mode, the GPU core (which includes the ARM’s L2 cache) and the SDRAM increase, so you can get more benefit than just the ARM clock boost.

Chris Evans avatar

I wondered that at first but the figures also include the USB Interrupt fix which I believe reduces its CPU load from 20% to 2%. This on its own gives about a 23% speed improvement

Mortimer avatar

If you are using an older wheezy image, you can upgrade: “sudo apt-get update && sudo apt-get upgrade” will get almost all these improvements.

andy baxter avatar

As far as I know, you should use “sudo apt-get update && sudo apt-get dist-upgrade” for upgrading between distributions. You may also need to change your /etc/apt/sources.list first – I’m not exactly sure how the raspberry pi handles this. See “man apt-get” and “” for more info.

asb avatar

See for some guidance on upgrading an older image.

Mortimer avatar

Sorry, what I meant to say is the text says quote : “If you are using an older wheezy image, you can upgrade: “sudo apt-get update && sudo apt-get upgrade” will get almost all these improvements.”. So “almost all”, which begs the question; What will be missed out by upgrading as opposed to any other method of getting these features?

asb avatar

Just the usual set of minor tweaks (mostly fixes) to the base image that get integrated over time. The one you might care about is easy to use wifi config. See my forum post:

Horst avatar

The performance increase is very impressive.

Is there any possibility to enable this dynamic overclocking and overvolting on the archlinux image, too?

Probably editing the config.txt is not sufficient. Which kernel modules are necessary?

asb avatar

I’m not sure if Arch is using the kernel builds from or not. If it is, then we build cpufreq in to the kernel. You just need to have something in userspace switch from the “powersave” governor to “ondemand” (we default to powersave to allow for cpufreq to be disabled if you hold down shift during boot, which is something we detect in an init script). Updating to the latest kernel build and adding `echo “ondemand” > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor` to your /etc/rc.local would be sufficient I think.

Ben Morris avatar

Am I right in saying that rc.local is executed after all other init scripts and thus this won’t improve boot times?

Tom avatar

Thanks for all your hard work!

I couldn’t pass the opportunity to ask two “woe is me” questions:

1) I have the 2012-08-16-wheezy-raspbian image. If I do those apt-get updates, will it include the ‘turbo’ mode?

2) Will the USB driver bug-fix also fix some of the wireless keyboard issues (in my case the Microsoft 800 keyboard with sticky keys problem, but a power consumption lower than 100 mA)?

Keep up the good work!

asb avatar

There have been a number of USB fixes integrated. Either try this image, or update the firmware packages on your existing Raspbian install and give it a go. See for more info on upgrading.

Tozzi avatar

How can this be implemented for us running a XBMC image? Like xbian, openelec or raspbmc?

dom avatar

Wait for a new image. Sam and Stephan should be supporting the new overclock scheme.

Tozzi avatar

There is no way to do this by yourself? :) If I don’t wanna wait.

The Mole avatar

Yes of course there is. But if you need to ask the question then it’ll probably take you longer than waiting! :-)

But learning is good in itself, so the basic steps would be to build yourself the new kernel version, tweak the init scripts and include that in your XBMC build…

Mark Browning avatar

Well, xbian is based on raspbian, so apt-get update && apt-get upgrade would probably still work. The other two are custom filesystems, though.

Reme avatar

What about the Arch users?

Ulrich avatar

that are very good news. Thanks a lot for all your work on making the RasPi even more awesome than it already is.

You wrote that by upgrading with apt we “will get almost all these improvements”. Can you elaborate what we will miss out on?

Steve avatar

Any plans to update the soft float version to match this? Looks like only the hard float version has been updated on the download page.

asb avatar

Yes, a soft float version will go up in the next couple of days. I have updated the firmware packages in the repo, so you actually should be able to follow the first part of the instructions at to update your firmware and configure overclock in raspi-config.

Steve avatar

Awesome, thanks, I was planning on re-installing mine back to soft-float in the next few days (need Mono support) so that’s great timing :-)

pd avatar


Ralph Corderoy avatar

Hi Eben, it may not matter in this case but I wonder if it’s worth getting newcomers used to `apt-get dist-upgrade’ rather than plain `upgrade’, it may be more what they need in the general case. Cheers, Ralph.

Salamander avatar

Many thanks to everybody involved in this achievements. Please, could we have a list of the five overclock presets in raspi-config? Will other distros (like OpenELEC) take advantage of all this speed improvements just upgrading to latest firmware?

asb avatar

“None” “700MHz ARM, 250MHz core, 400MHz SDRAM, 0 overvolt”
“Modest” “800MHz ARM, 300MHz core, 400MHz SDRAM, 0 overvolt”
“Medium” “900MHz ARM, 333MHz core, 450MHz SDRAM, 2 overvolt”
“High” “950MHz ARM, 450MHz core, 450MHz SDRAM, 6 overvolt”
“Turbo” “1000MHz ARM, 500MHz core, 500MHz SDRAM, 6 overvolt”

Other distros just need to add some support for configuring the cpufreq driver.

Salamander avatar

Thanks for the info.
The funny thing is that just yesterday I overclocked my PI for the first time ;)
arm_freq=900, core_freq=450, sdram_freq=500, no overvolt
Just tried it with OpenELEC. Everything fine, noticed a big improvement. Are the overclocking settings at config.txt still valid or are they superseded by another method?

asb avatar

Yes they’re valid. raspi-config is just making edits to config.txt for you. Though in recent firmware, without force_turbo=1 (which would set your warranty bit), the settings only take effect when the cpufreq driver switches the clocks. See for more info

Salamander avatar

I assume that setting force_turbo=1 does not automatically sets the warranty bit. You would also need to over-volt in order to void your warranty. Am I wrong?

Salamander avatar

On the other hand, what happens if arm_freq=arm_freq_min, core_freq=core_freq_min, and so on. This would be equivalent to force_turbo=1 but would not void the warranty. Just putting hacking hat on ;)

dom avatar

Ah – you can’t bring the min values above stock, so that foils that plan. force_turbo=1 doesn’t set warranty bit on its own – only in conjunction with over_volatage>0.

Salamander avatar

Good to know, thanks Dom. Where is that documented? At the wiki I just can see that the ‘*_min’ options have a default value, but no reference to a max one.

edgicat avatar

Great info thanks. One quick question. From what I’ve read If I want to overclock my PI to 1Ghz then I need add another 6 volts to the existing 5volt supply, thus 11volts? I can not find an 11volt PSU but i can find plenty of 12volt psu’s. Will this 1 extra volt damage to my PI or affecting the warranty?

dom avatar

Not sure if you are serious, but no. 5V is fine. The over_voltage setting is handled by the GPU, who’s default voltage is 1.2V, and with over_voltage=6 it is increased to 1.35V.

Keep your 11V power supplies away from the Pi.

dc avatar

lol. genius+ humour = made-my-day

sooth avatar



Chris Evans avatar

I see after the upgrade the kernel is still 3.1.9 are the I2C drivers & RTC included?
Or do we have to wait for the 3.2 kernel and any idea when that will appear?

dom avatar

The kernel is 3.2.27. I2C and RTC drivers are included.

Chris Evans avatar

Doh! Sorry I looked at the wrong benchmark table.

asb avatar

We’re on 3.2.x now and have been for some time.

Tiago avatar

Is the GPU overclocked also?

dom avatar

The GPU core clock is boosted when in turbo mode (and the SDRAM clock) as that improves the ARM performance (it speeds up the ARM’s bus and L2 cache).
We are not currently boosting the 3D and H264 clocks, as they are typically never the bottleneck in the system, and when they are busy is not necessarily correlated with when the ARM is busy, although I’m still experimenting with this behaviour.

Matt Hawkins avatar

Excellent. The Raspberry Pi is the device that just keeps on giving!

Wish I hadn’t spent last night getting my new WiFi dongle working. As ever, thanks to the Foundation for the behind the scenes work.

Katzohki avatar

Funny, I was preoccupied with the same task last night. :3

shang avatar

Same here… spent hours the night before!

Angel Padilla avatar

Brilliant work!
As far as the temperature goes, I think if you place a home-made small heatsink might do the quick. I remove one from a graphic adapter and cut to size to fit over the RPi chip’s.
Thanks to everyone for your hard work and contributing to the foundation.

JamesH avatar

I believe all the testing has been done without heatsinks. Although it might mean turbo mode can stay on for longer in more extreme conditions, unlikely to occur in the UK as an example.

Kris avatar

This is brilliant. I’ve set mine to turbo and I’m currently compiling pulse eight cec (as a test).

I can see the CPU flicking between 700mhz and 1ghz, with a temperature of about 68 degrees :)

If anyone’s interested, I made a very simple bash script to show the current stats:

cat /boot/config.txt | grep _freq
echo “”

echo “Temperature: ”
cat /sys/class/thermal/thermal_zone0/temp
echo “”

echo “CPU Scaling: ”
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq

Kris avatar

its probably worth adding

cat /boot/config.txt | grep over_voltage

under the first line :)

David avatar

Won’t all this polling the performance slow down your Pi?

Jongoleur avatar

Definitely a lot more zipppppppp!!!!!!

With overclocking set to the step below full Turbo, the system is fast and responsive; apart from an initial surge to full CPU loading when opening Midori, the rapid fallback to rippling peaks is impressive (I had spent too much time watching that graph fully blocked,…). The CPU temp monitor is something else to worry about, but at the moment its just tipping 49C so there’s nothing to worry about!

(Early production RasPi in a Pibow case, and RS psu)

jongoleur avatar

Oops…. Spoke too soon!

I just bought a colourful USB keyboard to go with the Pibow case and it doesn’t seem to like the increased clockspeed; sometimes keys don’t register, other times a character will start repeatinggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggggg ;-)

Changing the speed setting from “high” to “modest” seems to have cured this behaviour, so I still benefit from an improved speed though not as much as I would have liked.

When I get around to it, I’ll try “medium”….

Then I’ll go on to have fun with a wireless dongle.


q avatar

it’s your power supply

Stewart Watkiss avatar

Watch out the tax man will now be adding the pasty tax on the hot pi :-)

eben avatar

Knew we should have called it Raspberry Cake…

Adam avatar

The Raspberry Cake is a lie…

gamerb avatar

Wait, so how do you activate the turbo on the new image?

asb avatar

Use raspi-config (which is opened on first boot, or get to it later with ‘sudo raspi-config’).

gamerb avatar


JBeale avatar

Great news! Just curious how much this affects the power used by the device, is it still about 550 mA overall when running hard, or does Turbo Mode cause a significant increase in current draw? (not accounting for anything external)

dom avatar

You might expect the current draw to increase with performance (probably a bit less as there are fixed power costs), so you might expect the power to increase from ~500mA to ~750mA (plus whatever USB devices are connected).

Jim Manley avatar

For anyone who was wondering why I posted so vociferously very early on when Pi boards started shipping to use at the very least a 1 amp power adapter, and a 2 amp model would be much better, now you know why. It was not because you would ever reach 2 amps under normal circumstances, but to provide plenty of headroom during power consumption bursts above lower average steady-state current, plus USB device demand (especially now that F2 and F3 are gone on newer boards).

These improvements are all extremely gratefully appreciated by those of us working at the bleeding edge of the board’s capabilities. Now, if only we could have on-the-fly RAM compression/decompression that costs nothing in the way of CPU/GPU performance to effectively expand that 256 MB RAM ceiling … :D

nicknml avatar

I never heard of RAM compression/decompression, sounds interesting.

Mark avatar

Back in the days of 3/486s there was a MSR called Stacker(if I remember correctly) which claimed to boost your lowly 2/4MB machine to 2x that. It slowed down the system but gave you a pretty constant 25% increase. I’m sure offloading the compression to the GPU it would be smoother than a 4a6 25MHz SX:

Christmas avatar

Read (zRam) for compressed swap in ram.

Remi Gillig avatar

“Analogue audio quality has been improved.”

Does this affect the output audio jack at all? The audio quality from it was really awful and it made me stop coding when I realized that…

dom avatar

Yes. quality is improved from the analogue jack. Still not CD, but improved. Give it a try.

bbandi avatar

I’m currently testing it. Damn, it’s much better (using it with mpd). First, there’s no *click* between the songs, and when starting/stopping it (Although there’s a quiet low frequency boom, but it’s acceptable for me – actually, it reminds me when my turntable raises the pickup on the end of a record). The audo qaulity is also seems much better, but I didn’t do any blind test (I heard the high freq noise on the previous version, now I have to search it with volume/treble settings).
The only (quite little) problem for me is the badly chosed scale for the volume control (it seems linear instead of logarithmical)

benjamin avatar

its it just me or is cpufreq driver not working anymore ?
I’ve updated my older image and now cpu always stays at 700mhz no matter what load ….

asb avatar

It’s because we default to the powersave governor (i.e. no overclock), which allows us to implement the “hold shift to disable overclock” functionality. If you use raspi-config to set an overclock preset once, then an appropriate init script will be generated. Or else add echo “ondemand” > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor to /etc/rc.local

juanRIOT avatar

Good things come to those who wait, I say. Who has voided warranty because they’ve overclocked their Raspberry Pi? Not me :-D

Arsham avatar

Thanks so much for the continuous and awesome support! I’m so proud to be a Raspberry Pi owner and you guys continue to push the envelope on what these already amazing devices can do. I’ll be ordering many more soon (I am hoping a revision will come out with a power source switch that lets me choose USB or 5v POE).

Andreas Eriksson avatar

Many thanks. Very neat to see performance improvement of this kind.

normal avatar

Where can i get that benchmark tool?

Andrew avatar

This little cutie just keeps getting better and better and better and better and better…

Thaks to all involved!

exx avatar

What’s the tool you used for benchmarks? I want to try my system before and after…

normal avatar

I think the wiki page for overclocking needs to be edited to say that setting over_voltage more than 6 voids warranty as opposed to setting it more than 0. raspi_config sets over_voltage=6 but this post says that using turbo doesn’t void the warranty?

dom avatar

Actually setting overvolt to 8 won’t void warranty, but you will be restricted to 6, unless you set force_turbo.
This describes the exact formula for setting warranty bit:

Alex Chamberlain avatar

Well done everyone.

Is it really a good idea to include more software? Anyone up for developing a piece of software that can bootstrap an SD card from a “recipe” of packages etc rather than having to download 2GB images? We could cut down on bandwidth and it should speed up the write to the SD card a bit too.

Bryan Crotaz avatar

Until Model A comes along without Ethernet…

Rob Beard avatar

There is already such an image available…

Create a small FAT partition (a 32MB FAT16 partition seemed to work for me) and boot it. It’ll take you through an installation process which is similar to a Debian network install. Takes a while (even on a Virgin 30Mbit cable connection) but you can create a minimum base install to add to it (and you can select what optional things you want to install like X, SSH server, file sharing/printing support etc).

I’d guess though going by the date, you would need to manually make the changes to the image or wait until an updated version is released (could be wrong of course, maybe it downloads the updated kernel etc when it downloads the rest of the packages from the Raspbian mirror)


Temia Eszteri avatar

A quick question regarding heat dissipation, in that regard: is there any thermal transfer material to channel the heat from the CPU to the memory chip over it, therefore allowing one to use a heatsink on the memory to cool them both, or is the heat bottled up inside the space under the memory?

mahjongg avatar

Its a package on package device, with a massive amount of interconnects, so there are so many solder balls between the two packages that effectively the thermal resistance between the two packages is very low.

Temia Eszteri avatar

Okay, works enough for me and my $3 RAM heatsinks. Now I just need to wait for my RPi to actually arrive…

Iso9660 avatar

Amazing!!! Currently RPI is offering much better support in only 9 months than other projects have given in three years!!! The only I can say is AMAZING!!!

omenie avatar

I shall be trying this out in the morning. Brilliant, and in particular the USB piece in conjunction with the clock hike is great news.

John Franks avatar

Brilliant, just downloaded the latest kernal and installed an Edimax EW-7811Un wireless adapter, with out a problem. Had been having difficulties before getting it up and running. Thank you guys for all your hard work, it is really appreciated.

Albert avatar

Where can I download the image allowing me this 50% extra-speed for free with overclocking and overvolting that down’t void my warranty? Dows this new method void my warranty? Thanks!

tzj avatar

and then ‘sudo raspi-config’

Marc avatar

So I wonder if they will overclock the 64 core super pi stack?

Paito Anderson avatar

How can one run BYTEmark* aka nbench on their raspberry pi?

Kenneth avatar

Wow, the turbo is great…….. working happily with that.

OMightyBuggy avatar

Is there going to be an updated image?

My Rasp Pi currently is not online and I want to try the new features. :)

asb avatar

There is an updated image, check the download page.

Mark Janney avatar

Great work on the new image!
I have been using a KVM switch to change between my “office” keyboard and mouse and the Pi but when in the GUI other USB devices and internet stopped working.
All good now.

ChrisM avatar

Why use a KVM? Just run Synergy on your PC and the Pi, and you can move your mouse off the side of your PC screen and onto the Pi screen (and the keyboard input follows it).

Thomas avatar

The update looks truly amazing!

Simon avatar

The improvement in analogue audio is tremendous. Before the sound signal was low and hissy but now it’s much louder and clearer – here’s a couple of examples of how it sounds now &

BSDude avatar

Can we just download the firmware, the three boot files and overwrite existing ones (using OpenELEC RPi) and this will just update the firmware or is this some how specific to a distro or custom compiled kernel?

AndrewS avatar

Fantastic news. It’s great to see all the progress that the Foundation and Broadcom guys (and other volunteers) are making to the Raspi’s software stack :-)
First the armhf build, and now turbo mode… just goes to show how important software optimisation is on low-end hardware.

Kenneth avatar

A lot of thaks!

We were promised robots avatar

Sweet! Great work.

Cavan Orwell avatar

Tremendous upgrade, thank you all concerned. However, could I be doing something wrong as the Omxplayer no longer seems to want to work, whereas previously it performed faultlessly from the command prompt. I have put the MPEG2 key in the new config.txt, but all I get on trying to play a video is ‘have a nice day’ ! Any thoughts anyone on what is happening? Are there further configurations I need to make?

ftaurino avatar

very good news. the only missing thing is the x11 accelerated driver… ;)

liz avatar

We’re working on it. Nothing’s been parked; it’s just that some things take longer than others!

Nathan avatar

Would this allow us to underclock the Pi in order save on power?

cave avatar

I don’t think so.
The bottleneck for energy savings on the board are the Linear Voltage regulators.

The RG2 Part on the PCB consumes very much energy.

Switch them to switching regulators and consumption will go down ~33%

Angel Genchev avatar

Thanks !
I`m going to implement 2 cheap switching regulators with 2x IC MC34063 on separate PCB
5V -> 3.3V & 5V -> 1.8V

David avatar

This would require you to maintain a constant external temperature of 85 degrees C, which is not possible in the UK… :-)

Vicary avatar

Eben you’re really a badass… impress me again and I’ll have a man crush that I don’t want. :(

Jarrod avatar

I’ve posted the steps I went through to get this working on my Raspberry Pi, as well as a very preliminary “benchmark” outlining the differences between the 5 overclocking preset levels. :)

Tche_leao avatar

Wow!!!!Great news!!….Thanks for the good work!!!!

Des avatar

Hate being a newbie, but since I am brand-new to this, I would like to ask three simple questions.

1. I used the “Windows”/xbmc variant, so I could image my SD card from my Win7 desktop. Will an auto-update load these new code changes, or are they still pending for my build?

2. I want badly to get wifi working, if 1. above is “yes”, how do I get the wifi upgrades?

3. I don’t know how to get into terminal from xmbc…is there a tutorial?

Vinicius Tinti avatar

Raspberry Pi rocks.

How about updating the FAQ?

Vinicius Tinti avatar


Andrew avatar

Works as described.

AJ avatar

Really great job guys!!! The performance improved a lot and now I’m not afraid to burn my Pi… I could see a great improvement also using the XBMC installed in my Raspbian, that now is more fluid and it respond fast to the commands! The only real problem that I see is the RAM now, especially if you want to use the XBMC and as I wrote you need to dedicate 128MB of RAM to the video card because you have really too few RAM available and the programs are opening really slowly (and you can’t really surf with Chormium). Is there any possibility to expand in the next version the RAM to at least 512MB (with a small increase of the prize)? I think will make this microcomputer just perfect!

AJ avatar

ops, I wanted to say “as I read” instead of “as I wrote”

Kimbo avatar

Superduper! Thanks guys… I’ll test it soon.

Does the update come with the update in raspbmc?
How do I notice that it has updated my system?

James avatar

I have 2012-07-15-wheezy-raspbian and a rev 1 board. I have updated but i can’t find turbo mode. Is it there and if so where is it?

js avatar

Hm, for me, the turbo mode is slower than overclocking the RPi to 900 MHz overclocking. It seems that the on-demand governor is the problem: Even when compiling AND surfing at the same time, it often keeps 700 MHz and eventually switched to 1000, but then still switches back to 700 often, even though the temperature does is only less than 50 degrees. Will switching to the performance governor void my warranty? Does the performance governor kill a fuse bit? Or can I just use it if it works better for me?

js avatar

I meant overclocking to 900 MHz without overvolting, sorry.

liz avatar

You can use the force turbo option. As long as you don’t select overvolt that won’t set your warranty bit, but it’ll give you the overclock.

js avatar

Ok, good to know.

But what if I only want the performance temporarily? For example, when compiling, the ondemand governor sometimes swtiches back to 700 MHz. If I would switch the governor to performance before compilation and back to ondemand afterwards, this can’t happen. But will using the performance governor void my warranty, even if just for a short time?

liz avatar

Using the performance governor does not void your warranty at all.

js avatar

Nice! This is interesting, because this effectively would be the same as forcing turbo mode, so one would not expect that one voids the warranty and the other does not :). Will it stay this way, or is it possible that with some update suddenly the performance governor will void the warranty?

jirij avatar

try using “conservative” cpufreq governor, “ondemand” is more tailored to Intel CPUsaudioaudio

Brian LaPolt avatar

Boozst! Turbo for the car, turbo for the motorcycle, turbo for ICEs everywhere (Internal combustion engine), turbo for my Intel I7, but best of all Turbo Pi for desert!

Thank you to all for supporting and implementing this feature. The usability and speed is easily 100% better. Now I don’t have to permanently overclock my pi, it “just works”. Best $35 I’ve ever spent. Except that it’s gotten me to spend another $200 on quadcopter parts…. :P

Matthew Simpson avatar

Turbo mode seems like a good idea but I had trouble getting Quake 3 running on Raspbian with it enabled (level 5). The game kept crashing when I started a level. I built from source by the way.

Jon avatar

Hey my Pi has an uptime of 7 days (4 days better than previous best). Result! Thanks team Raspberry!

Lawrence Crumb avatar

Downloaded the update. Tried to put the image on a SD with my desktop and it seems that my Sony card reader would not work. I have a SD card slot on my Lenovo ThinkPad R500 and using Win32imagewriter I was able to write a SD card that did not update properly on the PI. It worked.
Also I was able to get rid of my ethernet cable as as my RTL8192 dongle worked and i am connected to my home WiFi network.

Kevin avatar

Question: Is it possible to see the status of the Warranty (sticky) Bit?

cave avatar

cat /proc/cpuinfo

in the line revision it should look like this
Revision: 0002

with stickybit it looks like
Revision: 1000002

RedPenguin avatar

What happens to the warranty if you used something like Raspbmc or even Rasbian (who actually admitted it and apologized) and do force_turbo=1 without many users even knowing it?

RedPenguin avatar

My apologizes it was XBian who admitted to it, but I checked Raspbmc RC5 and it appears to also have it enabled.

RPiLover avatar

Any chance you officially support a BSD (Net or Free)? It would be nice to use RPi without Linux already!

Angel Genchev avatar

Turbo is a nice feature, but i wonder if it`s possible to extend it in the opposite direction e.t. a mode i`d call “extended dynamic clocking” to allow for both turbo and deeper power saving when idling at lower than 700Mhz – for example 200Mhz. Useful when someone is just listening an mp3 on battery power.

Thomas Welsch avatar

Is underclocking also possible ?
Would this save power ?

Nick avatar

Is there a command I can run to see if the overclocking has worked and the speed?

Claudio Castro avatar

Hi everybody,

Im using my pi with raspbian + xbmc

Linux raspberrypi 3.6.11+ #538 PREEMPT Fri Aug 30 20:42:08 BST 2013 armv6l GNU/Linux

I tryed to set the overclocking option to TURBO using raspi-config, but it doesn’t boot after reboot, and even worst hold shift doesn’t seem to have any effect, finally I had to put the SD card on another computer and edit config.txt to comment out all the overclocking options.


clive avatar

Hi Claudio — you really need to ask in the forums, this thread is kind of old and sleepy.

Comments are closed