[SOLVED] Unable to use onboard bluetooth on Pi Zero 2 W (due to a defective board)

[jenzd]

Try a fresh 7.6.0 image. The file exists at the location below.

Code:

pi@moode:~ $ stat /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.bluez.service
  File: /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.bluez.service
  Size: 0               Blocks: 0          IO Block: 4096   regular empty file
Device: b302h/45826d    Inode: 44911       Links: 1
Access: (0644/-rw-r--r--)  Uid: (    0/    root)   Gid: (    0/    root)
Access: 2020-12-02 07:55:44.310775210 -0500
Modify: 2020-12-02 07:41:08.830137566 -0500
Change: 2020-12-02 07:55:44.310775210 -0500
 Birth: -

Tried again with a fresh 7.6.0 image (double checked MD5 checksum) using rufus to transfer the image to the SD card. No additional devices connected to the Raspberry Pi - only the official power supply. And did exactly the following:

1) Connect to the device via WLAN (AP mode - SSID "Moode").
2) Open a ssh session to 172.24.1.1 and run "tail -f /var/log/syslog" to watch the log.
3) Switch on bluetooth renderer via web interface.

Result: I got the same error messages as already posted.

Code:

Dec  5 02:28:42 moode systemd[1]: Starting Configure Bluetooth Modems connected by UART...
Dec  5 02:28:42 moode kernel: [  651.551453] uart-pl011 3f201000.serial: no DMA platform data
Dec  5 02:29:12 moode btuart[1759]: Initialization timed out.
Dec  5 02:29:12 moode btuart[1759]: bcm43xx_init
Dec  5 02:29:12 moode systemd[1]: hciuart.service: Control process exited, code=exited, status=1/FAILURE
Dec  5 02:29:12 moode systemd[1]: hciuart.service: Failed with result 'exit-code'.
Dec  5 02:29:12 moode systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.
Dec  5 02:29:12 moode systemd[1]: Condition check resulted in Bluetooth service being skipped.
Dec  5 02:29:13 moode systemd[1]: Condition check resulted in Bluetooth service being skipped.
Dec  5 02:29:13 moode systemd[1]: Started BluezAlsa proxy.
Dec  5 02:29:13 moode dbus-daemon[305]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.15' (uid=0 pid=1817 comm="/usr/bin/bluealsa -p a2dp-source -p a2dp-sink ")
Dec  5 02:29:13 moode dbus-daemon[305]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service not found.
Dec  5 02:29:13 moode bluealsa[1817]: /usr/bin/bluealsa: W: Couldn't get managed objects: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.

By the way I also had a look at

Code:

stat /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.bluez.service

which exists and shows the same result as you posted above.

Very strange. Maybe I have a defect device?