12

I followed this tutorial to set up my Bluetooth dongle and get it running. I have the same Bluetooth dongle that is in the tutorial, yet I can not seem to get it to work. I get to step "C" and then I run into problems. Here is some commands I ran to diagnose the problem:

$ hcitool scan
Device is not available: No such device
$ lsusb
...
Bus 001 Device 009: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
...
$ hciconfig dev
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:1B:10:00:2A:EC  ACL MTU: 1017:8  SCO MTU: 64:0
        DOWN
        RX bytes:1355 acl:0 sco:0 events:49 errors:0
        TX bytes:204 acl:0 sco:0 commands:48 errors:0
$ hciconfig -a
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:1B:10:00:2A:EC  ACL MTU: 1017:8  SCO MTU: 64:0
        DOWN
        RX bytes:1355 acl:0 sco:0 events:49 errors:0
        TX bytes:204 acl:0 sco:0 commands:48 errors:0
        Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy:
        Link mode: SLAVE ACCEPT
$ hcitool dev
Devices:
$ sudo hciconfig hci0 piscan
Can't set scan mode on hci0: Network is down (100)
$ sudo hciconfig hci0 reset
Can't init device hci0: Operation not supported (95)
$ /etc/init.d/bluetooth status
[ ok ] bluetooth is running.
$ sudo bluez-simple-agent
Traceback (most recent call last):
  File "/usr/bin/bluez-simple-agent", line 104, in <module>
    path = manager.DefaultAdapter()
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__
    **keywords)
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.bluez.Error.NoSuchAdapter: No such adapter

Any suggestions? Power isn't the issue since I'm running the dongle from a powered USB hub.

I do not want solutions that tell me to downgrade my software. That is not a solution, that is a workaround.

  • What are you powering from the hub the bluetooth dongle, the Pi or both? – Steve Robillard Dec 3 '13 at 22:57
  • @SteveRobillard Just the dongle. – syb0rg Dec 3 '13 at 22:58
  • What is returned from /etc/init.d/bluetooth status – Steve Robillard Dec 3 '13 at 23:00
  • @SteveRobillard Edited it in at the bottom of what commands I ran. It said it was running. – syb0rg Dec 4 '13 at 4:54
  • 3
    I'm having exactly the same error as you. Did you by chance got any update on this? – catteneo Jan 8 '14 at 2:42
8

Late answer, but recently experienced it. I noticed the interface is down. Yours is down too.

Running sudo hciconfig hci0 up on an updated firmware solved my problem. Not sure how that happened, as the people from this raspberrypi.org thread insists on downgrading.

  • This worked for me, after i unblocked the bluetooth interface with rfkill – mlhDev Dec 4 '16 at 15:46
-2

Check my answer in the following thread: http://www.raspberrypi.org/forum/viewtopic.php?t=63418&p=469478

I had the same issue with the same dongle and been able to solve it downgrading the RPi kernel (raspbian).

Cheers,

Olivier

  • 7
    This answer needs to be re-written to incorporate details from that other thread to better make a complete question/answer pair here. – Jivings Mar 16 '14 at 12:07

protected by Community Apr 4 '14 at 4:12

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.