You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Images | DietPi images are now shipped with a trailing FAT partition which contains dietpi.txt and other config files for easier pre-configuration and automation from Windows and macOS hosts. The partition is removed automatically on first boot, after copying all supported config files/scripts. Related CLI flags have been added to our build scripts: --add-fat-part for dietpi-imager and --no-fat-part for dietpi-build. Many thanks to @dirkhh for implementing this feature: DietPi-Imager | Add option to add FAT partition after rootfs to simplify setup #6602
Images | All our images are now compressed via xz instead of 7z. These are a little easier to handle, especially on Linux hosts, and many flashing utilities allow to flash zx-compressed images directly to disk, without the need to manually decompress them first. As xz compresses files and no directories, the dedicated README.md and hash text files are not included anymore. The hashes for integrity checks within an archive have no real purpose, as the compression algorithms imply hashes internally (CRC64 in case of xz), which are checked and integrity of the content assured as part of the decompression.
Images | Most of our images, those with do not ship with a very old Linux version, have no entropy daemon pre-installed anymore. Either rngd or haveged were required previously to assure that the system entropy pool remained sufficiently filled, otherwise boot, service starts, cryptography tasks or anything using random character from /dev/random could have hung. Recent Linux versions however fill the entropy pool from hardware random generators sufficiently by themselves, and have a HAVEGE-like fallback as well if no hardware random generator is available.
DietPi-CloudShell | The date/time output format at the top of every 3rd scene is now localised.
DietPi-Software | Docker: Enabled for Trixie and RISC-V via docker.io package from Debian repository.
DietPi-Software | Portainer: Enabled for RISC-V as Docker is now supported on RISC-V as well.
Orange Pi 5 | Resolved a v8.21 regression where the update may have lead to an unbootable system or caused other issues like missing HDMI output, because of a falsely set device tree file name.
Odroid C1 | Resolved an issue where the latest kernel upgrade broke boot of the Odroid C1. We do now pin, in case downgrade, and set on hold "current" and "edge" kernel packages of Armbian to v23.02.2 (Linux 5.15.93 respectively 6.1.11) with this DietPi update, which are the latest known functional packages for this SBC. Many thanks to @oskar242000 for reporting this issue: https://dietpi.com/forum/t/odroid-c1-not-booting-after-kernel-upgrade/17818
Bookworm | Resolved an issue where poweroff/reboot/halt commands did throw errors about missing dbus or logind. DietPi ships without dbus and with logind masked by default, as we do not see their features being used on a typical DietPi system. Instead, dbus is installed and logind unmasked on demand on certain software installs or when chosen via dietpi.txt. However, the newer systemd version since Bookworm attempts dbus > logind communication in any case when calling poweroff/reboot/halt, despite no wall message being sent, e.g. to handle shutdown inhibitors (like open SSH session being able to prevent shutdown), and throws errors if either dbus is not reachable or logind not running. Until in case dbus or logind are further tied into common system commands or features, we solved the issue by creating shell functions for poweroff/reboot/halt which call the respective systemd target directly to bypass logind (and hence dbus), but fall back to the original commands, depending on given command-line parameters.
dietpi-bookworm-upgrade | Resolved an issue on systems with Armbian repository, where the system was still identified as Bullseye after the distribution upgrade to Bookworm. Reason was Armbian's base-files package, which was not upgraded as intended. On all DietPi systems, the original base-files package from Debian will now be enforced to prevent this and similar issues. Many thanks to @rogerthn2019 for reporting this issue: Debian Bookworm testing and upgrade script feedback #6227 (comment)
DietPi-Software | Bazarr: Resolved an issue where the installation failed on ARMv6 and ARMv7 Bullseye and Bookworm systems, since some pre-compiled Python modules are currently not available on piwheels, due to the currently running prioritised builds of all modules for Bookworm.
The text was updated successfully, but these errors were encountered:
How to apply: https://github.com/MichaIng/DietPi/blob/master/BRANCH_SYSTEM.md
Related/solved issues: https://github.com/MichaIng/DietPi/issues?q=is%3Aissue+milestone%3Av8.22
Beta v8.22.3
(2023-09-23)
New software
Enhancements
dietpi.txt
and other config files for easier pre-configuration and automation from Windows and macOS hosts. The partition is removed automatically on first boot, after copying all supported config files/scripts. Related CLI flags have been added to our build scripts:--add-fat-part
for dietpi-imager and--no-fat-part
for dietpi-build. Many thanks to @dirkhh for implementing this feature: DietPi-Imager | Add option to add FAT partition after rootfs to simplify setup #6602README.md
and hash text files are not included anymore. The hashes for integrity checks within an archive have no real purpose, as the compression algorithms imply hashes internally (CRC64 in case of xz), which are checked and integrity of the content assured as part of the decompression.rngd
orhaveged
were required previously to assure that the system entropy pool remained sufficiently filled, otherwise boot, service starts, cryptography tasks or anything using random character from/dev/random
could have hung. Recent Linux versions however fill the entropy pool from hardware random generators sufficiently by themselves, and have a HAVEGE-like fallback as well if no hardware random generator is available.docker.io
package from Debian repository.Bug fixes
@oskar242000
for reporting this issue: https://dietpi.com/forum/t/odroid-c1-not-booting-after-kernel-upgrade/17818poweroff
/reboot
/halt
commands did throw errors about missingdbus
orlogind
. DietPi ships withoutdbus
and withlogind
masked by default, as we do not see their features being used on a typical DietPi system. Instead,dbus
is installed andlogind
unmasked on demand on certain software installs or when chosen viadietpi.txt
. However, the newer systemd version since Bookworm attemptsdbus
>logind
communication in any case when callingpoweroff
/reboot
/halt
, despite no wall message being sent, e.g. to handle shutdown inhibitors (like open SSH session being able to prevent shutdown), and throws errors if eitherdbus
is not reachable orlogind
not running. Until in casedbus
orlogind
are further tied into common system commands or features, we solved the issue by creating shell functions forpoweroff
/reboot
/halt
which call the respective systemd target directly to bypasslogind
(and hencedbus
), but fall back to the original commands, depending on given command-line parameters.The text was updated successfully, but these errors were encountered: