SOLVED: Guide to get RPi3 & Zero W internal Bluetooth working

Overview › Forums › Sticky Finger’s Kali-Pi › SOLVED: Guide to get RPi3 & Zero W internal Bluetooth working

Tagged: , , ,

This topic contains 12 replies, has 3 voices, and was last updated by  wilsonb 1 year, 8 months ago. This post has been viewed 11767 times

  • Author
    Posts
  • November 27, 2016 at 2:31 am #11023

    Re4son
    Keymaster

    Hi everyone,

    I’ve finally gotten around to look into the Rasperry Pi 3 internal bluetooth issue and found a way to get it to work.
    The following guide works with Sticky Finger’s Kali-Pi and vanilla kali if you install the re4son-kernel:

    THE NEW RE4SON KERNEL DOES THE ENTIRE SETUP AUTOMATICALLY, no manual configuration required. It supports all Pi’s (1,2,3,Zero, Zero W)
    Just head over to the re4son-kernel page for the installation guide.

    Happy hacking,
    Re4son

  • February 1, 2017 at 1:55 am #11126

    vavavoom
    Participant

    Hello Re4son,

    Does this turn on bluetooth automatically on boot up or do I have to type in the commands each time? Thanks

  • February 22, 2017 at 8:15 pm #11263

    wilsonb
    Participant

    Good question above..
    I will write a “Pairing script” to easily run those commands to pair different devices. Is this nessesary or just running [bluetoothctl] ?

    From the instructions, hard to tell where Vanilla Section stops and where StickyFingers image version starts.

    I got an error, so assume will have to install items above. Not sure what’s already “baked in”
    [bluetooth]# scan on
    Failed to start discovery: org.bluez.Error.NotReady

    Update: looks like items are already installed on Sticky Image

  • February 22, 2017 at 8:22 pm #11264

    wilsonb
    Participant

    After typing in
    root@kali-pi:~# dpkg -i pi-bluetooth_0.1.1_armhf.deb
    (Reading database … 193333 files and directories currently installed.)
    Preparing to unpack pi-bluetooth_0.1.1_armhf.deb …
    Unpacking pi-bluetooth (0.1.1) over (0.1.1) …
    Setting up pi-bluetooth (0.1.1) …
    Job for hciuart.service failed because the control process exited with error code.
    See “systemctl status hciuart.service” and “journalctl -xe” for details.
    hciuart.service couldn’t start.

    Journalctl shows;

    — Unit hciuart.service has begun starting up.
    Feb 23 07:18:51 kali-pi hciattach[1435]: Initialization timed out.
    Feb 23 07:18:51 kali-pi hciattach[1435]: bcm43xx_init
    Feb 23 07:18:51 kali-pi systemd[1]: hciuart.service: Control process exited, code=exited status=1
    Feb 23 07:18:51 kali-pi systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.
    — Subject: Unit hciuart.service has failed
    — Defined-By: systemd
    — Support: https://www.debian.org/support
    —
    — Unit hciuart.service has failed.
    —
    — The result is failed.
    Feb 23 07:18:51 kali-pi systemd[1]: hciuart.service: Unit entered failed state.
    Feb 23 07:18:51 kali-pi systemd[1]: hciuart.service: Failed with result ‘exit-code’.
    Feb 23 07:18:54 kali-pi wpa_supplicant[463]: wlan0: Failed to initiate sched scan
    Feb 23 07:19:57 kali-pi wpa_supplicant[463]: wlan0: Failed to initiate sched scan
    lines 2056-2091/2091 (END)

  • February 22, 2017 at 9:01 pm #11266

    wilsonb
    Participant

    So using Sticky image, continued with the steps starting at;
    “Login as root and install the necessary Bluetooth packages, firmware and rules:”
    A lot of this was already installed..

    and got farther with bluetooth,

    it sees it, trusted and paired..
    however, connection with wireless keyboard is shady..

    [bluetooth]# connect 20:73:00:7B:x:x
    Attempting to connect to 20:73:00:7B:x:x
    [CHG] Device 20:73:00:7B:x:x Connected: yes
    Failed to connect: org.bluez.Error.Failed
    [CHG] Device 20:73:00:7B:x:x Connected: no

  • February 22, 2017 at 9:26 pm #11268

    Re4son
    Keymaster

    Hi wilsonb,

    That’s odd. I’ve been using the Logitech K810 without any problems.
    The only issues I have with it is the lag, not too bad but a tiny bit annoying ( Raspbian’s the same though).

    I haven’t done the same endurance test with the latest kernel (Re4son 4.4.49 #1) which one are you using?

  • February 22, 2017 at 10:29 pm #11270

    wilsonb
    Participant

    Heya..
    Thanks for reply..
    I havent updated Kernel form baked STicky yet.. Should be same

  • February 22, 2017 at 10:34 pm #11271

    Re4son
    Keymaster

    I updated Sticky two days ago and included a new kernel (should not make any difference though) and nexmon drivers.

  • February 23, 2017 at 12:22 am #11275

    wilsonb
    Participant

    Just a thought…
    Maybe put a key symbol like * infront of items that are already done in Sticky.

  • February 23, 2017 at 1:48 am #11279

    Re4son
    Keymaster

    Good idea.

    In the manual installation guide, correct?

  • February 23, 2017 at 3:05 am #11280

    wilsonb
    Participant

    Yes sir.. Just so folks know which part to skip.

  • February 23, 2017 at 3:11 am #11281

    Re4son
    Keymaster

    Will do. Give me a day or two.

    Thanks for sharing your ideas.

  • February 23, 2017 at 3:50 am #11282

    wilsonb
    Participant

    Yes sir.. Just so folks know which part to skip.

    Example; I just did Setup OpenVASs section, because I don’t know if it was already done.. It’s taking FOREVER… then created the file
    /etc/systemd/system/greenbone-security-assistant.service.d/local.conf
    and it was already there with the text, so now thinking this all was already done.

  • Author
    Posts

You must be logged in to reply to this topic.