Ubuntu develop image from OOWOW
How can I confirm if my bluetooth hardware is broken, none of the os’s I have installed have bluetooth. I have tried armbian and ubuntu, but I cannot enable bluetooth in Gnome. Also unavailable on FydeOS
Hello @Egert
Have you installed the antenna?
Hello @ivan.li
Yes I have attached these antennas, wifi works okay, bluetooth used to work.
I disconnected the antenna and reattached it, but no change unfortunately. I looked at the photos online to confirm that my antennas are also connected as intented.
Hello @Egert
The antennas has better to attach before SBC boot. Hot-plug will cause something unexpected.
I disconnected the antenna and reattached it, but no change unfortunately.
By the way, may I know the reason?
I was just testing if perhaps my antenna was not properly attached to the board. That is why I removed and reconnected it.
Hello @Egert
When you disconnect the antenna, wait for a while and the Bluetooth device list will change.If the antenna is not connected, there is a high probability that other Bluetooth devices will not be found.
In my case, I cannot even enable bluetooth.
I get this message “Bluez daemon is not running”
Hello @Egert
Burn the firmware below. If Bluetooth is not available yet, I need you to provide some log information.
khadas@Khadas:~$ dmesg | grep Bluetooth
Hi @ivan.li
I am not able to boot up this image. I tried installing it through oowow, but after reboot i get into oowow and not ubuntu os.
I tried khadas@Khadas:~$ dmesg | grep Bluetooth
With a different ubuntu image, but I get no output, so I guess bluetooth hardware is not recognized. Where bluetooth is located on the board, perhaps I have damaged it?
Hello @Egert
1.Please try again 
http://docs.khadas.com/products/sbc/edge2/install-os/install-os-into-emmc-via-usb-tool
2.The largest module in the picture below
Hi @ivan.li
I got it running now using the rkdevtool. Unfortunately no bluetooth. I will check if I can see any damage on my board that could be the issue.
Hi @ivan.li, did you manage to resolve your bluetooth issue? I have the same problem. Recently installed Ubuntu 24.04 on my Edge 2, and I’ve just installed it in to a case with new antennas. WiFi working, but no bluetooth. Took it apart again, reconnected the antennas, same issue. I’m wondering if Ubuntu doesn’t have the necessary driver for the bluetooth chip.
Hello @tonybaynes
Can you check the latest image (edge2-ubuntu-24.04-gnome-linux-6.1-fenix-1.7.2-241022.img.xz)? Bluetooth should work.
Hi numbqq, I did as you suggested and I’m very pleased to report that this has solved my issue. Thank you! My Edge 2 now has Bluetooth working perfectly. All I did was reinstall the version of Ubuntu that you suggested.
there are issues between the image file contents.. and the repositories’ files available.. ive bounced from Rockchip’s direct, linux kernel, khadas, noone seems to patch the correct combination of files and or settings to repair this if it screws up or gets messsed with via some other software installs. Ive been trouble shooting this issue for a week now with AI scouring the net for solutions.. and this is the closest Ive got now to getting the bluetooth functional again. the work i put into this OS build.. reinstalling the OS is not an option.. : Alright, here’s what your logs are screaming:
You can create hci0 via btattach, but it’s a zombie: BD Address: 00:00:00:00:00:00, MTUs 0 → firmware never loaded.
Bluetooth: hci0: Opcode 0x0c03 failed: -110 = the controller never answered HCI Reset → usually wrong UART params or the chip’s still in ROM/boot mode because no proper patchram.
Your BCM4375C2.hcd is BRCMcfg-style (you can see BRCMcfgS/D and "BCM4375B1 UART 37.4MHz Ampak AP6275HH3" in the hexdump). Many distro brcm_patchram_plus builds don’t understand that container → the “file not an HCD file” you saw.
Kernel 6.1.118 has hci_uart.ko, but no hci_bcm: modprobe hci_bcm fails and /lib/modules/.../drivers/bluetooth only shows hci_uart.ko. Without hci_bcm, the kernel won’t do GPIO power/baud dance or firmware load for you.
So you’re stuck between:
a userspace loader that can’t parse the BRCMcfg blob, and
a kernel missing the hci_bcm driver that normally handles Broadcom/CYW BT bring-up.
