Apart from being somewhat slow, one of the downsides of the original Raspberry Pi SoC was that it had an old ARM11 core which implements the ARMv6 architecture. This was particularly unfortunate as most common distributions (Debian, Ubuntu, Fedora, etc) standardized on the ARMv7-A architecture as a minimum for their ARM hardfloat ports. Which is one of the reasons for Raspbian and the various other RPI specific distributions.

Happily, with the new Raspberry Pi 2 using Cortex-A7 Cores (which implement the ARMv7-A architecture) this issue is out of the way, which means that a a standard Debian hardfloat userland will run just fine. So the obvious first thing to do when an RPI 2 appeared on my desk was to put together a quick Debian Jessie image for it.

The result of which can be found at: https://images.collabora.co.uk/rpi2/

Login as root with password debian (Obviously do change the password and create a normal user after booting). The image is 3G, so should fit on any SD card marketed as 4G or bigger. Using bmap-tools for flashing is recommended, otherwise you'll be waiting for 2.5G of zeros to be written to the card, which tends to be rather boring. Note that the image is really basic and will just get you to a login prompt on either serial or hdmi, batteries are very much not included, but can be apt-getted :).

Technically, this image is simply a Debian Jessie debootstrap with a extra packages for hardware support. Unlike Raspbian the first partition (which contains the firmware & kernel files to boot the system) is mounted on /boot/firmware rather then on /boot. This is because the VideoCore expects the first partition to be a FAT filesystem, but mounting FAT on /boot really doesn't work right on Debian systems as it contains files managed by dpkg (e.g. the kernel package) which requires a POSIX compatible filesystem. Essentially the same reason why Debian is using /boot/efi for the ESP partition on Intel systems rather the mounting it on /boot directly.

For reference, the RPI2 specific packages in this image are from https://repositories.collabora.co.uk/debian/ in the jessie distribution and rpi2 component (this repository is enabled by default on the image). The relevant packages there are:

  • linux: Current 3.18 based package from Debian experimental (3.18.5-1~exp1 at the time of this writing) with a stack of patches on top from the raspberrypi github repository and tweaked to build an rpi2 flavour as the patchset isn't multiplatform capable :(
  • raspberrypi-firmware-nokernel: Firmware package and misc libraries packages taken from Raspbian, with a slight tweak to install in /boot/firmware rather then /boot.
  • flash-kernel: Current flash-kernel package from debian experimental, with a small addition to detect the RPI 2 and "flash" the kernel to /boot/firmware/kernel7.img (which is what the GPU will try to boot on this board).

For the future, it would be nice to see the Raspberry Pi 2 support out of the box on Debian. For that to happen, the most important thing would be to have some mainline kernel support for this board (supporting multiplatform!) so it can be build as part of debians armmp kernel flavour. And ideally, having the firmware load a bootloader (such as u-boot) rather than a kernel directly to allow for a much more flexible boot sequence and support for using an initramfs (u-boot has some support for the original Raspberry Pi, so adding Raspberry Pi 2 support should hopefully not be too tricky)

Update: An updated image (20150705) is available with the latest packages from Jessie and a GPG key that's not expired :).

I'm really pleased to see that you're trying to integrate the RPi hardware support with Debian's packages. I'm especially impressed you've already rebased onto 3.18.5.
Comment by Ben Hutchings Tue Feb 3 17:40:43 2015
You just answered all my questions - before my Pi2 turns up :D
Comment by Andy Cater Tue Feb 3 19:28:27 2015

Thank you for your work!

Will this RPi2 support get upstream into Debian Jessie? That would be awesome.

Comment by Nickolai Leschov Tue Feb 3 19:55:16 2015
Do you have scripts that generated the image, in case we wanted to reproduce it/add more packages?
Comment by Samat Jain Wed Feb 4 05:01:16 2015

Ben, I can't take the credit for it being based on 3.18.x already, the raspberry pi github was already 3.18.5 based so i just had to add those patches to the Debian kernel package and tweak it a tiny bit.

Nickolai, Debian Jessie is in hard freeze even if these packages were acceptable for Debian (which at least the kernel one is not imho), it is too late for Jessie. Hopefully for Stretch RPI2 will be supported out of the box.

Samat, No i didn't bother writing a script to generate the image. It's rather simple though:

  • debootstrap a standard debian armhf chroot
  • add the repository mentioned in the post and install the packages mentioned there
  • add config.txt and cmdline.txt in /boot/firmware from the standard rpi image
  • create an image file starting with a fat partition (and put the content from /boot/firmware on it) and an ex4 partition and put every else on it
  • update etc/fstab to mount the two partitions on respectively /boot/firmware and /
  • set a password for root (or alterntively create a new user with sudo rights and install sudo)
  • done!

At some point this will probably get automated, but it wasn't important for me now.

Comment by sjoerd Wed Feb 4 09:30:45 2015

Hi, is there a way to get the serial for the license key? I tried cat /proc/cpuinfo, but the command returned just "Serial : 0000000000000000". THX

Comment by motz_e Wed Feb 4 14:54:01 2015
Hi. Justed wanted to say thank you for this quick "up-and-running" solution! Nice work! :-)
Comment by jsl123 Wed Feb 4 15:29:39 2015

Can I use win32diskimager http://win32diskimager.sourceforge.net to install the image? Not sure how to flash a .gz image in a WIN8.1 ?

Comment by skywave Wed Feb 4 21:25:18 2015
Unzip the .gz first? Then use the Win32Imager.
Comment by Anonymous Thu Feb 5 16:16:44 2015

Great work, boots super fast, thx a lot!

Btw, does it include the videocore drivers for X or even better xwayland?

