Werner

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.

split into new topic due to off-topic

https://github.com/armbian/build/blob/main/config/boards/bigtreetech-cb2.conf Config is there. If there is no pre-made build available use the framework to create your own. This is what it's made for.

The driver seems to be already included. If I check my kernel (vendor rk35xx) config I see CONFIG_VIDEO_OV13855=y.

Alright, didn't know they are still there. Well as mentioned media won't receive any further updates since all functionally is merged into standard branches. Anyway, Rock64 is rk3399 I think and you should be good to go with mainline kernel, either current which is 6.12.y or edge which is 6.14-rc7 atm. The branches at https://github.com/armbian/linux-rockchip are made from Rockchip BSP code and mostly for rk35xx socs. I don't think there is much work there for rk3399.

moved Where did you get those? media branch has been abandoned for over a year now.

moved

Hi this warning tells you that it is up to you to do a risk assessment if you are fine with the fact, that the device's status is unknown to the Armbian team, that it may break with an upcoming update or never receive an update at all.

Alright. Yes, there seems to be some issue with the naming of the overlays which required editing armbianEnv by hand. It is hard to keep up with the continously changing world of SoCs and kernels where latter, especially on mainline, often even lacking basic overlays since close to nobody deals with this.