No Bluetooth adapter with Raspperry Pi Zero W

[SetZer0]

Hello,

I have installed Kali Linux in my Zero W box from the default repository (https://www.offensive-security.com/k...nux-arm-images). I tested all these images for 2019.2 below:

1. Kali Linux RPi0w Nexmon P4wnp1 Aloa
2. Kali Linux RPi0w Nexmon
3. Kali Linux RPi

Right now I am using option 3, because of its full rich (desktop) feautures. Everything is working fine, except bluetooth. When I perform 'hciconfig', there is no adapter present. Here are some logs:

root@xxx:~/Bluetooth# uname -a
Linux xxx 4.19.29-Re4son+ #6 Wed Mar 27 17:20:18 AEDT 2019 armv6l GNU/Linux 

root@xxx:~/# dmesg | grep Blue
[   49.979503] Bluetooth: Core ver 2.22
[   49.979691] Bluetooth: HCI device and connection manager initialized
[   49.979722] Bluetooth: HCI socket layer initialized
[   49.979742] Bluetooth: L2CAP socket layer initialized
[   49.979796] Bluetooth: SCO socket layer initialized 

root@xxx:~/Bluetooth# systemctl enable bluetooth && systemctl enable hciuart
Synchronizing state of bluetooth.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable bluetooth
Failed to enable unit: Unit file hciuart.service does not exist. 

Not sure if it wise to use option 3 since this image is quite heavy for the Zero W, but the question is if this image is suitable for the Zero W. Ofcourse I did the commands like 'apt-get update/upgrade/dist-upgrade'.

I also checked the images at https://re4son-kernel.com/re4son-pi-kernel, so I preferred for the default Kali images. And yes, I used google as my best friend to find out if there are issues with bluetooth, but it didn't bring me far.

The question is: what I experience with bluetooth, is this normal behaviour with the current image I am using or am I hitting an issue?

If more information is needed, let me know.

Thanks,

Setzer0

[steev]

systemctl enable bluetooth

only enables it next boot, you need to

systemctl start bluetooth

otherwise it won't start until the next boot.

Also note that the rpi image itself does not install the bluetooth bits that are needed, so what you're going to want to do if you insist on using the rpi image over the 0w image is, on the 0w (via ssh, or on the desktop in a terminal):

wget https://gitlab.com/kalilinux/build-scripts/kali-arm/raw/master/misc/pi-bluetooth/pi-bluetooth+re4son_2.2_all.deb
wget https://gitlab.com/kalilinux/build-scripts/kali-arm/raw/master/misc/pi-bluetooth/50-bluetooth-hci-auto-poweron.rules

cp 50-bluetooth-hci-auto-poweron.rules /usr/lib/udev/rules.d/50-bluetooth-hci-auto-poweron.rules
dpkg --force-all -i /root/pi-bluetooth+re4son_2.2_all.deb

Then reboot, and you should have bluetooth available (assuming you left the bluetooth service enabled. The hciuart service was dropped a few releases of bluez ago.

If you decide to go back to the 0w image, just running

systemctl enable bluetooth && systemctl start bluetooth

should get bluetooth working for you.

[SetZer0]

Thanks for your help. I am sure that I have replied earlier, but it's weird that my post didn't get here.

I did what you've told me, but it's not working. With the extra option of "systemctl enable hciuart" I get it working. I can use 'hciconfig'. With the default Kali Linux image, my external bluetooth Panda does do work, and that is important for me. Thanks again for your help for solving out the internal bluetooth issue.

[steev]

So are things working now for you, or not working? I'm not quite clear based on your message whether you're all set, or still having issues.