Comment by OliD Thu Feb 5 16:36:45 2015
Hi, I wanted to thank you very much for this release. I got my Pi2 yesterday and for some reason official Ubuntu Snappy does not work for me apart from logging from console. So I searched around and downloaded your image and it works and it is PRETTY DAMN FAST!!! Thank you so much for it. I would love if this became a supported distro for Pi2!!!
Comment by Random Geek Fri Feb 6 10:25:38 2015
Can you post your kernel source and config?
Comment by Anonymous Fri Feb 6 13:38:50 2015
This image is corrupted. Root partition fails to mount.
Comment by f4exb Fri Feb 6 23:44:43 2015
WTF is bmap tools and what's the use for it? Can't you just create an image file?
Comment by Anonymous Fri Feb 6 23:51:24 2015
Hey what's the userid and password?
Comment by Anonymous Sat Feb 7 00:27:23 2015
The Debian contrib and non-free repos as well as the security repos should be in the apt sources configuration.
Comment by OliD Sat Feb 7 05:28:04 2015
Hello, how to install it? I am unpacking it, writing image to sd with a Win32DiskImager and inserting into RPI2 but nothing is happening
Comment by A K Sat Feb 7 18:19:26 2015

Thanks a ton. I am in the process to get proview.se running on the rpi2 / Jessie ...

Comment by maba Tue Feb 10 14:20:58 2015

For everyone who had problems running it on the rp2 a simple solution is to use the bmap-tools to copy the image (as the author says) on the sd instead of any other programs. The procedure that worked for me was:

  1. Download and extract the jessie-rpi2-20150202.img.gz to get an .img file
  2. On any debian-based linux type "sudo apt-get install bmap-tools" and install it.
  3. Then type "sudo bmaptool copy --nobmap 'yourlocation/jessie-rpi2.img' /dev/sdx" (Change yourlocation to the location of the .img file and sdx for the letter where the SD is mounted, if you don't know it type "sudo fdisk -l" and look for it).
  4. Wait until it finishes and then put the SD on your rp2.

Actually this port is pretty damm fast, it seems a clearly replacement for our lovely Raspbian :)

Comment by Juan Tue Feb 10 19:59:58 2015

My rpi2 shipped and now here's this :)

Thanks for your hard work!

Comment by jocala Thu Feb 12 07:39:37 2015
Can't get Wifi to work.
Comment by Vitaly Sat Feb 14 02:35:58 2015
I don't suppose there is a write up of what you did anywhere - I'd like to be able to do my own network install (with the mimimum number of packages). Plan on looking to see if I can adapt the raspbain network instal image or the raspbian installer when I get time. Thanks for showing it is possible.
Comment by miket Sat Feb 14 23:40:17 2015
My rpi2 arrived today and setting up debian was cake thanks to you. Much appreciated my friend!
Comment by jocala Sun Feb 15 02:20:12 2015
Is there any way to install this onto an sd card via a windows PC? My guess is Win32DiskImager alone isn't enough for this?
Comment by edwinj85 Sun Feb 15 17:41:52 2015

Turns out you can get this running with just Win32DiskImager! You just need to unzip the .GZ archive and write the image to your sd card like you would with a normal raspbian distro. When you get to the command line just run apt-get install task-lxde-desktop to get a basic desktop running, it will take a long time to install. If the screen goes blank just press a key on your keyboard as the hdmi output of the pi loves to go idle.

After several downloads a few bouts of configuration pages you should get to a full fat desktop! You will then want to edit the config.txt in the /boot/firmware folder to disable overscan (then reboot) and you will also want to expand your primary partition to use all the space on your SD card or you won't have anything to spare:

http://raspberrypi.stackexchange.com/questions/499/how-can-i-resize-my-root-partition

I know this all works because I'm writing from a Pi 2 with debian on it right now! I still need to get sound working but this is great, thanks to the OP!

Comment by EdwinJ85 Sun Feb 15 20:27:54 2015
Hello. Act led does not blink even with manual control.
Comment by Anonymous Tue Feb 17 11:58:24 2015

Hey Vitali! About your wifi issue. You might need to install firmware for your usb wifi adapter. This worked for me:

Add Jessie repositories for contrib and non-free.

nano /etc/apt/sources.list
deb http://ftp.debian.org/debian jessie main contrib non-free
apt-get update

Identify your hardware:

apt-get install usbutils
lsusb

My wifi showed up as realtek RTL8188CUS

Install firmware:

apt-get install firmware-realtek

If not sure, use a sledgehammer to crack a nut:

apt-get install firmware*

Configure the network

apt-get install wicd-curses
wicd-curses

Highlight your ssid and tap right-arrow. Enable "automatically connect to this network", enter the secret key and tap F10 to finish. Highlight wired networks and tap (uppercase) D to disconnect. Highlight your ssid again and tap Enter to connect. Tap Q to exit.

Check for a connection:

ping bbc.co.uk

Reboot to check persistence ie that interface comes up automatically.

You may wish to install ssh in order to run headless.

apt-get install ssh

Good luck - Chris

Comment by Untrammelled Sat Feb 21 17:58:54 2015

How is the performance compared to Raspbian, same? Is the tools to expand the partition to use the entire SD card included?

I don't suppose, that I can just use dist-upgrade the kernel after installation? I am thinking about security here - I like to always have the most up-to-date system.

Comment by CuriousDane Mon Feb 23 20:40:17 2015

I saw that that docker is already working!

But of course you need a base image... Do you think you could provide one? I think I don't know enough about basic Debian to pull that off myself...

Comment by Martin Mon Feb 23 22:55:17 2015

Thanks for the great work! I used your experience as a basis for producing an Ubuntu 14.04 image. Details are at https://wiki.ubuntu.com/ARM/RaspberryPi .

Some observations:

  • 3.18.7 applies nearly cleanly on top of 3.18.5 + BCM2709 patches, if you want to produce an updated kernel. My 3.18.0-14.15 kernel is based upon vivid's 3.18.0-14.15 kernel, which is based on 3.18.7.
  • The firmware in the raspberrypi-firmware-nokernel package is ancient (relatively speaking) from December, and is probably causing some of the problems in the comments here. The activity LED not working is definitely one of them.
  • I've adopted your change of putting the firmware in /boot/firmware. Hopefully that sticks, as it's a good idea.
  • I've split raspberrypi-firmware-nokernel (previously binary bootloader firmware + binary userland utils in /opt/vc) into raspberrypi-firmware-nokernel (which now just has the firmware) and raspberrypi-vc (which compiles the userland utils / libraries from source and installs them "properly" in /usr).
  • I've packaged xserver-xorg-video-fbturbo, for faster window move/scroll operations on the Raspberry Pi. The packaging is based on xserver-xorg-video-fbdev from trusty, but should be portable to jessie with little/no modification.

