Skip to content

LordOS 0.8.4.1-beta

Pre-release
Pre-release

Choose a tag to compare

@lordbasex lordbasex released this 25 Oct 17:25
· 1609 commits to main since this release

An update of 0.8.4 for the Raspberry Pi 5: its bootloader from Settings, and a new Pi image with the HDMI fix, the browsers and the ISO's system packages (0.8.4 held its Pi image back).

Added

  • Settings → Board firmware (Raspberry Pi 5). A new page, only on a Raspberry Pi 5 (and Pi 500, Compute Module 5), for the bootloader that lives in the board's EEPROM: the installed version, the newest one available, whether it is up to date, and Update. After updating it says a restart finishes the job and offers Restart…; the board installs the new bootloader as it starts, keeping its recovery path. This is LordOS's replacement for the bootloader part of raspi-config (ignore rpi-eeprom-update's hint to run it). It runs only the system's rpi-eeprom-update with a fixed set of options, through two closed admin actions: reading the status is open to everyone, updating needs an administrator (docs/SETTINGS.md, "Board firmware").
  • The bootloader updater in the LordOS repository. rpi-eeprom (the bootloader images and rpi-eeprom-update) and the few Raspberry Pi packages it needs (raspi-utils and its parts, raspinfo, kms++) are now mirrored in lordos.org/apt for arm64, copied from Raspberry Pi's archive only after its signature and every file's SHA-256 check out against a pinned list (tools/release/rpi-mirror.list). A Pi with only the LordOS and Debian repositories gets new bootloaders with the usual updates; PCs never see these packages (docs/UPDATES.md, "Raspberry Pi firmware packages").
  • Browsers in the Raspberry Pi image. Chromium and Firefox ESR come preinstalled, as on the ISO, with the same defaults: a single bar with their tabs and LordOS's window buttons, the LordOS GTK theme and the video settings of Settings → Displays → Video (the defaults are now one script shared by both images, tools/iso/browser-defaults.sh).
  • The rest of the ISO's system packages in the Pi image: automatic time (systemd-timesyncd), printing (cups, avahi-daemon), exFAT and NTFS drives, power profiles, the MIME database and the GTK settings schemas. The first user is also allowed to manage printers (lpadmin), as on a PC.

Fixed

  • Raspberry Pi 5 on an HDMI monitor stayed on the text console ("no display device with KMS"). The firmware ignored the display driver line in the image's config.txt because it came before the display_auto_detect and camera_auto_detect lines; it now comes after them. Together with 0.8.4's longer wait for the display driver, the desktop shows on HDMI at the first boot.
  • The Pi image's clock. The board keeps no time without a battery and the image had no network time client, so it started months behind and every update failed with "not valid yet". It now sets the time from the network at boot.

Known issues and limitations

  • A monitor plugged in after boot stays black until the board is restarted: the login screen doesn't follow the kernel's display events yet. Connect the HDMI monitor before switching the board on. Fixed for 0.8.5.
  • A Pi set up from the 0.8.3 image has no network time client: if Store → Updates fails, set the time in Settings → Date & Time first, then install systemd-timesyncd from the Store.
  • The bootloader release (Default or Latest) is shown but not changed from Settings: it is /etc/default/rpi-eeprom-update, a file of the rpi-eeprom package.
  • Raspberry Pi archive on the Pi image. The image still lists Raspberry Pi's archive, limited by apt priorities to the firmware, kernel tools and utilities; the Store's own package engine does not read apt priorities yet, so "Update all" there may take Raspberry Pi's builds of a few packages (such as Chromium or BlueZ) instead of Debian's. apt follows the priorities.
  • install.sh does not install browsers (on a Raspberry Pi OS Lite or any Debian 13): install Chromium or Firefox ESR from the Store if the system has none (docs/INSTALL-DEBIAN.md).

Upgrading

  • From 0.8.4 (and 0.8.3 to 0.8.1): Store → Updates shows "LordOS 0.8.4.1 is available" with these notes; Update installs it and a restart finishes it. sudo apt update && sudo apt upgrade does the same. No migration runs (ls /var/lib/lordos/migrations is unchanged from 0.8.4); your settings are kept. On a PC nothing else changes.
  • Raspberry Pi 5: after the update, Settings shows Board firmware. If it says "The bootloader tools are not installed", Install adds rpi-eeprom from the LordOS repository. The browsers and the other image packages above are not added to a board that is already set up: install them from the Store.

Downloads

The packages and a new Raspberry Pi 5 image (checked on an HDMI monitor). The live ISO and the LordOS Imager of 0.8.4 stay current (an installed system updates itself to 0.8.4.1); the Imager offers this Pi image on its own.

File What it is
lordos-0.8.4.1-rpi5-arm64.img.xz Image for the Raspberry Pi 5, for the LordOS Imager or any image writer app, an SD card or an NVMe drive.
lordos_0.8.4.1_amd64.deb The LordOS package for an existing Debian 13 on a PC (installed by install.sh, or with apt install ./…).
lordos_0.8.4.1_arm64.deb The same package for Debian 13 on arm64.
install.sh The one-line installer for Debian 13: curl -fsSL https://lordos.org/install.sh | sh. It checks the signature before installing.
SHA256SUMS The SHA-256 of every file in this release.
SHA256SUMS.sig The Ed25519 signature of SHA256SUMS with the LordOS release key (base64).
lordos_0.8.4.1_<arch>.spdx.json Software bill of materials (SPDX 2.3) for each package: what it bundles and the Debian packages it depends on.

Verifying the downloads

The LordOS release public key is lordos-release.pub.pem (in the repository, or at https://lordos.org/lordos-release.pub.pem). Its fingerprint, the SHA-256 of the DER public key, is:

c7155b8e6bbbb180f907381994d06af76d333016cd6f3facf67cadd053ea108e

With OpenSSL 3, in the folder with the downloads:

openssl pkey -pubin -in lordos-release.pub.pem -outform DER | sha256sum   # must match the fingerprint
base64 -d SHA256SUMS.sig > SHA256SUMS.sig.bin
openssl pkeyutl -verify -pubin -inkey lordos-release.pub.pem -rawin -in SHA256SUMS -sigfile SHA256SUMS.sig.bin
sha256sum -c --ignore-missing SHA256SUMS

"Signature Verified Successfully" and "OK" for each downloaded file mean the files are the ones we published. Details: docs/SIGNING.md.

Links