Skip to content

Release Notes

July 2024 (version 9.6)


The July 7th, 2024 release of DietPi v9.6 comes with new the new software package soju (an IRC bouncer) and further enhancements resp. bug fixes.

Orange Pi Zero 3 on ilex

Orange Pi Zero 3. Photo by StephanStS, DietPi

New software


  • General Since we provide all kernel, bootloader and firmware packages from our own APT repository now, the Armbian APT repository is removed from all systems. In case you use an SBC which is not officially supported by DietPi, as generic device, it is however preserved.
  • Quartz64/Star64/VisionFive 2 The extended attribute handler for ext4 security labels CONFIG_EXT4_FS_SECURITY has been enabled for these SBCs, required for some Docker containers. Many thanks to @gxsw for reporting this missing feature: MichaIng/DietPi#7102
  • Quartz64/Star64/VisionFive 2eBPF functionality for firewall and network monitoring software like Cilium has been added to our kernel builds for these SBCs. Many thanks to @kbrighton for reporting these missing features: MichaIng/DietPi#6834
  • Orange Pi 5 Older U-Boot builds caused the Ethernet MAC address to be random and change on every boot. Recent U-Boot builds solve this, but they are not flashed automatically on package upgrades. We hence inform users and offer to flash the latest U-Boot image during the DietPi update. Many thanks to @thuehlinger for reporting and testing the case: MichaIng/DietPi#6663
  • DietPi-Config enhancements Legacy Odroid C2 resolution and GPU memory options have been removed.
  • DietPi-Config enhancements The static DNS server menu now contains entries to select the default gateway/router or locally running DNS resolver (Pi-hole, AdGuard Home, Unbound, systemd-resolvd, …), if detected.

Bug fixes

  • Network | Resolved a rare issue, where shutdowns could hang, when networking.service and ifup@.service instances try to bring down the same network interface concurrently. Many thanks to @ioctl2 for reporting this issue: MichaIng/DietPi#7104
  • Odroid C1 Resolved an issue, where the kernel upgrade did not apply as intended. Many thanks to @th2j for reporting this issue:
  • VisionFive 2 Resolved an issue where our new image did not boot, because of a false device tree name in /boot/extlinux/extlinux.conf.
  • NanoPi R6C Resolved an issue where our new images did not boot, since the latest mainline U-Boot for R6S does not support the R6C anymore. Many thanks to @labmaster for reporting this issue: MichaIng/DietPi#7109
  • DietPi-Tools | DietPi-Banner Resolved an issue where incorrect RAM usage was printed with German and potentially other locales. Many thanks to @jwgn for reporting this issue: MichaIng/DietPi#7107
  • DietPi-Tools | DietPi-Banner Resolved an issue where logins as non-root user printed “No certificate found” if the Let’s Encrypt cert status option was enabled, since non-root users have no permission to see the certificate files. In such cases, sudo is now used automatically, if the user has NOPASSWD permissions, else a meaningful info is shown. Many thanks to @FrapiFrance for implementing this fix: MichaIng/DietPi!7121
  • DietPi-Tools | DietPi-Drive_Manager Resolved an issue, where network drives and potentially mounts in general could be attempted to be unmounted on shutdown, before services which can access them are stopped, leading to hanging shutdown sequences and potentially even data loss. Many thanks to @polite-garlic for reporting this issue:
  • DietPi-Software | DietPi-Dashboard Resolved an issue where the installation on RISC-V systems failed.
  • DietPi-Software | Node-RED Resolved an issue where reinstalls/updates failed because of incompatibilities between latest Node.js or global modules with older local instances. Many thanks to @thinkbig1979 for reporting this issue: MichaIng/DietPi#7128
  • DietPi-Software | Fail2Ban Resolved an issue on Debian Bookworm and above, where Dropbear login failures were not detected due to a non-matching default filter. Dropbear runs as native systemd unit since Bookworm, logging to the system journal via STDOUT, which results in a different log entry prefix. The default filter however has not been updated for this. The fix is as well applied to existing Fail2Ban installs, as long as no own override /etc/fail2ban/filter.d/dropbear.local has been created. Many thanks to @ThePlanplan for reporting this issue: MichaIng/DietPi#6665

As always, many smaller code performance and stability improvements, visual and spelling fixes have been done, too much to list all of them here. Check out all code changes of this release on GitHub: MichaIng/DietPi!7142