My packages are available at https://launchpad.net/~fo0bar/+archive/ubuntu/rpi2/+packages if you'd like to take a look.

Comment by Ryan Finnie Tue Feb 24 06:26:03 2015

Juan: If you're in the directory that you downloaded all 3 files to (and have "bmap-tools" installed -- as suggested using "apt-get install bmap-tools" on a Debian based system), the following command is enough:

sudo bmaptool copy jessie-rpi2-20150202.img.gz /dev/sdX

where sdX is your SD card's device (and you don't need the "sudo" if you're root already) of course.

Using bmaptool is really a time saver and it is pretty clever in discovering the *.bmap file and extracting the *.gz automagically prior to writing the image file to the SD card. :-)

Comment by Robert Tue Feb 24 17:50:19 2015

Hi all !

Great work ! I bmapped the image to a 16gb stick, booted the rpi, then did "apt-get install xbmc gnome"! Ran into space issues (the partitions are for a 4GB stick) so i resized the partition and the filesystem on the fly without rebooting and continued apt-get. So now i have a full xorg and gnome install.

However, on reboot GDM seems to start, but only presents a black screen, no login box or anything.

Any idea what could be the cause ?

Thanks for your great work, Cheers, Karl

Comment by Karl_K Wed Feb 25 16:08:29 2015

Hi !

Thanks for the image, it provides lightning fast access to debian jessie on rpi2 !

However, it seems xbmc from debian repos does not work on rpi2, i get "XBMC needs hardware accelerated OpenGL rendering" error.

Any idea what to do ?

Cheers, Karl

Comment by Karl_K Fri Feb 27 00:44:55 2015
Could you enable ssh by default?
Comment by Dovydas Sun Mar 1 13:03:36 2015

Hey Sjoerd,

Great Image :-) I got XFCE4 running with an USB sound card, but i want to use the sound plug on the Pi. Did you make any progress on that?

DenniZ

Comment by DenniZr Mon Mar 2 16:41:17 2015

I installed this as my first raspberry OS and it works great. I have a gcc 4.9.2 development environment up and running. But now I want to enable the perfomance counter and for that I need to make a kernel module, I know little more than the guides on the web provide but to get things right, I need the kernel sources. Do I need the patched sources you built from, and in that case may I have them? I understand if you don't have an answer...

Comment by Anders Sat Mar 7 14:12:32 2015
Anders, it looks like the kernel is packaged in the regular Debian way. To get the full kernel source, you can apt-get install linux-source-3.18, which puts a source tarball in /usr/src. To get just the headers (which usually suffices to build a kernel module), you can apt-get install linux-headers-3.18. That puts the headers in the place where they're found by the usual module-building process.
Comment by Jeff Epler Mon Mar 9 16:03:43 2015

You have done a very good job!I now have been working with it some days. But is there a Descrption how to get the Act-Led still working without building a new SD-image ? ? What has to be updated on the SD-image ? What files ? I think noone needs to use the bitmap-tools. To copy the 3M-image bit by bit took me about 10 Minutes with Rasbian and my RPI-2. you than can expand the image with fdisk or Gparted. I installed the mate-desktop-environment together with lightDM and it seems to be perfect for this image on RPI-2. Jessie with mate-desktop seems to be something faster than Ubuntu 14.04 with XFCE so I will stay at Jessie with Mate. I managed to install the Chromium-Webbrowser 37.xxx together with the Pepperflashplayer-Plugin an it also runs perfect. I refered to this link here:

http://blog.valitov.me/2014/06/installing-google-chromium-on-arm.html?m=1

many greetings

Klaus

Comment by Klaus Tue Mar 10 20:48:45 2015

Just FYI folks incase you were thick like me and missed it -- the config for /boot/config.txt has been moved to /boot/firmware/config.txt

So don't make a /boot/config.txt, it will be ignored, but do edit /boot/firmware/config.txt. Saved me a lot of trouble once all of that clicked in.

Comment by Joe Wed Mar 11 08:45:01 2015
Did you manage to get OpenGL running? I'm trying to get Kodi to run to no avail.
Comment by jake Wed Mar 11 18:52:26 2015

in now could manage to get the newest firmware and ACT led is working. For a quick solution I installes andrew Hessets udate script which is in Rasbian and can be started with "rpi-update" To install the script please type or copy this commands in a terminal

If not installed already install git :

root@jessie-rpi:~# apt-get install git

root@jessie-rpi:~# wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update -O /usr/bin/rpi-update && sudo chmod +x /usr/bin/rpi-update

root@jessie-rpi:~# sudo rpi-update

Now the script has written the new files to ./boot directory but we need them under .boot/firmware

you have to move now all new files from ./boot to ./boot/firmware. The old files there have to be replaced with the new ones. If done so make a reboot.

Now the act-led should blink again.

Later we should update Andrews script for us with the right download directory.

many regards

Klaus

Comment by Klaus Wed Mar 11 20:59:04 2015
Sorry, please remove "sudo" out of this commands.
Comment by Klaus Wed Mar 11 21:02:49 2015

Hi Jeff, thanks for the pointers. Installing the headers using apt-get was not possible. But I got the source instead, unpacked it, ran make modules_prepare and pointed the makefile to the kernel source root. I can now build a kernel module that I can force feed the kernel with modprobe -f, I am close to success...

Comment by Anders Wed Mar 11 22:04:43 2015

There are some things still missing in this image.

First you need the alsa-utils:

apt-get install alsa-utils

Configure the output to go to 3,5mm jack:

amixer cset numid=3 1

Than load modprobe:

modprobe snd_bcm2835

If all is done you should have sound on 3,5mm jack.

If you want sound on hdmi outut:

amixer cset numid=3 2

