Differences between revisions 7 and 8
Revision 7 as of 2020-05-12 18:48:32
Size: 4374
Editor: HolgerLevsen
Comment: add ToC
Revision 8 as of 2020-07-07 16:21:32
Size: 3443
Editor: ?xcancerberox
Comment: Change links to daily builds. Add rpi 4. Change overview.
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
Debian buster should be able to run on all of the Raspberry Pi ≤3 models, but there are a few issues preventing us from releasing an official image: We are building daily images to run on all of the Raspberry Pi ≤3 models. Work is being done to the 4 model, we are almost there!
Line 7: Line 7:
 * We need to more thoroughly test the Raspberry's hardware:
   * At least Raspberry Pi 0W, 1, 2 and 3B+ are known to boot; other submodels are ''expected'' to work (but testing and documenting them is necessary!)
   * 3B+ image reliably supports the wlan interface; 0W's not yet
 * The Bluetooth module is untested everywhere :-/
 * The new (June 2019) Raspberry Pi 4 is not yet supported (the kernel does not yet have a Device Tree for it)
More info in (https://raspi.debian.net/)[https://raspi.debian.net/]
Line 13: Line 9:
Longer-term improvements: == Daily images ==
Line 15: Line 11:
 * The hardware still needs a non-free binary blob to boot (included in the raspi3-firmware package). A [[https://github.com/christinaa/rpi-open-firmware|free software replacement]] is being worked on but development is [[https://github.com/christinaa/rpi-open-firmware/issues/37|stalled]].

Any help on these issues is very welcome!

== Preview images ==

First, lets set up some environment variables matching your needs. First, the raspberry model — It can currently be {{{0w}}}, {{{2}}} or {{{3}}}. If it's a {{{0w}}}:
First, lets set up some environment variables matching your needs. First, the raspberry model — It can currently be {{{0w}}}, {{{2}}}, {{{3}}} or {{{4}}}. If it's a {{{0w}}}:
Line 36: Line 26:
$ wget https://people.debian.org/~gwolf/raspberrypi/20190628/20190628_raspberry-pi-${RPI_MODEL}_buster_PREVIEW.img.xz $ wget https://raspi.debian.net/daily/raspi_{RPI_MODEL}.img.xz
Line 42: Line 32:
$ wget https://people.debian.org/~gwolf/raspberrypi/20190628/20190628_raspberry-pi-${RPI_MODEL}_buster_PREVIEW.img.xz.sha256
$ sha256sum -c 20190628_raspberry-pi-${RPI_MODEL}_buster_PREVIEW.img.xz.sha256
20190628_raspberry-pi-0w_buster_PREVIEW.img.xz: OK
$ wget https://raspi.debian.net/daily/raspi_{RPI_MODEL}.xz.sha256
$ sha256sum -c raspi_{RPI_MODEL}.xz.sha256
raspi_{RPI_MODEL}.img.xz: OK

Overview

We are building daily images to run on all of the Raspberry Pi ≤3 models. Work is being done to the 4 model, we are almost there!

More info in (https://raspi.debian.net/)[https://raspi.debian.net/]

Daily images

First, lets set up some environment variables matching your needs. First, the raspberry model — It can currently be 0w, 2, 3 or 4. If it's a 0w:

$ export RPI_MODEL=0w

Second, where is your SD card detected in your computer? Lets say, it's /dev/sdf:

$ export SD_CARD=/dev/sdf

Now, get the image you need:

$ wget https://raspi.debian.net/daily/raspi_{RPI_MODEL}.img.xz

It is recommended to check the image was correctly downloaded by comparing its SHA256:

$ wget https://raspi.debian.net/daily/raspi_{RPI_MODEL}.xz.sha256
$ sha256sum -c raspi_{RPI_MODEL}.xz.sha256
raspi_{RPI_MODEL}.img.xz: OK

You can also verify this SHA256 sum is the same Gunnar has:

$ LANG=C gpg --verify 20190628_raspberry-pi-3_buster_PREVIEW.img.xz.sha256.asc 
gpg: Signature made Sat Jun 29 06:19:48 2019 CEST
gpg:                using RSA key 7C795E5399688DDF66F7D62049DD2A4E4979619C
gpg: Good signature from "Gunnar Eyal Wolf Iszaevich <gwolf@debian.org>" [full]
gpg:                 aka "Gunnar Eyal Wolf Iszaevich <gwolf@gwolf.org>" [full]
gpg:                 aka "Gunnar Eyal Wolf Iszaevich (Instituto de Investigaciones Econ�micas UNAM) <gwolf@iiec.unam.mx>" [full]
gpg: WARNING: not a detached signature; file '20190628_raspberry-pi-3_buster_PREVIEW.img.xz.sha256' was NOT verified!
$ cat 20190628_raspberry-pi-3_buster_PREVIEW.img.xz.sha256.asc |grep img.xz
98970fa80eb55a9245cd99605e2b372236ed80d3ada85231b2293a6bec634557  20190628_raspberry-pi-3_buster_PREVIEW.img.xz
$ sha256sum  20190628_raspberry-pi-3_buster_PREVIEW.img.xz
98970fa80eb55a9245cd99605e2b372236ed80d3ada85231b2293a6bec634557  20190628_raspberry-pi-3_buster_PREVIEW.img.xz

Now, write the image to your SD card! Make sure $SD_CARD is right! (you risk losing information otherwise!)

$ xzcat 20190628_raspberry-pi-${RPI_MODEL}_buster_PREVIEW.img.xz | dd of=${SD_CARD} bs=64k oflag=dsync status=progress

If resolving client-supplied DHCP hostnames works in your wired network, you should be able to log into the Raspberry Pi using SSH after booting it (otherwise, you can only log in from the console):

$ ssh root@rpi3
# Password is “raspberry”

Of course, we want to come up with a better way to do this than shipping a network-listening service with a preset root password :-Þ

For the sources of this image (and/or for customizing your own build), please see https://salsa.debian.org/raspi-team/image-specs

Installation

It’s not necessary to dump a prebuilt image onto the SD card. You can use the configurable builder used to create the images linked above or a simple shell script creating Raspberry Pi 3B+ arm64 (or armhf) images to create your own image file or install straight to the SD card, from another running GNU/Linux machine.

This avoids problems with things like preset passwords, machine IDs, lack of random bytes/entropy, …