New Raspbian, Debian and Arch Linux images

Update: copied Alex’s summary of the changes to Raspbian from the comments into the post.

We’ve just posted updated Raspbian, Debian and Arch Linux images on the downloads page, all of which include our most recent firmware and kernel. Raspbian has the following significant changes:

  • Updated Scratch image (significant performance improvements).
  • Updated armv6-optimised Pixman library.
  • Updated armv6-optimised memxxx() functions.
  • Updated raspi-config with new layout, and new functionality (setting hostname and enabling camera support).
  • Native mmap support in the bcm2835 ALSA driver, and numerous other firmware changes; see commits to
  • The boot partition now has the label “boot”.
  • The Wayland/Weston preview from Collabra is installed and their apt repository is included as an apt source.


mark avatar

This may sound silly but do I need to re-download and reinstall the image to keep my Pi *completely* up to date. I’ve used rpi-update and apt-get dselect-upgrade, is this enough?

Markus avatar

Yeah, I’m wondering the same thing since I just reinstalled a sd card yesterday. Changelog or something would be useful.

asb avatar

`sudo apt-get update && sudo apt-get upgrade` will be enough.

asb avatar

I should add: there are some cases where a new image gets you some base configuration changes. It’s only minor things for this release, like won’t be on your /etc/apt/sources.list if you just apt-get update && apt-get upgrade.

Aurock avatar

Would ‘sudo apt-get dist-upgrade’ get any closer to the current downloadable version, or is it not going to update anything that ‘sudo apt-get upgrade’ wouldn’t?

Drone avatar

I would like an answer to this question too:

“Would ‘sudo apt-get dist-upgrade’ get any closer to the current downloadable version, or is it not going to update anything that ‘sudo apt-get upgrade’ wouldn’t?”

What is the difference?

Peter Aandahl avatar

I found this

So if you want to get as close as possible to a new fresh install it looks like sudo apt-get dist-upgrade is the best way to go.


audiologist avatar

No its not.

I tried apt-get update and apt-get diet-upgrade and rpi-update, and after reboot, still the alsa driver did not support memory-mapped io. Only installing a fresh image gave me that.

William H. Bell avatar

Hi Liz,

How far off is the Wayland image or the recovery boot partition?

Thanks and best regards,


The Raspberry Pi Guy avatar

Yeah, I second that!

How close is Wayland to official release? Can’t wait to get it!

The Raspberry Pi Guy

Joe avatar

The big issue with Wayland currently is there are no everyday window managers available. What you’ve seen in the demos is Weston, which is a reference compositor used to test Wayland’s features. It’s not suitable for every day usage at all.

There’s no menu, configuration is done via a messy ini (one [launcher] section per icon on the top bar) and X clients do not get the same window management functions as Wayland ones.

And I’ve tried running Openbox in Wayland, it doesn’t work ;)

I don’t think Raspberry Pi images will actually include Wayland until it’s actually usable beyond initial observations of awesomeness. Which it’s very useful for right now.

I can’t blimmin wait for a Wayland window manager. Or an Openbox port. Oh man…

Doug Taylor avatar

It seems to me that the first Wayland thing they should push out the door is the xWayland layer. Even if it’s less efficient than pure Weston, it sounds as if Weston+xWayland is a faster X server (due to graphics acceleration) than, and it’s basically a drop-in replacement for it, yes?

After that, then we can see about native Weston apps, which sound like they’d be very cool.

Jim avatar

Ditto on Wayland.

tzj avatar

Double ditto on that second, even if its just the current test version, it saves having to compile it ourselves. :D

asb avatar

Wayland/Weston provided by Collabora are preinstalled on this latest image with the apt source included by default. Daniel Stone is planning on further updating the package when he gets back from travelling next week (at which point it should include an easy launcher script).

Pi-man avatar

Great thanks !
Stupid question, if Wayland/Weston is included, how is it launched

Joe avatar

`weston-launch` will run a Weston session.

Pi-man avatar

Running 2013-05-25-wheezy
Command not found