This modprobe and others should be loaded already at boot. Configuration should be possible at ./etc/modprobe.d Maybe one can refer to the already existing settings at Rasbian.

Comment by Klaus Wed Mar 11 22:49:25 2015
...

on initial boot... after apt-get update && apt-get upgrade...

Setting up initramfs-tools (0.119) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.119) ... update-initramfs: Generating /boot/initrd.img-3.18.0-trunk-rpi2 Unsupported platform. run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1 dpkg: error processing package initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) -- Is this to be expected ?

root@jessie-rpi:~# apt-get install linux-headers-3.18 Reading package lists... Done Building dependency tree
Reading state information... Done Note, selecting 'linux-headers-3.18.0-trunk-all-armhf' for regex 'linux-headers-3.18' Note, selecting 'linux-headers-3.18.0-trunk-rpi2' for regex 'linux-headers-3.18' Note, selecting 'linux-headers-3.18.0-trunk-all' for regex 'linux-headers-3.18' Note, selecting 'linux-headers-3.18.0-trunk-common' for regex 'linux-headers-3.18' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:

The following packages have unmet dependencies: linux-headers-3.18.0-trunk-rpi2 : Depends: linux-kbuild-3.18 but it is not installable E: Unable to correct problems, you have held broken packages. ---seems trying to install headers does not work as previously stated?

Comment by spencer Thu Mar 12 06:48:32 2015

To load the soundmodule at boot time you should edit the soundmodule to modules.conf in ./etc/modules-load.de

There you can add one line for any kernel module you want to load at boot time. For soundmodule add :

snd_bcm2835

Don't forget to install alsa-utils

and switch output to 3,5mm jack with "amixer cset numid=3 1" or to hdmi with "amixer cset numid=3 2"

Comment by Klaus Thu Mar 12 09:20:27 2015

I encountered the same problem as Spencer above. Everything worked fine until I did an apt-get update & upgrade after which I got the same error messages as above. Not sure what to do about this. Everything worked beautifully before.

Paul

Comment by Paul Thu Mar 12 14:52:52 2015

I ran into the same problem as above when upgrading the image. The short term problem is that flash-kernel 3.33 does not recognize the RPI2.

A temporary fix is to hold back flash-kernel to 3.31 until 3.33 is fixed. Do "apt-mark hold flash-kernel" before you upgrade. After it is fixed you can lift the hold with "apt-mark unhold flash-kernel"

Steve

Comment by Steve Zingman Fri Mar 13 01:50:24 2015
root@jessie-rpi:~# apt-cache policy flash-kernel
flash-kernel:
  Installed: 3.33
  Candidate: 3.33
  Version table:
 *** 3.33 0
        500 http://ftp.debian.org/debian/ jessie/main armhf Packages
        100 /var/lib/dpkg/status
     3.31~exp.1co1+b3 0
        500 https://repositories.collabora.co.uk/debian/ jessie/rpi2 armhf Packages

It seems that flash-kernel gets updated to main version instead of the collabora one. You can downgrade (and hold), but it might be useful to pin the collabora repo to a high enough priority. Someone might post a helpful file.

Comment by XTL Fri Mar 13 07:52:10 2015

You can have the Hexxeh rpi-update tool update a different directory with BOOT_PATH and ROOT_PATH environment variables. They default to / and /boot, so I should just be able to set them to / and /boot/firmware right?

Also I wasn't able to get OC working on this image. My Pi refused to go any faster than 800Mhz.

Comment by David Fri Mar 13 18:24:39 2015
For those having issues with upgrading due to flash-kernel, the flash-kernel package in the collabora repositories has been rebased on the version in jessie which should solve the problem
Comment by sjoerd Fri Mar 13 20:52:00 2015

Thanks and also "dankjewel" I guess!?

Paul

Comment by Paul Sat Mar 14 14:10:57 2015
What is the difference between Debian Jessie and Raspbian Jessie (get it by taking Raspbian Wheezy and change sources.lst to jessie), other than the fact that Raspbian delivers rpi specific packages already? I'm using Raspbian Jessie for two weeks now and it seems to have all the same package versions just like Debian Jessie. I'm running on an "old" Pi B, however (fully headless, too, so no GUI related stuff whatsoever installed). I'm thinking of getting a RPi2, will there be any benefit of using Debian Jessie instead of Raspbian Jessie?
Comment by Anonymous Sun Mar 15 19:36:15 2015

Hi !

I just upgraded firmware and still xbmc from debian repos will not run due to missing OpenGL support. What i do not understand is that in the debian xbmc source makefile it automatically uses opengles compile parameters on ARM platforms, so it seems its actually compiled the right way.

This guy has working kodi on debian jessie on rpi2: http://www.raspberrypi.org/forums/viewtopic.php?f=56&t=101831

I installed it and it just works. Its version 14.1 so its newer than jessies 13.2 but he seems not to want to disclose how he did it. I would really prefer a straight debian install like we discuss here, with just kernel and a few other packages not from the repos, if we could just get xbmc/kodi running....

Cheers, Karl

Comment by Karl_K Sun Mar 15 22:14:36 2015

Is there a way to get EGL working (e.g. for clutter or qtquick based things to work)? There is libraspberrypi0 package, but it seems most libraries pull in and use Mesa, which leads to failure starting anything.

Example hello worlds:

$ qml -qt5 test4.qml 
libEGL warning: GLX/DRI2 is not supported
libEGL warning: DRI2: failed to authenticate
Unable to find an X11 visual which matches EGL config 77
Could not initialize OpenGL
Aborted
$ ./testclutter.py 
libEGL warning: GLX/DRI2 is not supported
libEGL warning: DRI2: failed to authenticate

(testclutter.py:6885): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to eglMakeCurrent with no surface
Segmentation fault
Comment by Axel Tue Mar 17 12:34:45 2015

