Raspberry Pi

Warning: 11 Feb 2021 - There is currently a known bug upstream
kernel/initramfs cannot be loaded from subdirectory with same name as volume label

+ + +
+
+

This tutorial explains how to install Alpine Linux on a Raspberry Pi. Alpine Linux will be installed in diskless mode, hence, Alpine Local Backup (lbu) is required to save modifications between reboots. +

For scenarios where there is not expected to be significant changes to disk after setup (like running a static HTTP server), this is likely preferable, as running the entire system from memory will improve performance (by avoiding the slow SD card) and improve the SD card life (by reducing the writes to the card, as all logging will happen in RAM). Diskless installations still allow you to install packages, save local files, and tune the system to your needs. +

If any of the following apply, then installation in sys-mode installation is likely more appropriate. +

+

There will be constant changes to the disk after initial setup (for example, if you expect people to login and save files to their home directories)
Logs should persists across reboots
Plan to install packages which consume more space than can be loaded into RAM
Plan to install kernel modules (such as ZFS or Wireguard)

+

Preparation

+

Download the Alpine for Raspberry Pi tarball. You should be safe using the armhf build on all versions of Raspberry Pi (including Pi Zero and Compute Modules); but it may perform less optimally on recent versions of Raspberry Pi. The armv7 build is compatible with Raspberry Pi 2 Model B. The aarch64 build should be compatible with Raspberry Pi 2 Model v1.2, Raspberry Pi 3 and Compute Module 3, and Raspberry Pi 4 model B.
Create a bootable FAT32 partition on your SD card. The partitioning and formatting part of the instructions on the linked page could be done using a graphical partitioning tool such as gnome-disks, just make sure the partition type is W95 FAT32 (LBA). (The current type can be found in the "Type" column in the output of fdisk -l.)
Extract the tarball to the root of the bootable FAT32 partition.

+

To setup a headless system, a bootstrapping configuration overlay file headless.apkovl.tar.gz may be added to enable basic networking, so that following configuration steps can be performed under ssh. Pi Zero may be configured with simple USB ethernet-gadget networking with another computer sharing its internet connection. +

Optionally create a usercfg.txt file on the partition to configure low-level system settings. Specifications can be found here. However, note some settings can only be set directly in config.txt, which may be overwritten after updates. In particular, gpu_mem will have no effect when specified in usercfg.txt (source). Some interesting values include: +

+

To enable the UART console: enable_uart=1
To enable audio: dtparam=audio=on
If you see black edges around your screen after booting the Pi, you can add disable_overscan=1
If you plan to install on a Pi Compute Module 4 with I/O board, you may need to add: otg_mode=1

+

Recent versions include Broadcom firmware files. If you're using an older Alpine version, see section below. +

+

Installation

+

Follow these steps to install Alpine Linux in Diskless Mode: +

+

Insert the SD card into the Raspberry Pi and power it on
Login into the Alpine system as root. Leave the password empty.
Type setup-alpine
Once the installation is complete, commit the changes by typing lbu commit -d

+

Type reboot to verify that the installation was indeed successful. +

+

Post Installation

+

Update the System

+

After installation, make sure your system is up-to-date: +

+

apk update +apk upgrade

+

Don't forget to save the changes: +

+

lbu commit -d

+

Note: this does not upgrade the kernel. In order to upgrade the kernel, a full upgrade of the Alpine Linux version must be performed as described in upgrading Alpine Linux for removable media. +

+

Clock-related error messages

+

During the booting time, you might notice errors related to the hardware clock. The Raspberry Pi does not have +a hardware clock, thus you need to disable the hwclock daemon and enable swclock: +

+

rc-update add swclock boot # enable the software clock +rc-update del hwclock boot # disable the hardware clock

+

Since the Raspberry Pi does not have a clock, Alpine Linux needs to know what the time is by using a +Network Time Protocol (NTP) daemon. Make sure you have a +NTP daemon installed and running. If you are not sure, you can install an NTP client by running the following +command: +

+

setup-ntp

+

The Busybox NTP client might be the most lightweight solution. Save the changes and reboot, once the NTP software is +installed and running: +

+

lbu commit -d +reboot

+

After reboot, make sure the date command outputs the correct date and time. +

+

WiFi on boot

+