koos avatar

I’ve compiled wayland/weston myself to get the new rpi speed-ups. Works fine but what looks missing is a wayland backend for X. At least it doesn’t work (“xserver crashing too fast: 256”) and, judging from the source code, `Xorg -wayland` is not supported.

asb avatar

The package has now been updated. If you are running this latest image, just `sudo apt-get update && sudo apt-get upgrade`. You will now have a `weston-launch` script that should easily give you a weston session. If using an older image, make sure you’re running recent firmware (updating via apt-get is new enough) and follow the instructions at

fbutler avatar

I’m getting the following when trying a sudo apt-get update after adding:
deb wheezy rpi
to /etc/apt/sources.list:

W: GPG error: wheezy Release:

The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY ED4BF9140C50B1C5

fbutler avatar

The package installs OK, but I can’t find the weston-launch script anywhere.

Ton van Overbeek avatar

Just did an `sudo apt-get update && sudo apt-get upgrade` but no weston-launch in ‘dpkg -L weston’. ‘dpkg -l weston’ still shows version 1.1.0-0rpi20130508. Not in the repository yet ???

asb avatar

Hmm, the new package definitely is in and is listed in I don’t have my pi to hand to check myself, but possibly there’s an issue with the repository.

Ton van Overbeek avatar

Noted that the ‘old’ package is ‘weston_1.1.0-0rpi2013050801_armhf.deb’ and the ‘new’ one is ‘weston_1.1.0-0rpi20130603_armhf.deb’. Since the ‘old’ one has a longer name (the extra ’01’) it might be considered younger by apt and friends.

asb avatar

Yes, that’s exactly the issue, can confirm by verifying `dpkg –compare-versions 1.1.0-0rpi20130603 gt 1.1.0-0rpi2013050801 &&
echo true || echo false` shows “false”. I’ve passed it on. For the time being you should be able to grab that .deb and install with sudo dpkg -i

asb avatar

The weston package is now updated and correctly versioned, and includes a weston launch script.

mihol avatar

Would it make sense to continue the conversation on forum thread below ?

Urra901109 avatar

Changelog maybe? It would be nice if it includes wayland

asb avatar

What’s changed (mostly applies to the Raspbian build):

Apologies in advance if this formats incorrectly

* Updated scratch image (performance improvements)

* Updated armv6 optimised pixman

* Updated armv6 optimised memset/memcpy

* Updated raspi-config with new layout, and new functionality like setting hostname and enabling camera support.