U-boot has RPi2 support since a while. Would you update to 3.19 with Mesa(anholt's implementation)?

Comment by MY123 Thu Mar 19 18:35:18 2015

After trying for ages to compile kodi on rpi2 i finally found a different way to get what i want:

http://karl.kashofer.org/2015/03/19/debian-jessie-xfce-and-kodi-on-rpi2/

This now seems to work, Cheers, Karl

Comment by Karl_K Thu Mar 19 22:13:25 2015

If you're having trouble installing linux-kbuild-3.18, it's in the experimental release of debian. Just add the following line to /etc/apt/sources.list:

deb http://ftp.debian.org/debian experimental main

Then run:

sudo apt-get update
sudo apt-get -t experimental install linux-kbuild-3.18

and you should be good to go.

Comment by Jack Sun Mar 22 05:08:20 2015

For (my) reference, I have been able to successfully run outofthebox omxplayer (omxplayer_0.3.6~git20150319~7c752d3_armhf.deb) after installing the following :

libraspberrypi0:armhf 1.20141219-1~nokernel1.co1+b3
libraspberrypi-bin:armhf 1.20141219-1~nokernel1.co1+b3
(and of course the omxplayer dependency)

gpu_mem=192

I wonder when the latest firmware that supports gpu_mem_1024 is going to be released on the repository ? Working great !

Thanks, Thomas.

Comment by thomas /= Tue Mar 24 11:31:25 2015

I had the same Problem, that overclocking did not work after installing debian jessie.

This can be fixed by setting:

echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo ondemand > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

echo ondemand > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor

echo ondemand > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor

in /etc/rc.local

Comment by Anonymous Wed Mar 25 21:59:16 2015

I think for those of trying to run Kodi I have a solution.

You'll need to follow the usual instructions for install deb-multimedia's repos:

Add the keys:

wget http://www.deb-multimedia.org/pool/main/d/deb-multimedia-keyring/deb-multimedia-keyring_2014.2_all.deb

dpkg -i deb-multimedia-keyring_2014.2_all.deb

Add the repository:

http://www.deb-multimedia.org/debian-m

Update:

apt-get update

Install kodi:

apt-get install kodi kodi-bin kodi-standalone

Build a launch script:

$ nano kodi.sh

!/bin/sh

export LD_LIBRARY_PATH=/opt/vc/lib:/opt/kodi /usr/lib/kodi/kodi.bin

Save it and run it. It seems to work fine.

Just be warned you'll need to have the additional raspberry pi stuff from the collabora repository: I didn't have them installed on my image and apt-get couldn't find them, so I had to wget and install manually...

Comment by joe Thu Mar 26 22:37:02 2015

SSH keys are included in the image, which is insecure. It means that anyone can who has access to your network can impersonate your specific Raspberry Pi, which is one of the things that SSH is designed to prevent.

As a workaround, users can remove the existing keys:

sudo rm /etc/ssh/ssh_host_*_key*

And then regenerate their own unique keys:

sudo dpkg-reconfigure openssh-server

If you've ssh'd to your Raspberry Pi previously, you'll get a warning or error about the key having been changed. On your client machine, remove the entries in ~/.ssh/known_hosts listing your Raspberry Pi's old key to rectify this.

Comment by J.P. Larocque Wed Apr 8 00:18:10 2015

Thanks for your work and building an Image based on Debian jessie.

i've recreated my own Repository and added some packages for my own system. so u can also this repo. http://debian.gunah.eu/debian/ i've provid also a new version of flash-kernel (with your patch), because i got an issue with "Unsupported Platform".

About the Problem of some user with the serial of the raspberry pi, i've used the original raspbian to find it out.

Comment by Mathis Wed Apr 8 14:28:43 2015

Could you update the collabora-repo version once again?

Merci, Robert

Comment by Robert Fri Apr 10 14:52:16 2015

Hi All! Please help me! Im rooky :) jessie-rpi login: ?

Comment by warpig Fri Apr 10 22:53:02 2015
How do I get rid of the initramfs-update error message after each apt-get run?
Comment by Rolf Tue Apr 14 22:26:52 2015

The flash-kernel script doesn't work. You must manually copy (as root) the kernel to the proper location.

user@rpi:~# cp /boot/vmlinuz-3.18.0-trunk-rpi2 /boot/firmware/kernel7.img

To install the linux-headers-3.18.0-trunk-rpi2 package, you have a dependency on the virtual package linux- kbuild - 3.18. This package come from experimental Debian repositories. You must add them to the end of sources.list file and adjust the priority of those repositories.

user@rpi:~# echo "# Debian Exp\
deb http://ftp.fr.debian.org/debian experimental main contrib non-free\
deb-src http://ftp.fr.debian.org/debian experimental main contrib non-free" >> /etc/apt/sources.list
user@rpi:~# cat <<EOF > /etc/apt/preferences.d/experimental
Package: *
Pin: release a=experimental
Pin-Priority: 80
EOF

To illustrate, here is my sources.list :

user@rpi:~# cat /etc/apt/sources.list
# Repo spécifique RaspPi2 (ARMV7 armhf)
deb https://repositories.collabora.co.uk/debian jessie rpi2

# Debian repo
deb http://ftp.fr.debian.org/debian jessie main contrib non-free
deb-src http://ftp.fr.debian.org/debian jessie main contrib non-free
deb http://ftp.fr.debian.org/debian jessie-updates main contrib non-free
deb-src http://ftp.fr.debian.org/debian jessie-updates main contrib non-free
deb http://security.debian.org/debian-security jessie/updates main contrib non-free

# Debian Exp
deb http://ftp.fr.debian.org/debian experimental main contrib non-free
deb-src http://ftp.fr.debian.org/debian experimental main contrib non-free

And my /etc/apt/preferences.d/ directory:

user@rpi:~# cat /etc/apt/preferences.d/collabora
Package: *
Pin: origin repositories.collabora.co.uk
Pin-Priority: 600
user@rpi:~# cat /etc/apt/preferences.d/experimental
Package: *
Pin: release a=experimental
Pin-Priority: 80

I hope it could be useful for other ...

Comment by BoN_Lth Fri Apr 17 11:10:09 2015

I'm the founder of SolydXK. I've used your image as a base for SolydX RPI2. I hope you don't mind.

You can see my post (with download link to the ISO) here: http://forums.solydxk.com/viewtopic.php?f=53&t=5457

