Raspi-image-spec/README.md

118 lines
4.0 KiB
Markdown
Raw Normal View History

# Raspberry Pi image specs
2017-10-08 21:18:48 +01:00
This repository contains the files with which the images referenced at
https://wiki.debian.org/RaspberryPiImages have been built.
2017-10-08 21:18:48 +01:00
## Option 1: Downloading an image
See https://wiki.debian.org/RaspberryPiImages for where to obtain the
latest pre-built image.
2017-10-08 21:18:48 +01:00
## Option 2: Building your own image
If you prefer, you can build a Debian buster Raspberry Pi image
2018-07-18 23:57:39 +01:00
yourself. If you are reading this document online, you should first
clone this repository:
2017-10-08 21:18:48 +01:00
```shell
git clone --recursive https://salsa.debian.org/raspi-team/image-specs.git
cd image-specs
2017-10-25 09:55:04 +01:00
```
For this you will first need to install the following packages on a
Debian Buster (10) or higher system:
* vmdb2 (>= 0.17)
* dosfstools
* binfmt-support
2021-03-04 08:41:51 +00:00
* qemu-utils
* qemu-user-static
2021-03-04 08:41:51 +00:00
* debootstrap
2020-08-29 19:38:44 +01:00
* time
* kpartx
2020-08-29 19:38:44 +01:00
To install these (as root):
```shell
2021-03-04 08:41:51 +00:00
apt install -y vmdb2 dosfstools qemu-utils qemu-user-static debootstrap binfmt-support time kpartx
2020-08-29 19:38:44 +01:00
```
Do note that at least currently vmdb2 uses some syntax that is available
only in the version in testing (Bullseye).
If debootstrap still fails with exec format error, try
2021-02-07 01:45:01 +00:00
running `dpkg-reconfigure qemu-user-static`. This calls
`/var/lib/dpkg/info/qemu-user-static.postinst` which uses binfmt-support
to register the executable format with /usr/bin/qemu-$fmt-static
This repository includes a master YAML recipe (which is basically a
configuration file) for all of the generated images, diverting as
little as possible in a parametrized way. The master recipe is
[raspi_master.yaml](raspi_master.yaml).
A Makefile is supplied to drive the build of the recipes into images.
Some portions of building the image will require root privileges, thus
you'll need to execute *make* below as root.
The argument to `make` is constructed as follows:
`raspi_<model>_<release>.<result-type>`
Whereby <model\> is one of `1`, `2`, `3` or `4`, <release\> is either `buster`
or `bullseye` and <result-type\> is `img` or `yaml`.
Model `1` should be used for the Raspberry Pi 0, 0w and 1, models A and
B. Model `2` for the Raspberry Pi 2 models A and B. Model `3` for all
models of the Raspberry Pi 3 and model `4` for all models of the
Raspberry Pi 4.
So if you want to build the default image for a Raspberry Pi 3B+ with
Bullseye, you can just issue:
```shell
make raspi_3_bullseye.img
```
This will first create a `raspi_3_bullseye.yaml` file and then use that
*yaml* recipe to build the image with `vmdb2`.
You can also edit the `yaml` file to customize the built image. If you
want to start from the platform-specific recipe, you can issue:
```shell
make raspi_3_bullseye.yaml
```
The recipe drives [vmdb2](https://vmdb2.liw.fi/), the successor to
`vmdebootstrap`. Please refer to [its
documentation](https://vmdb2.liw.fi/documentation/) for further details;
it is quite an easy format to understand.
Copy the generated file to a name descriptive enough for you (say,
`my_raspi_bullseye.yaml`). Once you have edited the recipe for your
specific needs, you can generate the image by issuing the following (as
root):
2017-10-25 09:55:04 +01:00
```shell
vmdb2 --rootfs-tarball=my_raspi_bullseye.tar.gz --output \
my_raspi_bullseye.img my_raspi_bullseye.yaml --log my_raspi_bullseye.log
2017-10-08 21:18:48 +01:00
```
This is, just follow what is done by the `_build_img` target of the
Makefile.
## Installing the image onto the Raspberry Pi
2017-10-08 21:18:48 +01:00
Plug an SD card which you would like to entirely overwrite into your SD card reader.
Assuming your SD card reader provides the device `/dev/mmcblk0`
(**Beware** If you choose the wrong device, you might overwrite
important parts of your system. Double check it's the correct
device!), copy the image onto the SD card:
2017-10-08 21:18:48 +01:00
```shell
sudo dd if=raspi_3.img of=/dev/mmcblk0 bs=64k oflag=dsync status=progress
2017-10-08 21:18:48 +01:00
```
Then, plug the SD card into the Raspberry Pi, and power it up.
2017-10-08 21:18:48 +01:00
2020-07-07 21:19:43 +01:00
The image uses the hostname `rpi0w`, `rpi2`, `rpi3`, or `rpi4` depending on the
target build. The provided image will allow you to log in with the
`root` account with no password set, but only logging in at the
physical console (be it serial or by USB keyboard and HDMI monitor).