Igor

Yes, and there is also PCI error before that - could be hw related. I was testing RPi Zero 2W and Rpi5 about two weeks ago and both WiFi worked OOB. Did you try booting our latest official image? We are using K6.12.y since last release and also if you build from sources now, it will be 6.12.y

@TonyB Tested - it works now as expected when installing this image https://dl.armbian.com/rpi4b/Bookworm_current_minimal-homeassistant Also tested other platforms with success: Khadas VIM1S x86 Nanopi M6

Firmware for BT was added https://github.com/armbian/firmware/commits/master/ while for enabling of CM4 refer to official instructions - what needs to be set in /boot/firmware/config.txt in order to get full functionality. This is the same as in official OS.

There are two things - from a quick log check - that are missing: - enabling "something" in the /boot/firmware/config.txt This can be an overlay telling to enable certain overlay specific for CM4 - firmware files (which are for Bluetooth): [ 6.374743] Bluetooth: hci0: BCM: firmware Patch file not found, tried: [ 6.374779] Bluetooth: hci0: BCM: 'brcm/BCM4345C0.raspberrypi,4-compute-module.hcd' [ 6.374787] Bluetooth: hci0: BCM: 'brcm/BCM4345C0.hcd' [ 6.374795] Bluetooth: hci0: BCM: 'brcm/BCM.raspberrypi,4-compute-module.hcd' [ 6.374802] Bluetooth: hci0: BCM: 'brcm/BCM.hcd' Let me check ...

With enabled everything in automatic upgrades. If kernel is not frozen, it will update too. If it's frozen (check with apt-mark showhold) find in the armbian-config to unfreeze it.

Let's ping Radxa engineers if they have a clue on this @RadxaYuntian otherwise I propose trying CURRENT kernel. That should be generally more reliable in those things.

Hardly without logs. Type: sudo armbianmonitor -u and provide URL.

OS is not involved into this, hardware interface (kernel) determines if things works or not and how well. We are using latest Rockchip kernel and this might work better in previous, still in use by Radxa. Guessing that you are using some 5.10.y or 6.1.75 ... since you forgot to tell the most important information Try with mainline based kernel 1st, https://docs.armbian.com/User-Guide_Armbian-Config/System/#install-alternative-kernels -> current , where such hardware usually works better. Or try older vendor kernels, that might be the same as in Radxa OS.

Make sure all parameters of /boot/firmware/cmdline.txt are one after another, in one line. This is correct way on a clean target: sed -i '/./ s/$/ systemd.unified_cgroup_hierarchy=0 apparmor=1 security=apparmor/' /boot/firmware/cmdline.txt I haven't done with all the testings and will continue tomorrow. I have to check major targets, not just Rpi.

I estimate few days, a week, if focusing just into this problem. "Officially supported" also needs someone to act as a maintainer https://docs.armbian.com/User-Guide_Board-Support-Rules/#standard-support On a long term, not just fixing current issue. Every kernel (boot-loader) change can break features partially or completely (boot failure).

It works. I messed up something. Just add that to the cmdline.txt and it should work - works for me. I am fixing now installation methods and testing to make sure everything is alright.

Run this as root: echo " systemd.unified_cgroup_hierarchy=0 apparmor=1 security=apparmor" >> /boot/firmware/cmdline.txt reboot This works for me (after adding this): Fixes: https://github.com/armbian/os/pull/289 https://github.com/armbian/configng/pull/466

Majority of firmware on Armbian images are developed from scratch and around mainline sources (dietpi only download Armbian, re-brand it to dietpi and "support" - they never fixed any common issues). Alternatively we could use Allwinner stack provided by Orangepi to achieve same hardware functional level, but in that case many other things won't be working (well). Static private kernels are in very poor state and not long term solution as nobody is going to maintain them. https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one Either use Orangepi fixed kernel or support development that happens at and around projects such as Armbian. We are spiting blood to make those boards working with modern kernel, without any help of this vendor. And very little, close to none, from end users. This is the main reason why things are not at the state you expect. It's a lot of work to get those devices working well and developers are humans with their needs.

which hardware platform / kernel ?

Try armbian-config way - drop your configs before.

This is not Armbian fault by any means. When you buy hardware, you mainly support hardware designers. Proper software support, that is yet to be developed by projects such as ours (with or without collaboration with hardware makers). This board was added to the Armbian build framework by vendor last week (!), which means its support is basic, bugs are expected and it only have community support status ATM: https://docs.armbian.com/User-Guide_Board-Support-Rules/ Probably this will fix it. https://github.com/armbian/build/pull/7903

Which most likely won't work on Wayland based Gnome desktop ... switching Gnome to X or using XFCE or similar is a way that this will work.

Armbian OS updates: - enable / disable kernel upgrades - switch between stable and rolling repository - enable automatic updating of Docker containers images - automatic packages updating enable + configure (unattended-upgrade)

Explanation and a fix that needs to be integrated https://github.com/armbian/build/issues/7896

Its a Trixie related bug (or some intentional splitting of package dependencies). Fixed: https://github.com/armbian/build/pull/7894

You need a VNC server that supports Wayland. Put that into Google search / ask AI.

We have many of such boards in the system Armbian mission is trying to keep them alive as long as possible. We invest a lot of efforts to keep them build-able, but there is just too many things that can go wrong in the u-boot / kernel area. Boards are constantly collapsing - if we want to keep them aligned with a modern kernel. The task is simply too big for our small team. We encourage people, owners of those (old) boards to step up and integrate those findings to the builds system, so this solution is available for everyone. We are running one mirror on Radxa ITX with success: https://www.armbian.com/newsflash/armbian-v24-11/ Software wise we are covering it well.

Nothing is planned unfortunately. It was a try if I can bring this from the dead in a couple of hours. I spent all the time I could afford to. In order to not go into the self-destruction path, we set a rules to ourselves: https://docs.armbian.com/User-Guide_Board-Support-Rules/ I can't maintain this board. It is one out of (perhaps 500 that are on the market, and one out of 100 that has some user base behind). If someone will help, and step up, to match the board support rules, this board can be lifted to standard support. It was dropped to community support about a year ago https://github.com/armbian/build/pull/6654 as we haven't heard it from its maintainer for a long time. We don't have any other alternative. I hope someone will take a look and integrate those changes into the build framework. Then we will at least a device into automated testing for early problem detections. They will certainly pop up in the future as they always does

Yeah. We have alias for neofetch that is borking this. Needs to find another way.

It depends. It might not work on weird private kernels (vendor v6.1.99), but it works on mainline based ones (<= 6.12) it has to. It works on Bookworm, while on Noble it will work tomorrow: https://github.com/armbian/os/pull/285 Test build succeeded: https://github.com/armbian/os/actions/runs/13486581225/job/37678541738