Comment by Schoelje Fri Apr 17 16:25:11 2015

Hello, how to install a flash plugins with this optimized version of Debian Jessie for Raspberry Pi2 thank you for your answer

Comment by jy Mon Apr 20 18:53:23 2015

Append the following to /etc/flash-kernel/db to make it work with the updated flash-kernel version:

Machine: Raspberry pi 2 Model B
Machine: BCM2709
Kernel-Flavors: rpi2
Boot-Kernel-Path: /boot/firmware/kernel7.img

Comment by BtbN Tue Apr 21 10:33:51 2015

do not add deb-multimedia.org,

pardon my giant text but I had to do it to be heard over the last guy. it's not safe, see what support says about it: http://ircbots.debian.net/factoids/factoid.php?key=dmm
Comment by shawn Thu Apr 23 06:55:18 2015

sjoerd, the version of flash-kernel in jessie overtook the version in your repo. please bumb the version. for now I will use apt pinning as a work around.

root@jessie-rpi:~# apt-cache policy flash-kernel flash-kernel: Installed: 3.35 Candidate: 3.35 Version table: * 3.35 0 500 http://ftp.debian.org/debian/ jessie/main armhf Packages 100 /var/lib/dpkg/status 3.33.co1+b1 0 500 https://repositories.collabora.co.uk/debian/ jessie/rpi2 armhf Packages

Comment by shawn Thu Apr 23 07:50:09 2015

I have downloaded the Debian image from https://images.collabora.co.uk/rpi2/ and am very impressed with the way it my webserver. On my RPI2's I also have the Raspberry Pi camera module which work perfectly under Raspian but I do not know what is needed or the steps to make it work under this pure Debian environment. I would be very grateful if someone could explain the steps required to get it working. Ultimately I want to steam video to a web page (not using VLC) in html. Regards Chris Bussey

Comment by Chris Bussey Sun Apr 26 19:32:20 2015

small image, but include the essentials like dhcp and ssh.

Perfect for my needs.

Comment by Marco Sun Apr 26 20:33:55 2015
Very nice effort, i hope to see this integrated into Debian soon. Kudos.
Comment by dutchfish Sat May 2 02:34:06 2015
My notes say you can get the camera working (at least in some way) by adding the line start_x=1 to config.txt (see note about location above). Then you can load the module bcm2835-v4l2.
Comment by XTL Thu May 7 09:25:22 2015
What toolchain did you use for crosscompiling the kernel?
Comment by ken Mon May 11 09:49:35 2015

Hi,

many, many thanks for this image! I'm using it since one week and like it very much.

After installing the image, I've done some changes that I like to share with you here. Thanks to shawn for his help with this notes.

ENLARGE THE SECOND PARTITION ON THE SDCARD AFTER DDING THE IMAGE
for example using gparted

CHANGE ROOTS PASSWORD
'passwd'
follow instructions

