Differences between revisions 58 and 59
Revision 58 as of 2020-11-28 13:30:13
Size: 11241
Revision 59 as of 2020-11-28 13:30:55
Size: 11242
Deletions are marked like this. Additions are marked like this.
Line 44: Line 44:
Announced in 2019, this system adds a second HDMI port, more memory, true Gigabit Ethernet and USB3.
[[https://raspi.debian.net/tested-images/|RPi4 SD card images became available]], combining Debian 10 and a kernel from ''backports''. Known problems are
Announced in 2019, this system adds a second HDMI port, more memory, true Gigabit Ethernet and USB3. [[https://raspi.debian.net/tested-images/|RPi4 SD card images became available]], combining Debian 10 and a kernel from ''backports''.

Known problems are

Can I put Debian on my Raspberry Pi?

Yes. To quickly get a ready-to-use image, visit RaspberryPiImages. To know more, please read on.

Booting via a binary blob

All Raspberry Pi models before the 4 (1A, 1B, 1A+, 1B+, Zero, Zero W, 2, 3) boot from their GPU (not from the CPU!), so they require a non-free binary blob to boot. This binary blob is available in the non-free Debian repository, packaged as the raspi-firmware package (or raspi3-firmware until Debian 10).

Debian and Raspbian

The most often used distribution across all raspberries is Raspbian (also known as Raspberry Pi OS). This is, first of all, for historical reasons (booting a mainline Linux kernel was not supported on Raspberries until late 2018), but also because of other non-free components that are shipped as part of Raspbian (such as Oracle Java and Wolfram Mathematica).

Raspbian builds a single image for all of the Raspberry families, so you will get an armhf 32-bit, hard floating-point system, but built for the ARMv6 ISA (with VFP2), unlike Debian's ARMv7 ISA (with VFP3) port.

Raspbian is not affiliated with the Debian project, although it derives from it. You can also run regular Debian on your Raspberries! (keep reading...)

Raspberry Pi 1 (A, B, A+, B+, Zero, Zero W)

The systems now known as Raspberry Pi model 1 models A and B were announced in February 2012. This family was expanded by very similar models A+ and B+. In 2015, the Zero model was announced, using the same CPU as the 1 family but with a smaller form factor, followed by the Zero W, which adds wireless connectivity.

The first generation Raspberry systems work using Debian armel. The Raspberry Pi 1's processor falls uncomfortably between the processor families that Debian has chosen to target, between armel and armhf. While Raspbian solves this to some degree an unofficial port will always give less certainty than an official one.

The Zero uses the same SoC/CPU as the first version, so they should function identically.

Raspberry Pi 2

The second generation systems were announced on 2014. The only member of this family is the Raspberry Pi 2.

Second-generation raspberries (model 2 only) works with Debian armhf will work.

You can refer to the RaspberryPi2 page, which aims to collect more detailed information how to run Debian nicely on this hardware.

Raspberry Pi 3 (3, 3A+, 3B+)

The Raspberry Pi 3 was announced in 2016, and is the first 64-bit member of the family. Some models include wireless connectivity. This family will work with Debian arm64. For further details and information on how to run with this hardware, go to the RaspberryPi3 page.

Raspberry Pi 4 and Raspberry Pi 400

Announced in 2019, this system adds a second HDMI port, more memory, true Gigabit Ethernet and USB3. RPi4 SD card images became available, combining Debian 10 and a kernel from backports.

Known problems are

  • 968188 4K display resolution is not recognized with Raspberry Pi 4B

  • 968181 DRM unavailable on Rapsberry Pi 4B

More technical details about Raspberry Pi 4 support are available on the RaspberryPi4 page.

The Raspberry Pi 400, announced in November 2020, is extremely similar to the Raspberry Pi 4 B models. What works on the Pi 4 B models also works on the Pi 400.

Should I buy a Raspberry Pi?

That is a decision that you will have to make given your application, below are some pros and cons that you should consider.


  • Large and active community
  • Low price for the capabilities offered


  • 3D acceleration is not integrated with X or other standard mechanisms. Therefore 3D applications will currently require Pi specific builds. As of November 2020, there is work in progress to integrate it into both the Linux kernel and Mesa for the Raspberry Pi 4.
  • A binary blob used by the GPU must be present on the SD card for the system to boot.
  • While some hardware documentation has been released the documentation is sorely lacking.
  • While schematics are available the board design is closed and the main processor is not available for purchase by the general public.

A number of similar boards are available, generally at slightly higher prices but also usually with more powerful processors. Some examples are given below, more can be found in the CheapServerBoxHardware list.

Raspberry Pi issues

The Raspberry Pi issues relate to technical problems, software freedom and hype:

  • The CPU in the Raspberry Pi 1 and Zero implements the ARMv6 ISA (with VFP2) and is thus incompatible with the Debian armhf port baseline of ARMv7+VFP3 and ARM hardware-floating-point ports for other distributions, which all have the same baseline. It is compatible with Debian armel (armv4t, soft(emulated) FP), but floating-point tasks will be slow when running the Debian armel port. (This doesn't stand for newer families)
  • The Raspberry Pi (all models before the 4) boots from its GPU and only non-free software is currently available for the GPU, even starting the machine requires a large (2MB) blob of non-free, unsupportable software
  • The 3D driver for the Raspberry Pi, while Free Software, is just a shim that passes OpenGL commands directly to the non-free software running on the GPU. This means that any issues with OpenGL cannot be fixed nor performance improved. This is better than some other GPUs because the ARM part can be rebuilt. More recently an alternative driver has become available that drives the 3D core in the GPU directly from the ARM rather than passing messages to the VPU core in the GPU which in turn drove the 3D core.

Binary blob needed to boot

The binary blob needed to boot the Raspberry Pi can be downloaded using the rpi-update script available from https://raw.githubusercontent.com/Hexxeh/rpi-update/master/rpi-update and has been packaged as raspi3-firmware in the non-free repository of Debian (but should soon be renamed to just raspi-firmware, as it's not model-3-specific). It can be used with vmdebootstrap to create a bootable SD card image, according to a recipe from Petter Reinholdtsen.

See more information at this independent documentation project based on a combination of static analysis and trial and error on real hardware: https://github.com/hermanhermitage/videocoreiv/

Broadcom publicly released some code, licensed as 3-Clause BSD, to aid the making of an open source GPU driver. The "rpi-open-firmware" effort to replace the VPU firmware blob started in 2016: https://github.com/christinaa/rpi-open-firmware. See more at https://news.ycombinator.com/item?id=11703842 Unfortunately development of rpi-open-firmware is currently stalled.

QEMU User Emulation for Raspberry Pi Development

See RaspberryPi/qemu-user-static for information on how you can mount, edit, and run a Raspberry Pi disk image on a host Debian machine using QemuUserEmulation (much faster/simpler than than full system emulation)


Initramfs for custom loading of modules at boot does work, but you must update it everytime you use rpi-update, this way:

mkinitramfs -o /boot/initrd

In the Raspberry Pi 2 you must also include this in /boot/config.txt:

initramfs initrd followkernel

And this is /boot/cdmline.txt:

root=/dev/mmcblk0p2 initrd=-1 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 elevator=deadline rootwait

Because rpi-update is not the official way that Debian updates the Initramfs, you may find weird things happening when you update rpi, so if your system becomes unbootable because there is a needed module in the initrd that you need (like encryption), you must boot with another up to date sdcard, chroot into the new environment, mounting first /boot and /dev, and then update the initrd manually. This just happens because of the privative special way of booting of the Raspberry Pi, out of any reasonable standard.

Overclocking Pi 2

Overclocking is quite easy and convenient, and doesn't invalidate your warranty if you don't change voltage. It happens that the actual L2 speed of the Raspberry Pi 2 is severelly underclocked, making the device much more slower that it should actually be. There has been reports of users using overclocked speeds of the processor and the L2 for months without a single issue, but you must be carefull in respecting a good proportion between L2 speed and processor, and overclocking the RAM is generally not recommended.

Try this setting, it has demonstrated to be stable and doubles the speed of this small machine in general. Edit /boot/config.txt and substitute or add these lines:


Unfortunatelly, the options shown when running raspi-config are not quite stable even they are slower than this recommended option.

Giving more power to the USB devices

If you are running a lot of devices, you may need a lot of power. Actually, the Pi 2 can give up to 1.2A to the devices, but it is severely limited by default to 600mA, so if you connect a lot of devices, they are going to be reseting themselves or limiting in some ways because of lack of energy. There is an option to actually double the amount of energy you can give to the devices, but you must also use a good 2A adapter. Just edit /boot/config.txt and add this:


This way I am able to run a very energy consuming 4G modem and a Wifi dongle at the same time without issues.

Also, you not only need a good and reliable adapter, but also a good cable. The shorter and thicker the better.