Werner

moved

Here and there things are sent upstream, but I am not aware of any defconfig changes that have been sent. So the answer is probably no. Also keep in mind that kernel configuration is one part only. Also other factors come into play like additional patches to the kernel regarding drivers or device tree.

You don't need the wireguard or wireguard-dkms package since all Armbian images ship the wireguard kernel module by default. All you need is the wireguard-tools package which you can install with the --no-install-recommends switch for apt which will prevent installing useless dependencies like kernels which wont work

Then go straight to dinner

Just for fun you could try an edge image for the board with btrfs. vendor is using a very old vendor-hacked uboot to make it work while edge follows mainline uboot which may have better btrfs support.

Ah. I guess at time of installation 6.6.y was current but since 6.12 is now available as new lts it has been moved to legacy. Therefore the name is different. Simplest to get matching packages is IMHO using the framework to create a set of packages and install them via dpkg.

Check how and why this kernel is installed: /boot/uInitrd-6.12.12+bpo-arm64-16k Seems like Debian backports kernel which WILL not work with your board. Make sure the vendor kernel is the only kernel installed. Write a fresh image to microsd and boot from it. chroot into your nvme and remove the wrong kernel. Make sure the symlinks to initramfs and kernel image are correct again. Should be sufficient.

next generation armbian-config still has some rough edges and constantly receiving fixes and improvements. If you can reproduce a special case where something doesnt work right, feel free to report at the github repo.

moved

code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } apt-cache search linux-headers If not there, use the build framework to create your own set of kernel packages including headers: https://docs.armbian.com/Developer-Guide_Build-Preparation/

Probably at April 1st 2026.

Could be. btrfs installation, especially on other devices, are not much tested. So breakage could be possible. Needs investigation. Should usually just work Yes, documentation is a constant problem. We don't have enough helping hands to keep everything in good shape. Keeping up with kernel development is already a challenge with hundreds of boards. Either the answer is right there or a mirror is out of sync which can happen from time to time. Feel free to fix apt source to a fixed mirror from this list: https://docs.armbian.com/Mirrors/

This error description leads nowhere. Hook up a debug serial console to get an idea what happens inside while the system does not boot. Share the logs here. Also verify powering and wiring. https://debug.armbian.de

Just like kernel features and drivers such overlays need to be developed to be shipped. So it is very likely that some/most/all overlays for various features are missing. If you need them, vendor kernel is the way to go for now.

dtb overlays are usually in /boot/dtb/rockchip/overlay

Check /boot/dtb/rockchip/overlay for available overlays. If you are using mainline kernel overlays might be missing. Use vendor kernel in this case. If armbian-config fails for adding simply add them manually with overlays= in /boot/armbianEnv.txt

moved to beginner. User seems unsure which board they actually use (r6s vs 5rc).

If there are no pre-built version available, use the build framework to create your own: https://docs.armbian.com/Developer-Guide_Build-Preparation/

This is more or less expected for current since the HDMI implementation in this LTS version is very basic/incomplete. Features were and still are in development and did not make it into this version. If you need desktop use edge or vendor.

armbian-config is still able to handle overlays, though in some cases it might not works. Not an issue though since it can be easily done manually as well. Check /boot/dtb/rockchip/overlay for the available overlays. You need the rk3588 ones. Check if the overlay_prefix in /boot/armbianEnv.txt is correct. Might be necessary to change to rockchip. Then simply add the overlays you want like this (example): overlays=rk3588-i2c8-m2

moved

the bootloader needs to be installed on emmc separately. armbian-install usually takes care of that. How to debug boot issues: https://debug.armbian.de

https://debug.armbian.de

Github build repository is only for framework bugs, building Armbian to say. Firefox is userspace and issues when running Armbian are to be reported here in forums.

We can discuss including this into CLI/desktop images. Not for minimal.