If you have already configured WiFi during the setup, the connection will not return on reboot. +You will need to start up a service to automatically connect to the wireless access point. +

+

Run rc-update add wpa_supplicant boot to connect to the wireless access point during bootup.
Run it manually with /etc/init.d/wpa_supplicant start.

+

Enable Graphics

+

Remount the boot partition writeable (i.e. /media/mmcblk0p1): +

+

mount /media/mmcblk0p1 -o rw,remount

+

Add the following lines to /media/mmcblk0p1/config.txt: +

+

dtoverlay=vc4-kms-v3d
+

+

If you are experiencing graphical issues, you can also try: +

+

dtoverlay=vc4-fkms-v3d
+

+

And perhaps also raising the default gpu_mem: +

+

gpu_mem=128
+

+

Note that raising the gpu memory is not likely to actually improve performance on the Pi4 +

Install the Mesa drivers: +

+

apk add mesa-dri-gallium

+

Then reboot: +

+

lbu_commit -d; reboot

+

WiFi drivers

+

As of Alpine 3.14, the WiFi drivers for the Raspberry Pi were moved from linux-firmware-brcm to the linux-firmware-cypress package (source?). Since the images seem to be an outdated version of the former, Wi-Fi will work during installation, but after the first update it will break. +Use the ethernet interface to download the required packages: +

+

apk add linux-firmware-cypress

+

And reboot. +

+

Persistent storage

+

Loopback image with overlayfs

+

When you install Alpine in diskless mode, the entire system is loaded into memory at boot. If you want additional storage (for example, if you need more space than offered by your RAM) we need to create loop-back storage onto the SD card mounted with overlayfs. +

First, make the SD card writable again and change fstab to always do so: +

+

mount /media/mmcblk0p1 -o rw,remount +sed -i 's/vfat\ ro,/vfat\ rw,/' /etc/fstab

+

Create the loop-back file, this example is 1 GB: +

+

dd if=/dev/zero of=/media/mmcblk0p1/persist.img bs=1024 count=0 seek=1048576

+

Install the ext utilities: +

+

apk add e2fsprogs

+

Format the loop-back file: +

+

mkfs.ext4 /media/mmcblk0p1/persist.img

+

Mount the storage: +

+

echo "/media/mmcblk0p1/persist.img /media/persist ext4 rw,relatime,errors=remount-ro 0 0" >> /etc/fstab +mkdir /media/persist +mount -a

+

Make the overlay folders, we are using the /usr directory here, but you can use /home or anything else. +

+

Warning: Overlay workdir needs to be an empty directory on the same filesystem mount as the upper directory. So each overlay must use its own workdir.

+

mkdir /media/persist/usr +mkdir /media/persist/.work_usr +echo "overlay /usr overlay lowerdir=/usr,upperdir=/media/persist/usr,workdir=/media/persist/.work_usr 0 0" >> /etc/fstab +mount -a

+

Your /etc/fstab should look something like this: +

+

/dev/cdrom /media/cdrom iso9660 noauto,ro 0 0 +/dev/usbdisk /media/usb vfat noauto,ro 0 0 +/dev/mmcblk0p1 /media/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,errors=remount-ro 0 0 +/media/mmcblk0p1/persist.img /media/persist ext4 rw,relatime,errors=remount-ro 0 0 +overlay /usr overlay lowerdir=/usr,upperdir=/media/persist/usr,workdir=/media/persist/.work_usr 0 0

+

Now commit the changes: (optionally remove the e2fsprogs, but it does contain repair tools) +

+

lbu_commit -d

+

Remember, with this setup if you install things and you have done this overlay for /usr, you must not commit the 'apk add', otherwise, while it boots it will try and install it to memory, not to the persistent storage. +

If you do want to install something small at boot, you can use `apk add` and `lbu commit -d`. +

If it is something a bit bigger, then you can use `apk add` but then not commit it. It will be persistent (in /user), but be sure to check everything you need is in that directory and not in folders you have not made persistent. +

+

Traditional disk-based (sys) installation

+ + + +

This material is proposed for merging ...

It should be merged with Classic install or sys mode on Raspberry Pi. There's an existing page for sys-installations on RasPi. +(Discuss)

+

