Conversation
Release v10.5
Bumps [actions/checkout](https://github.com/actions/checkout) from 6 to 7. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v6...v7) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Required since v0.44.0 for the newly used Argon2 password hashing algorithm via argon2-cffi.
We moved the overlay_error declaration into the overlay loop and removed support for generic fixup scripts.
Co-authored-by: MichaIng <micha@dietpi.com>
The package does not start it if installed from dietpi-software.
* dietpi-software: Immich: updates for v3 release * dietpi-software: Immich: update plugin filters and dirs * Revert "dietpi-software: Immich: updates for v3 release" This reverts commit 4605901.
The $version variable needs to remain untouched, or we'd need to store a dedicated variable for the build dir.
Packages were removed upstream.
The Trixie packages depend on fuse2, which was removed from Forky in favour of fuse3.
The key expired at the behinning of June, and Raspbian Trixie + Debian Testing suites are available now.
The Debian Testing packages still depend on fuse2. And the suite is available for amd64 only.
Until Forky, it is pulled in by some essential package(s). From Forky on, only by ifupdown, which is not installed on our container images.
Even if nothing needs to be compiled, extracting the wheels into `/tmp` takes ~600 MiB space. 2 GiB memory results in a 1 GiB `/tmp` on DietPi, which is usually sufficient with some buffer.
The fix has been merged + released by Debian.
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 6 to 7. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](actions/setup-python@v6...v7) --- updated-dependencies: - dependency-name: actions/setup-python dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…eleases (#8217) Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: MichaIng <micha@dietpi.com>
`dietpi-config` uses `/etc/modprobe.d/dietpi-disable_bluetooth.conf` as flag about whether Bluetooth is enabled or not. Since v10.5 we do not create it anymore on all systems, so that Bluetooth in those cases kept showing as enabled, hence could not be actually enabled anymore either. This commit re-adds `/etc/modprobe.d/dietpi-disable_bluetooth.conf` in every case, it might just remain empty. It is no elegant solution, but works, until we have a better idea how to detect whether Bluetooth is enabled or not, like the `bluez` package, or service. Or use rfkill, to block Bluetooth on a lower level, no matter which adapter/driver is loaded (almost, `sprdbt_tty` on Allwinner does not support rfkill).
systemd v261 seems to have solved the "Inappropriate ioctl for device" issue on `/dev/console` == `/dev/pts/0` when QEMU-emulation is used. Context about the underlying issue that was fixed: - https://lists.nongnu.org/archive/html/qemu-devel/2026-01/msg03649.html - https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/2133804 - https://gitlab.com/qemu-project/qemu/-/work_items/3065
None if these arguments is interpreted by mainline Linux, and support for none of these is patched by Armbian into mainline Linux. The device tree nodes to disable HDMI and the VPU do not exist in mainline Linux either. The VU7 touchscreen might still work and might still require the USB quirk, but it is very unlikely. Remove for now until someone asks for it. Remove "rw" cmdline flag. This is pretty wrong to use, as the kernel/initramfs should always mount the rootfs R/O. systemd-remount-rootfs.service is responsible for the R/W remount, after certain initial boot stages.
This additioanlly updates overlay prefixes for all Rockchip SBCs: - Remove `rockchip` prefix, as long as any other is given for each kernel branch. - Replace `rockchip-rk3568` prefix with `rockchip-rk3568-hk`, which contains very generic overlays. - Add `rockchip-rk3566` prefix for all RK3568 boards (as it is vice versa), since both prefixes complement each other without overlaps. - Add `rockchip-rk3568-rock-3a` prefix for ROCK 3A. This also fixes wrong serial console devices for Rockchip SBCs which have been switched from vendor to mainline Linux recently.
This patch was added when not all RPi images were forced to have the modern kernel stack yet, hence the boot partition might still have been mounted at /boot rather than /boot/firmware. The migration script did create a symlink for config.txt, so that /boot/config.txt remained valid. However, in the meantime, the migration script does not create the symlink anymore, and that code explicitly checks whether the raspi-firmware package is installed already, so that the /boot/firmware mount must exist. So it makes sense to check config.txt in its modern kernel stack location.
If it is not reset after a "Full" benchmark, a custom filesystem benchmark will take `/dietpi-benchmark_testfile` as target directory, and skip the mount point selection menu.
Show actual test file path in results dialog.
It uses a better non-linear algorithm to calculate a proper write cache.
…ages Dropbear is not preinstalled on container images, but `AUTO_SETUP_SSH_SERVER_INDEX` as well as `aSOFTWARE_INSTALL_STATE[104]` indicated it is. Since we plan to implement sopport for pre-installing software via `dietpi-software` within `dietpi-installer`, pre-seeding `/boot/dietpi/.installed` works already. Hence make use of this to indicate the correct install states.
- Changed custom entry to accept multiple commands - Added network usage by namespace - Added disk usage by pattern matching - Added systemd and fail2ban status - Standardized printing - Organized color resources - Added G_TRUNCATE_MID Co-authored-by: MichaIng <micha@dietpi.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Beta v10.6.0
(2026-08-03)
New images
Enhancements
@rouiljfor reporting the issue with one of these: https://dietpi.com/forum/t/25290/boot/dietpi/.dietpi-banner. The number of colour codes has been extended, using easier to remember named array indices. Many thanks to @timjolson for implementing these features: dietpi-banner: enhance and add new banner options #8172Bug fixes
@vlixand@tigerskyfor reporting this issue: https://dietpi.com/forum/t/24902, https://dietpi.com/forum/t/25296@Totof, and many others for reporting the issue and testing many attempts to fix it. And many thanks to @EvilOlaf from Armbian for helping with debugging, and moving the driver from a complex patch series into a dedicated GitHub repository: OrangePi Zero 2W - Kernel Oops During Downloads #8220/dietpi-benchmark_testfiledirectory was unintentionally created, if a "Full" benchmark was done first, and a "Custom Filesystem" Benchmark afterwards, for which no mount selection menu was shown either.dietpi-software reinstall 215 216, which includes Immich Machine Learning, (only) if installed.