Only that its a known issue. In open source world it is normal to see magnitude more issues then its resolving capacity. I'll look into when possible - its high on 2do list. No need.

Yes for sure, thank you. > lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 003: ID 2b89:8761 Realtek Bluetooth Radio Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 004: ID 0583:2060 Padix Co., Ltd (Rockfire) 2-axis 8-button gamepad > sudo dmesg | grep -i bluetooth [ 1.706048] usb 6-1: Product: Bluetooth Radio [ 4.360426] Bluetooth: Core ver 2.22 [ 4.360457] NET: Registered PF_BLUETOOTH protocol family [ 4.360460] Bluetooth: HCI device and connection manager initialized [ 4.360466] Bluetooth: HCI socket layer initialized [ 4.360469] Bluetooth: L2CAP socket layer initialized [ 4.360480] Bluetooth: SCO socket layer initialized [ 4.415023] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 4.417020] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 4.417027] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 4.417442] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [ 6.328832] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 6.328847] Bluetooth: BNEP filters: protocol multicast [ 6.328859] Bluetooth: BNEP socket layer initialized [ 870.557589] usb 6-1: Product: Bluetooth Radio [ 870.569776] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 870.571601] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 870.571614] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 870.571686] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [ 1246.745679] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 1246.747602] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 1246.747629] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 1246.747756] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [ 3667.259558] Bluetooth: RFCOMM TTY layer initialized [ 3667.259580] Bluetooth: RFCOMM socket layer initialized [ 3667.259595] Bluetooth: RFCOMM ver 1.11 [65689.757539] usb 4-1: Product: Bluetooth Radio [65689.769644] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [65689.771604] Bluetooth: hci0: RTL: rom_version status=0 version=1 [65689.771649] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [65689.771913] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin And here's a pastebin of the full dmesg output. https://pastebin.com/wMuX0bVW I got the driver files from here, https://github.com/Elif-dot/RTL8761BU uname Linux opi5 6.16.4-edge-rockchip64 #1 SMP PREEMPT Thu Aug 28 14:34:51 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux thanks

Thanks for the quick confirmation! From your answer I guess it is an issue that is already under investigation. No need to open a dedicated issue on some tracker, right?

Hi, although this topic is quite old, I was trying to bring this forward. I think I had a partial success on this. I've built an Armbian image with a newly created defconfig file. I took the DTB file from above. Result: the board seems to boot (SD card). The blue LED starts to blink (heartbeat). Ethernet is working, I can SSH into the box. USB seems to work, at least my Logitech Unifying Receiver is recognized Problem: there is no HDMI output. with dmesg | grep -i hdm I got the following output: [ 0.083861] /vop@fe040000: Fixed dependency cycle(s) with /hdmi@fe0a0000 [ 0.083981] /hdmi@fe0a0000: Fixed dependency cycle(s) with /vop@fe040000 [ 0.118236] /hdmi@fe0a0000: Fixed dependency cycle(s) with /hdmi-con [ 0.118360] /hdmi-con: Fixed dependency cycle(s) with /hdmi@fe0a0000 [ 4.671032] dwhdmi-rockchip fe0a0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (DWC HDMI 2.0 TX PHY) [ 4.675209] dwhdmi-rockchip fe0a0000.hdmi: registered DesignWare HDMI I2C bus driver [ 4.689857] rockchip-drm display-subsystem: bound fe0a0000.hdmi (ops dw_hdmi_rockchip_ops [rockchipdrm]) I dont know if this help. Maybe someone can assist? @Igoreverybody here honors and respects you and your work and your effort. We (or at least me) do not expect you to bring up one after another working image for all boards out there. What we do is asking for help to help ourselves. It is more than clear and obvious, that you are frustrated by the numerous apparent "requests" on one side and a massive lack of volunteering support on the other side. BUT: for US it is also sometimes frustrating, that you try to end all those threads like this by saying "STFU, RTFM". I am (and many more are) NOT those people, who just pass by to say "Hey Armbian, when do you finally support board XYZ?????????". Many of us TRY to contribute. But sometimes the tasks are just too hard to teach ourselves. You do this on a daily basis. But for "beginners" building the first linux image is so damn challenging and especially when you are alone on the battlefield (like when trying to bring an unsupported board to life). Yes, I read the docs. And yes, I already did before you restructured the build system. So asking for help is not intended to upset you. And still, I don't expect any support from your side. We try to come as far as possible on our own. But maybe there has been a time, when even you needed some guidance which involved a little bit more than RTFM... I respect and appreciate your work!

Correct. It's a problem of: https://github.com/armbian/os/blob/main/.github/workflows/complete-artifact-matrix-all-stable.yml and this configuration: https://github.com/armbian/os/blob/main/userpatches/targets-all-not-eos.yaml It is something to study