Devuan Chimaera on Raspberry Pi 4B with encrypted root file system

Image : https://arm-files.devuan.org/devuan_chi … i4.img.zip (SHA256 239e7dbfe0f27eaa2305fefcfca2f9838c65d90828892cdd96aed8bd76c743b)

The installation was based on instructions by Andreas Hug: https://andreashug.medium.com/raspberry … 7e680fc8d5. The most significant changes were omitting the logical volume manager, using a second SD card with NOOBS instead of shuffling partitions on the primary SD card, and encrypting with Adiantum+Argon2i instead of AES+SHA256.

Overall a success except for the small issues below:

• When starting the system for the first time, the framebuffer resolution was too high. Only a small part of the console output was visible and the setup seemed to be hung. There was a visible restart counter ("restart: 6/-1" before pulling the plug) and the lower bottom part of a QR code was visible in the upper right corner of the screen. The fix was to manually set the framebuffer resolution in `/boot/config.txt` (`framebuffer_width`, `frambuffer_height`).

• The SD card could not be mounted after this. The SD card is brand new and after copying the Devuan image a second time on the SD card, there were no further mounting problems. `dd conv=fsync` was used both times.

• The second partition with the root file system was not aligned to a 4096 byte boundary.

• Making Wi-Fi work was annoying. The rfkill was obvious to fix but afterwards both connman (error message `Error /net/connman/technology/wifi: No carrier`) and network-manager (no visible access points when iwlist saw them) did not work. Removing connman and adding the Wi-Fi name and password in `/etc/wpa_supplicant/wpa_supplicant.conf` lead to Wi-Fi access.

• The country in `wpa_supplicant.conf` was wrong, even after setting up locales.