It is also possible to switch to a fully disk-based installation. This is not yet formally supported, but can be done somewhat manually. This frees all the memory otherwise needed for the root filesystem, allowing more installed packages. +

Split your SD card into two partitions: the FAT32 boot partition described above (in this example it'll be mmcblk0p1) , and a second partition to hold the root filesystem (here it'll be mmcblk0p2). Boot and configure your diskless system as above, then create a root filesystem: +

+

apk add e2fsprogs +mkfs.ext4 /dev/mmcblk0p2

+

Now do a disk install via a mountpoint. The setup-disk script will give some errors about syslinux/extlinux, but you can ignore them. +The Raspberry Pi doesn't need them to boot. +

+

mkdir /stage +mount /dev/mmcblk0p2 /stage +setup-disk -o /media/mmcblk0p1/MYHOSTNAME.apkovl.tar.gz /stage +# (ignore errors about syslinux/extlinux)

+

Add a line to /stage/etc/fstab to mount the Pi's boot partition again: +

+

/dev/mmcblk0p1 /media/mmcblk0p1 vfat defaults 0 0

+

Now add a root=/dev/mmcblk0p2 parameter to the Pi's boot command line, either cmdline-rpi2.txt or cmdline-rpi.txt depending on model: +

+

mount -o remount,rw /media/mmcblk0p1 +sed -i '$ s/$/ root=\/dev\/mmcblk0p2/' /media/mmcblk0p1/cmdline-rpi2.txt

+

You might also consider overlaytmpfs=yes here, which will cause the underlying SD card root filesystem to be mounted read-only, with an overlayed tmpfs for modifications which will be discarded at shutdown. +

N.B. the contents of /boot will be ignored when the Pi boots. It will use the kernel, initramfs, and modloop images from the FAT32 boot partition. To update the kernel, initfs or modules, you will need to manually (generate and) copy these to the boot partition or you could use bind mount, in which case, +copying the files to boot partition manually, is not needed. +

+

echo /media/mmcblk0p1/boot /boot none defaults,bind 0 0 >> /etc/fstab

+

Persistent Installation on Raspberry Pi 3

+

See Classic install or sys mode on Raspberry Pi and https://web.archive.org/web/20171125115835/https://forum.alpinelinux.org/comment/1084#comment-1084 +

+

Persistent Installation on Raspberry Pi 4

+

As of 3.14, setup-alpine should ask you if you want to create a sys mode partition on your Raspberry Pi 4. +

+

Troubleshooting

+

Long boot time when running headless

+

If no peripherals are connected, the system might hang for an exceptionally long period of time while it attempts to accumulate entropy. +

If this is the case, simply plugging in any USB device should work around this issue. +

Alternatively, installing haveged, the random numbers generator, would speed up the process: +

+

 apk update 
+ apk add haveged
+ rc-update add haveged boot
+ lbu commit -d
+ service haveged start
+

+

(Tested on a raspberry pi zero W in headless mode, no USB connected, Alpine 3.10.3) +

+

apk indicating 'No space left on device'

+

Note some models of the Raspberry Pi such as the 3A+ only have 512M of RAM, which on fresh Alpine deployment will only leave around 200M for tmpfs root. It's important to keep this limitation in mind when using these boards. +

+

Wireless support with older Alpine images

+

If you need Wi-Fi, you'll need to download the latest Broadcom drivers to your SD card. +(Replace /mnt/sdcard with the correct mount point.) +

+

 git clone --depth 1 https://github.com/RPi-Distro/firmware-nonfree.git