* Updated firmware (native mmap support in the bcm2835 ALSA driver, many other changes – see commits to

* The boot partition now has the label “boot”

* Wayland/Weston preview from Collabra is installed and their apt repository is included as an apt source

asb avatar

Oh, and rpi-update is there by default (along with git).

Pi-man avatar

downloads still has
is this the new release ?

asb avatar

Yes, I think the previous one we had up was generated the end of February.

Aurock avatar

Please consider adding some release notes or changelog when you put out a new version. Including it in an announcement post like this one would be good, or even better, add a link to the release notes on the download page.

Alex avatar

Does this include all of the USB fixes? (see the “USB redux” thread for details)
I currently have to use rpi-update to make the Pi work with a lot of USB devices? Is this no longer required?

eben avatar

Yes – it includes the latest USB fixes.

Gordon avatar

Sorry Eben,

No it doesn’t include the latest fiq_split fixes… I need a little more evidence from people that it’s all good (in other words isn’t going to be a regression..)

scot avatar

So if wayland is included how do we start it?

Peter Ryan avatar

Well, I totally don’t know what I’m doing… but….

$ mkdir /tmp/wayland
$ export XDG_RUNTIME_DIR=/tmp/wayland/
$ weston

However, for me, whilst I get a desktop appear, I can’t access anything because it is totally ignoring my overscan settings. I can’t even close it! I have to kill it from a separate SSH session. If I wait long enough though, I do get to see a wayland/weston locked session window… so that’s nice. I’ll marvel at that for a bit!

Pi-man avatar

Got it sort of working following your instructions
The only different thing I did was to chmod 0700 /tmp/wayland

No locked session window
I have overscan disabled

Desktop only has terminal working
That may be something to do with
/etc/weston/weston.ini launcher only having an entry for terminal

Seems very fast

szarpaj avatar

Updated armv6-optimised Pixman library.
Updated armv6-optimised memxxx() functions.

Can anyone elaborate on those two?

eben avatar

Sure. The ARMv6 instruction set includes some useful features for accelerating operations which access memory in a structured fashion (cache preloads) and/or perform operations on vectors of 8- or 16-bit quantities (media processing instructions). We’ve commissioned optimised versions of memcpy(), memmove() and memset(), and of a subset of the Pixman blitting functions, which take advantage of these facilities.

This translates directly (and transparently) into improved application performance, particularly for X and the various web browsers which use Pixman in their back ends.

szarpaj avatar

Thanks Eben.

Raspbian has some patches „repository” like Debian patches? I’m one of Gentoo users and it would be nice to also benefit from those improvements. (-: I’m not using X right now on my Raspberry Pi Gentoo, but maybe some day… or on another Pi (already got two of them).

asb avatar

I believe the armv6 pixman patches actually got accepted upstream in the most recent pixman release. You’ll certainly see them posted on the pixman mailing list. See for the memxxx operations and for pixman patches.

szarpaj avatar

I remember one implementation of newer memcpy (afair) from the formus that was used (/tested) with LD_PRELOAD. I suppose that those new, improved distros got it „built‑in” toolchain and not using a dirty workaround?

asb avatar

@szarpaj: sxtill a dirty workaround I’m afraid.

markyd avatar

I did think web browsing had got a lot snappier, was reading this thread to see if Wayland had been integrated somehow (now I know it is not) but the performance improvement most likely comes from here, exciting to know there is always more to come :-) the hard work is appreciated!

JxPond avatar

I was under the impression that xwayland acted as a shim between Wayland and say LXDE so things should be somewhat improved?

That is until there is a version of lxde that has a native backend for wayland proper.

don isenstadt avatar

I downloaded the new raspbian image but it will not work on my newer pi boards (512mb) .. it works fine on the old 256mb board.. any ideas?? I also updated and upgraded it but still no luck..strange

don isenstadt avatar

by “it will not work” I mean it will not boot.. I only get the red power light.. very strange

eben avatar

Hi Don
That’s not good. A couple of questions:

– where did you buy the board from?
– what color is the headphone jack?
– can you see what is written on top of the RAM package on top of 2835?

steven avatar

Works perfectly on my 512

don isenstadt avatar

what color is your headphone jack?
on the 512 that works for me it is black and my samgsung chip is 240.. the one that fails is 231 and a light blue jack .

don isenstadt avatar

board purchased from element 14.
headphone jack color is light blue
on to of the 2835 . 3 lines
samgsung 231
k4p4g324eb agc1
. gkf4979a
the raspian image
more info..
I have 2 512mb pis – the other one works the chip on that on is 240..

eben avatar

Can you clarify the last line: which string is replaced by “240” on the working Pi?

dliloch avatar

the number across from the SAMSUNG on the working board is 240.

dom avatar


Can you replace bootcode.bin with a version that works on the 512M board and report if it boots.

Pay special attention to what the green LED does if the boot fails.

dliloch avatar

ok.. will do the size of bootcode.bin is 17808 in both cases the one that does not work is may 25th the new one is may 29th.. in all cases when I do a uname -a I get
3.6.11+ #456

dliloch avatar

I just did this and it failed again. I do not get a act green light flash like I do on the image that works. again the only difference I could see on bootcode.bin was the date.. the size of the two files is identical.

eben avatar

Could you please mail me both bootcodes as an attachment to [email protected]?

dliloch avatar

I sent the two versions. let me know if you need anything further.

Paul Hanlon avatar

I updated and upgraded four days ago. It’s a while since I did that, and I have to say the performance improvements were staggering. Everything seems snappier, more responsive, and robust. Keep up the good work guys, because it is really good work.

Jonathan avatar

So, Is Weston not good on the the Pi at the moment?

Jim Manley avatar

It’s an alpha version at the moment, which means it isn’t a finished product by any means. Not all of the functionality has been completed for all of the features and even many of those that have been completed have not been tested and debugged to the point where they can be relied upon consistently. What has been provided can be thought of as a demonstration of the actual code that will largely form the final software (not a simulation or prototype). It’s good enough that people can try it out and provide feedback, but they shouldn’t expect to do anything critical that might get trashed when, not if, this early release has a problem.

For example, when I opened more than about a dozen terminal windows, the display started flashing at a show rate with the desktop squeezed to occupy the left side of the display, but when I closed some of the windows, everything went back to normal. In another case where I tried to resize a terminal window to occupy most of the screen by dragging a corner, the cursor wouldn’t change back to anything other than the resize “corner” icon. So, I couldn’t click on anything else to select it, and I wound up having to kill the weston process via a command line, but was able to restart and operate it again without any problem.

It’s also not well documented, so it’s not clear to a neophyte how to do anything other than open, drag-move, drag-resize, and execute commands within a terminal window. The developers are working on a script to help automate launching of the software and will undoubtedly be expanding the desktop to include everything that the current default Raspbian LXDE-based has. This will include the pop-up menu with access to all apps, multiple desktop selector, opened-window tabs, performance meter, clock, etc., in the toolbar. It will also include desktop icons for frequently-used programs, etc.

Apparently, the target for the essentially-finished code is this coming Fall, so figure at least 3 ~ 4 months. The more people who can find problems such as I described above (but unique and not already reported), the faster the bugs can be fixed. Dig in and help out – it’s a bit mucky down here at the moment, but the Sun is out and will help bake things into a more solidified state.

Jason Bramwell avatar

Today is also the first time I’ve seem Pidora on the downloads page.

vonProteus avatar

How can i update to latest version without reformatting card?

xXAzazelxX avatar

sudo apt-get update && sudo apt-get dist-upgrade

Antonio avatar

just do, sudo apt-get update and then sudo apt-get upgrade. May take some minutes, so don’t wait in front of it.

Panayiotis avatar

Will be an rdesktop alternative running on Wayland? Can’t wait to use a raspberry pi as thin client. Wayland looks promising

Do avatar

Agreed. i would like to know too

UtrechtPi avatar

Tip for Don and Eben: I had the same issue with 231 and blue plug Pi: new (may) raspbian wouldn’t boot; just red LED.
However: install of february raspbian would’t boot eiter(!), from that same SD-card. Tried DD of May-Raspbian-image to new SD-card (first set to FAT 32 using gparted). Then may Raspbian booted OK. So: first try other SD-card; May Raspbian may then boot OK for you, too.
(BTW: Thank you for the Pi and Raspbian).

tzj avatar

Thanks for the tip, not tried it on my ‘231’ 512 pi yet, but good to know.

dliloch avatar

thanks I will try another card I have lots of sd cards available .. I wonder what is causing this?

dliloch avatar

just amazing! It worked! I took a sandisk class 4 8gb card and reimaged it via dd with the may 25th image.. and it worked.. the card that failed was a emtec class 10 8gb card ..

Surfparadise avatar

Anyone have verify if this upgrade fix the analogue audio output problem with RASPBMC?


tokoservo avatar

Wow, fantastic. how about ubuntu? do you have Ubuntu for raspberry version?

ThePapanoob avatar

no ubuntu cant be used on a raspberry since the ubuntu arm needs a newer processor get an a10 device instead of a raspi!

PJC avatar

What happened to NOOBS? I figured it would have been included in this release.

PJC avatar

Never mind……I see it is a separate tool.

Martin Jarvis avatar

How does the new Raspbian version affect the use of Java of Raspberry Pi? Does it address the soft float/hard float problem?

Comments are closed