CHANGE HOSTNAME (see also https://wiki.debian.org/HowTo/ChangeHostname)
'grep -R jessie-rpi /etc/*' check which files you need to edit
'vi /etc/hostname' edit the hostname in /etc/hostname
'vi /etc/hosts' edit the hostname in /etc/hosts
'dpkg-reconfigure exim4-config' reconfigure exim4
'reboot' reboots the system

PREVENT PACKAGE FLASH-KERNEL UPDATING FROM OFFICIAL REPO WITH APT PINNING
'touch /etc/apt/preferences.d/flash-kernel' create a new file
'vi /etc/apt/preferences.d/flash-kernel' edit it an add the following lines to it:
Package: flash-kernel
Pin: origin repositories.collabora.co.uk
Pin-Priority: 1000
'apt-cache policy flash-kernel' check if the package is pinned

GENERATE NEW SSH KEYS (from http://sjoerd.luon.net/posts/2015/02/debian-jessie-on-rpi2/#comment-4c4e1defb59a765819781eddc928fd6d)
'rm /etc/ssh/ssh_host_*_key*' remove the old ones
'dpkg-reconfigure openssh-server' create new ones

RECONFIGURE LOCALES AND TIMEZONE
'dpkg-reconfigure locales'
'dpkg-reconfigure tzdata'

ACTIVATE ADDITIONAL REPOS
'vi /etc/apt/sources.list' open editor and add the following:
deb http://ftp.us.debian.org/debian/ jessie contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
deb http://ftp.us.debian.org/debian/ jessie-updates main contrib non-free

NOW YOU CAN SAFELY UPDATE THE SYSTEM
'apt-get update'
'apt-get upgrade'

Comment by nadu Sun May 17 23:31:31 2015

Hej Sjoerd! Great work with this jessie image.

I've instaled it without problem. But when I try to configure the keyboard to my localization, it does not work.

I do: dpkg-reconfigure keyboard-configuration and all is ok. But when I finished, there were two warnings about some "invoke-rc deprecated mode" (or similar) and the keyboard arrangement didn't change.

After this I tried service keyboard-setup start but nothing happens: I get stucked in English keyboard, and it is a mess to keep track of many symbols.

What can I do!? TIA

Comment by Shevek Wed May 20 00:17:51 2015
To everybody asking me how to use vi: you can use another editor like nano as well. It should be preinstalled. If not, run 'apt-get install nano'.
Comment by nadu Wed May 20 10:01:03 2015

Hi

I tested the image in various ways (I mean various burn image & boot) and it hangs after some time up (some hours). For the symptomps seems more a software lock than a hardware issue, as in all cases I'm able to ping the Pi and even TCP-connect via SSH (but not getting prompt), even serial console don't show me the login prompt.

On my first install, I upgraded packages and reconfigured some settings so I supossed I made some mistake/error (as the settings were from wheezy/sysvinit) which made the system unable to work as expected.

But on my second try, I simply wrote the image to the SD and booted the pi2, leaving it up for some hours, so no changes/upgrades of flash-kernel done on the image, nothing no changes.

I left some sessions logged (via serial and via SSH) and wait to things happen.

After some hours I found that the load is starting to increase (3, 5, 7 and up to 10 when finnally got fully unresponsive). During that I tried to check for top/dmesg output but that commands hang simply sitting down there, although other commands (free, ps, ..) work. (ps doens't show any process eating too much CPU).

As I still had access (when load was below 10), I preferred to reboot and start again to monitor the issue, but voilà:

root@tessa:~# reboot

Failed to start reboot.target: Connection timed out

Broadcast message from root@tessa on pts/1 (Thu 2015-05-21 08:27:49 UTC):

The system is going down for reboot NOW!

root@tessa:/var/log# uptime 08:51:47 up 11:39, 1 user, load average: 10.00, 10.02, 9.46

May be new systemd feature ??

Is very strange, as no one reported issues here, but I'm sure is not a Hardware issue as the same image worked correctly using raspbian Wheezy.

Any clues or any one having similar issues ?

Thanks

Comment by Marc Mon May 25 12:27:22 2015

Hi, thanks for this great tutorial and image, it all works perfectly for me. With one exception: After I apt-get install xfce4, I got

Processing triggers for initramfs-tools (0.120) ...
update-initramfs: Generating /boot/initrd.img-3.18.0-trunk-rpi2
Unsupported platform.
run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

I used the method suggested by BoN_Lth, which is manually copying /boot/vmlinuz-3.18.0-trunk-rpi2 to /boot/firmware/kernel7.img.

I've got flash-kernel pinned at the Collabora repository and its current version is 3.35.co1+b1.

Any way to fix this? Is copying the kernel to /boot/firmware/kernel7.img all that the flash-kernel package does?

Comment by Michael Franzl Wed May 27 19:09:20 2015

Seems the GPG keys for the collabora repository have expired (from apt-get update)

Reading package lists... Done W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repositories.collabora.co.uk jessie InRelease: The following signatures were invalid: KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1401577200 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1401577200 KEYEXPIRED 1433150817

W: Failed to fetch https://repositories.collabora.co.uk/debian/dists/jessie/InRelease

W: Some index files failed to download. They have been ignored, or old ones used instead.

Comment by Anonymous Wed Jun 3 15:40:00 2015
An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repositories.collabora.co.uk jessie InRelease: The following signatures were invalid: KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1401577200 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1401577200 KEYEXPIRED 1433150817
Comment by Debianita Fri Jun 5 23:43:02 2015

Hello,

First I must say, very good job. I've had no problems at all with that image on my new RPI2. All things I need for my project are working as expected. Thanks a lot for that.

I just want to update the PI with apt-get update ... It says ERR https://repositories.collabora.co.uk/debian/

And at the end:

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repositories.collabora.co.uk jessie InRelease: The following signatures were invalid: KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1401577200 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1401577200 KEYEXPIRED 1433150817

May be something wrong with the keyring?

Comment by bats4u Sat Jun 6 12:43:05 2015

Hi !

Would it be possible to enable usbip in your kernel build ?

karl@fernseher-rpi:~$ zcat /proc/config.gz |grep USBIP

CONFIG_USBIP_CORE is not set

I would really need that to share a printer. Thanks, Karl

Comment by Karl Mon Jun 8 00:31:01 2015

I had plenty of KEYEXPIRED errors during apt-get update. I found out that the Collabora key for apt expired.

$ apt-key list
/etc/apt/trusted.gpg.d/collabora-obs-archive-keyring.gpg
--------------------------------------------------------
pub   2048R/B5FBB289 2013-05-09 [expired: 2015-06-01]
uid                  Collabora OBS Automatic Signing Key <example@example.com>

I'm pretty bad when it comes to apt and security, I failed miserably with gpg and apt-key usual commands. In the end, I downloaded and installed manually the latest keyring package from Collabora. It may not be the right way to do it, but it works like a charm now.

$ wget https://repositories.collabora.co.uk/debian/pool/rpi2/c/collabora-obs-archive-keyring/collabora-obs-archive-keyring_0.5+b1_all.deb
$ dpkg -i collabora-obs-archive-keyring_0.5+b1_all.deb
$ apt-get update

Hope this helps ;)

Comment by elboulangero Mon Jun 8 18:58:25 2015

Just wanted to report this is still working after updating to 8.1 (with flash-kernel pinned as above).

Only issue is the apt key for your repo has expired (and is registered to an @example.com email address!)... Could these be updated/signed properly please?

Thanks

Comment by ScHiZniK Mon Jun 8 20:02:30 2015

Sadly running 'apt-get update' now results in:

KEYEXPIRED 1433150817

Any chance you could take a look at this on the repo?

Thanks!

Comment by chrisaw Wed Jun 10 23:49:03 2015

Turns out the resolution for the key issue I posted above is:

wget https://repositories.collabora.co.uk/debian/pool/rpi2/c/collabora-obs-archive-keyring/collabora-obs-archive-keyring_0.5+b1_all.deb dpkg -i collabora-obs-archive-keyring_0.5+b1_all.deb

Issue resolved - woop!

Comment by chrisaw Wed Jun 10 23:55:48 2015

There is a mismatch in the repository about the version of flash-kernel (at least). The one actually present is much more recent that the one advertised in the list.

Hope it helps.

Comment by jwarnier Wed Jun 17 10:46:36 2015

Seems there is a problem in one of the default sources:

Reading package lists... Done W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repositories.collabora.co.uk jessie InRelease: The following signatures were invalid: KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1401577200 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1401577200 KEYEXPIRED 1433150817

W: Failed to fetch https://repositories.collabora.co.uk/debian/dists/jessie/InRelease

Comment by Pedro Thu Jun 18 00:31:14 2015

Seems there is a problem in one of the default sources:

Reading package lists... Done W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repositories.collabora.co.uk jessie InRelease: The following signatures were invalid: KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1401577200 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1401577200 KEYEXPIRED 1433150817

W: Failed to fetch https://repositories.collabora.co.uk/debian/dists/jessie/InRelease

Comment by Pedro Thu Jun 18 00:31:38 2015

Hi,

doing an apt-update it complains about invalid signatures and expired keys:

W: An error occurred during the signature verification. 
The repository is not updated and the previous index files will be used. 
GPG error: https://repositories.collabora.co.uk jessie InRelease: 
The following signatures were invalid: KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 
KEYEXPIRED 1401577200 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 
KEYEXPIRED 1433150817 KEYEXPIRED 1401577200 KEYEXPIRED 1433150817

I tried to get new keys but I do not know where to get them. Using 'apt-key net-update' didn't work. I have the impression that those keys turned invalid only few days before...

Could you please help me to get valid keys for: repositories.collabora.co.uk jessie InRelease

Thanks in advance, Foka

Comment by Foka Sun Jun 21 11:29:39 2015

I've been using the image and updating it without issue since February. Recently on running apt-get update I've been getting an error with the repository as follows:


Hit http://ftp.debian.org jessie InRelease
Hit http://ftp.debian.org jessie/main armhf Packages Hit http://ftp.debian.org jessie/main Translation-en Get:1 https://repositories.collabora.co.uk jessie InRelease Get:2 https://repositories.collabora.co.uk jessie InRelease [2,707 B] Err https://repositories.collabora.co.uk jessie InRelease

Fetched 2,707 B in 19s (140 B/s)
Reading package lists... Done W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repositories.collabora.co.uk jessie InRelease: The following signatures were invalid: KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1401577200 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1433150817 KEYEXPIRED 1401577200 KEYEXPIRED 1433150817

W: Failed to fetch https://repositories.collabora.co.uk/debian/dists/jessie/InRelease

W: Some index files failed to download. They have been ignored, or old ones used instead.


Any assistance would be appreciated.

Comment by Anonymous Sun Jun 28 02:33:24 2015
How do we get a new key for apt-get? The current key expired. Thanks.
Comment by Andrew Lentvorski Thu Jul 2 03:23:34 2015

I was looking for a good linux distro to use my RPI2 as a server, but all the other ones are bloated, or don't have good sources. All I had to do was use rufus to burn this to my MicroSD card, pop it in to my RPI2, and SSH into it. I changed the sources to the standard jessie list, ran apt-get update, then upgrade, now I have a surprisingly fast, cheap, mini server. ProFTPd-basic is super fast and awesome. Nginx and php5-fpm run flawlessly. And I can use it as an RTMP server too. So much value for the $. Thanks for the distro.

Comment by Stardust342 Thu Jul 2 21:11:06 2015
SPI

Hi, Thx your very much for your work, it is very quit and simple to install (bmaptools is really fast)

Still, i have a little problem. I need raspi-config, in order to activate SPI, and to connect a 4DS 32 LCD screen.

Where can i find this tool ? is there a new way to configure this raspbian ? Thx

Comment by CHERRIER Sylvain Mon Jul 6 16:46:38 2015
I've just installed my second RPI2 with current image jessie-rpi2-20150705.img.gz on the weekend. I saw that "trusted=yes" is set on Sjoerd's repository in /etc/apt/sources.list. I strongly recommend to remove this setting. I've already emailed Sjoerd about this. He will generate a fresh image. Thank you in adavance ;)
Comment by nadu Mon Jul 13 12:56:41 2015
I just ran into the same issue. The image is using systemd-timesyncd for time synchronization. Yet, I couldn't find out what's causing the problem, as systemd-timesyncd is running and seems to be confgured properly.
Comment by nadu Sat Nov 7 13:15:53 2015

Hi,

Raspbian Jessie Lite - the Minimal image based on Debian Jessie on official RPi site ( https://www.raspberrypi.org/downloads/raspbian/ ) looks like our image here.

Did anyone compare the official image and the one of this site? Sjoerd what do you think?

Regards, Murat TA1DB

Comment by TA1DB Mon Nov 30 11:28:42 2015

Thanks a lot for providing this really nice guide, I was able to use my pi2 with jessie in no time.

A few additions:

To get rid of systemd, this link provides all the details: http://without-systemd.org/wiki/index.php/How_to_remove_systemd_from_a_Debian_jessie/sid_installation

Basically all you need to do is to put the usual network stuff to /etc/network/interfaces and then

apt-get install sysvinit-core sysvinit-utils
cp /usr/share/sysvinit/inittab /etc/inittab
reboot
apt-get remove --purge --auto-remove systemd
echo -e 'Package: systemd\nPin: release *\nPin-Priority: -1' > /etc/apt/preferences.d/systemd

To get system time right:

dpkg-reconfigure tzdata
apt-get install ntp

I also added max_usb_current=1 to /boot/firmware/config.txt, so the PI gives enough power to an external USB Hard Drive.

Comment by Tim Fri Jan 15 22:35:48 2016

Thanks a lot for providing this really nice guide, I was able to use my pi2 with jessie in no time.

A few additions:

To get rid of systemd, this link provides all the details: http://without-systemd.org/wiki/index.php/How_to_remove_systemd_from_a_Debian_jessie/sid_installation

Basically all you need to do is to put the usual network stuff to /etc/network/interfaces and then

apt-get install sysvinit-core sysvinit-utils
cp /usr/share/sysvinit/inittab /etc/inittab
reboot
apt-get remove --purge --auto-remove systemd
echo -e 'Package: systemd\nPin: release *\nPin-Priority: -1' > /etc/apt/preferences.d/systemd

To get system time right:

dpkg-reconfigure tzdata
apt-get install ntp

I also added max_usb_current=1 to /boot/firmware/config.txt, so the PI gives enough power to an external USB Hard Drive.

Comment by Tim Fri Jan 15 22:36:41 2016
I solved the "time sync problem" a few weeks ago: It has been a hardware issue for me. I thought it had to be a timesync issue because my Pi was pingable but not reacting to https and ssh anymore (http wasn't active). As I posted before, systemd-timesync was configured properly. When I tried getting help on IRC, someone suggested to check hardware related stuff. He was right :)
Comment by nadu Mon Mar 14 20:51:05 2016
I appreciate to hear comments and/or test results if anybody already tested or plan to use this excellent debootstrap on the new RPi 3. Does it work good as it does on RPi 2? What differs?
Comment by TA1DB Wed May 4 12:36:49 2016