+ cp firmware-nonfree/brcm/* /mnt/sdcard/firmware/brcm
+

+

Prefix	Effect
"`@`"	If the executable path is prefixed with "`@`", the second specified token will be passed as "`argv[0]`" to the executed process (instead of the actual filename), followed by the further arguments specified.
"`-`"	If the executable path is prefixed with "`-`", an exit code of the command normally considered a failure (i.e. non-zero exit status or abnormal exit due to signal) is recorded, but has no further effect and is considered equivalent to success.
"`:`"	If the executable path is prefixed with "`:`", environment variable substitution (as described by the "Command Lines" section below) is not applied.
"`+`"	If the executable path is prefixed with "`+`" then the process is executed with full privileges. In this mode privilege restrictions configured with `User=`, `Group=`, `CapabilityBoundingSet=` or the various file system namespacing options (such as `PrivateDevices=`, `PrivateTmp=`) are not applied to the invoked command line (but still affect any other `ExecStart=`, `ExecStop=`, … lines). However, note that this will not bypass options that apply to the whole control group, such as `DevicePolicy=`, see systemd.resource-control(5) for the full list.
"`!`"	Similar to the "`+`" character discussed above this permits invoking command lines with elevated privileges. However, unlike "`+`" the "`!`" character exclusively alters the effect of `User=`, `Group=` and `SupplementaryGroups=`, i.e. only the stanzas that affect user and group credentials. Note that this setting may be combined with `DynamicUser=`, in which case a dynamic user/group pair is allocated before the command is invoked, but credential changing is left to the executed process itself.
"`!!`"	This prefix is very similar to "`!`", however it only has an effect on systems lacking support for ambient process capabilities, i.e. without support for `AmbientCapabilities=`. It's intended to be used for unit files that take benefit of ambient capabilities to run processes with minimal privileges wherever possible while remaining compatible with systems that lack ambient capabilities support. Note that when "`!!`" is used, and a system lacking ambient capability support is detected any configured `SystemCallFilter=` and `CapabilityBoundingSet=` stanzas are implicitly modified, in order to permit spawned processes to drop credentials and capabilities themselves, even if this is configured to not be allowed. Moreover, if this prefix is used and a system lacking ambient capability support is detected `AmbientCapabilities=` will be skipped and not be applied. On systems supporting ambient capabilities, "`!!`" has no effect and is redundant.

Restart settings/Exit causes	`always`	`on-success`	`on-failure`	`on-abnormal`	`on-abort`	`on-watchdog`
Clean exit code or signal	X	X
Unclean exit code	X		X
Unclean signal	X		X	X	X
Timeout	X		X	X
Watchdog	X		X	X		X

802.1X und dynamische VLANs im WLAN mit Ubiquiti Unifi

Eine kurze Übersicht

Trennung per VLAN

Internet oder nicht?

Der genutzte RADIUS-Server

Installation von Freeradius

clients.conf

users

Manueller Test

Wie es nicht aussehen sollte

Wenn alles klappt

RADIUS-Server im Unifi Controller eintragen

Falls ein USG als RADIUS-Server genutzt wird

Geräte eintragen und zuweisen

Vorsicht mit Windows 10 und WLAN und dynamischen MAC-Adressen

Die Konfiguration eines WLANs

Fazit

Sie benötigten persönliche Unterstützung oder haben nicht die richtige Lösung für Ihr Problem gefunden?

Die berufliche Unabhängigkeit

Jan

+ 23 Kommentare:

Schreibe einen Kommentar Antworten abbrechen

Kategorien

Building Networks – Ihr professioneller Partner für IT und Infrastruktur

Microsoft Hyper-V – Das Handbuch

Schlagwörter

Sonstiges

Goal#

Copy Alpine to the SD Card#

Boot Alpine from the SD Card#

Install Alpine#

After the first reboot#

The last piece: make /var persistent#

A) Separate partition (or file)#

B) Bind mount#

C) Overlay mount#

Conclusion#

References#

Preparation

Installation

Post Installation

Update the System

Clock-related error messages

WiFi on boot

Enable Graphics

WiFi drivers

Persistent storage

Loopback image with overlayfs

Traditional disk-based (sys) installation

Persistent Installation on Raspberry Pi 3

Persistent Installation on Raspberry Pi 4

Troubleshooting

Long boot time when running headless

apk indicating 'No space left on device'

Wireless support with older Alpine images

See Also

setup-alpine

setup-hostname

setup-interfaces

setup-dns

setup-timezone

setup-proxy

setup-apkrepos

setup-sshd

setup-ntp

setup-disk

Partitioning

RAID

LVM

setup-lbu

setup-apkcache

setup-bootable

setup-xorg-base

Video packages (optional)

Input packages

Configure xorg-server (optional)

Keyboard Layout (optional)

Documentation needed

setup-xen-dom0

setup-mta

Goal

Copy Alpine to the SD Card

Boot Alpine from the SD Card

Install Alpine

After the first reboot

The last piece: make /var persistent

A) Separate partition (or file)

B) Bind mount

C) Overlay mount

Conclusion

References