Creating a bug report/issue
I have searched the existing open and closed issues
Required Information
DietPi version | cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=6
G_DIETPI_VERSION_RC=1
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
Distro version | bullseye
Kernel version | Linux DietPi 6.9.5-edge-rockchip64
Architecture | arm64
SBC model | OrangePi 3b v2.1
Power supply used | ( 5V 2A RAVpower)
SD card used | (SanDisk ultra)
Steps to reproduce
Try enabling Bluetooth using built in DietPi Advance
menu
…
Expected behaviour
sudo bluetoothctl show
must list BT adapter
Actual behaviour
No default controller available
Extra details
Used rfkill
to unblock some stuff but no success
dietpi@DietPi:~$ sudo rfkill list
0: bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
dietpi@DietPi:~$ sudo rfkill unblock 0
[ 1798.373062] sdiohal err:wait scan card time out
[ 1801.444840] WCN_ERR: wait SDIO rescan card time out
[ 1801.450404] WCN_ERR: chip power on fail
[ 1801.454736] sdiohal err:sdiohal_runtime_put line 1756 not have card
Apparently others too having this issue & perhaps because DietPi
doesn’t have necessary drivers
dietpi@DietPi:/$ dmesg | grep WCN
[ 2.626458] WCN: marlin_init entry!
[ 2.627226] WCN: marlin_parse_dt chip_en gpio=27
[ 2.627664] WCN_ERR: gpio chip_en request err: 27
[ 2.628114] WCN: marlin_parse_dt reset gpio=79
[ 2.628552] WCN: wcn config keep power on
[ 2.628922] WCN: wcn config bt wake host
[ 2.629297] WCN: marlin_parse_dt bt-wake-host-gpio=80
[ 2.636947] WCN: marlin_probe ok!
[ 11.306720] WCN: marlin power state:0, subsys: [MARLIN_BLUETOOTH] power 0
[ 11.491247] WCN: start_marlin [MARLIN_WIFI]
[ 11.491680] WCN: marlin power state:0, subsys: [MARLIN_WIFI] power 1
[ 11.492261] WCN: the first power on start
[ 12.036221] WCN: start_marlin [MARLIN_BLUETOOTH]
[ 17.122388] WCN_ERR: wait SDIO rescan card time out
[ 17.122903] WCN_ERR: chip power on fail
[ 17.124476] WCN: marlin power state:0, subsys: [MARLIN_BLUETOOTH] power 1
[ 17.125152] WCN: no module to power on, start to power on
[ 22.754355] WCN_ERR: wait SDIO rescan card time out
[ 22.754869] WCN_ERR: chip power on fail
another reddit link
ls /lib/firmware/brcm
indicates bcm4345xx
missing … perhaps I will copy / paste from this github
Tried x2 solutions didn’t work
1] Disabled wifi but enable BT , then reboot
2] source
copy firmware/brcm at master · armbian/firmware · GitHub to /lib/firmware/brcm to solve this problem. now it works. Thank you for your attention to this matter
log:
root@DietPi:~# dmesg | grep -iE "blue|brcm"
[ 10.719052] -->rfkill_bluetooth_init
[ 10.720717] bluetooth_set_power: start_block=1
[ 10.724221] WCN: marlin power state:0, subsys: [MARLIN_BLUETOOTH] power 0
[ 10.724872] bluetooth_set_power: end_block=1
[ 10.725285] <--rfkill_bluetooth_init
[ 11.456199] bluetooth_set_power: start_block=1
[ 11.456240] WCN: marlin power state:0, subsys: [MARLIN_BLUETOOTH] power 0
[ 11.456255] bluetooth_set_power: end_block=1
[ 12.909003] brcmfmac: F1 signature read @0x18000000=0x15294345
[ 12.912874] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9
[ 12.914124] usbcore: registered new interface driver brcmfmac
[ 12.994114] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43456-sdio.rockchip,rk3566-orangepi-3b.bin failed with error -2
[ 13.072555] Bluetooth: Core ver 2.22
[ 13.072694] NET: Registered PF_BLUETOOTH protocol family
[ 13.072702] Bluetooth: HCI device and connection manager initialized
[ 13.072721] Bluetooth: HCI socket layer initialized
[ 13.072729] Bluetooth: L2CAP socket layer initialized
[ 13.072752] Bluetooth: SCO socket layer initialized
[ 14.114016] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 15.126193] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 357.687379] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 357.687405] Bluetooth: BNEP filters: protocol multicast
[ 357.687424] Bluetooth: BNEP socket layer initialized```
system
Closed
January 19, 2025, 10:54am
4
This topic was automatically closed 178 days after the last reply. New replies are no longer allowed.