Belkin (B8T017) Bluetooth dongle

[arjangoossens]

Hi

I don't seem to get my Belkin (B8T017) bluetooth dongle to work. I tried the debian6-19-04-2012 and 2012_06_10_spindle_wheezy_public_alpha images, but the result is the same on both.

What am i doing wrong? or is this dongle not supported?

hciconfig always indicates it is down, when trying to get i up, i get "Connection timed out (110)"

root@raspberrypi:~# hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:19:0E:07:EA:74 ACL MTU: 1021:8 SCO MTU: 64:1
DOWN
RX bytes:455 acl:0 sco:0 events:16 errors:0
TX bytes:75 acl:0 sco:0 commands:18 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT

[bob_binz]

Is the dongle plugged into a hub? If so, try connecting it directly to one of the ports on the Pi if you can. I had a similar problem with mine and could only cure it by connecting to a Pi port. I'm not sure whether it's a power issue or not, although I do know my hub was an el-cheapo model.

[arjangoossens]

the dongle is directly plugged in the rpi usb port (the only usb device attached)

[observing]

I have experienced something similar to your problem when I tried to get my bluetooth dongle working. I followed the instructions at http://wiki.debian.org/BluetoothUser. At first, hcitool didn't seem to see the device and hciconfig gave me output similar to what you listed (i.e. the interfaceis DOWN). When trying to bring the interface UP, I also received the "Can't init device hci0: Connection timed out (110)" error.

What I discovered was that, in connecting a usb keyboard, usb mouse, and usb bluetooth dongle at the same time, only two of the three were functional. When the bluetooth dongle was one of the two functional devices, it worked as expected. It didn't matter which of the usb devices were connected to the powered hub or directly to the RPi. I eventually worked around the problem by pairing a bluetooth mouse to the dongle and not using the usb mouse.

Since you didn't mention having multiple usb devices connected, this may not be helpful to you, but I think the non-functional state of your bluetooth dongle mirrors the state of mine prior to the workaround.

[arjangoossens]

thanks for the replies.

I tested it again, with only the bluetooth dongle directly into the rpi (no keyboard, no display connected) but the same still occurs:

root@raspberrypi:~# sudo hciconfig hci0 up
Can't init device hci0: Connection timed out (110)
root@raspberrypi:~# sudo hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:19:0E:07:EA:74 ACL MTU: 1021:8 SCO MTU: 64:1
DOWN
RX bytes:548 acl:0 sco:0 events:21 errors:0
TX bytes:116 acl:0 sco:0 commands:27 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT

I am going to try arclinux and maybe a different dongle.

[observing]

One last thought. I also installed blueman, which added some additional packages. If you can launch LXDE, you might want to give it a try. As you can imagine, it took a number of turns at plugging and unplugging the usb mouse and keyboard to navigate through blueman to pair the bluetooth mouse with the dongle.

[migube]

hi guys,

did u manage to get it working ? I have similar issues.
didn't try under X yet.

I'm trying under wheezy/raspbian , but would need it too under openelec/rasbmc ...

tx !

[sensornet]

Hi guys,

I have similar "Connection timed out (110)" problems with the dongle directly plugged into RPi usb port (without any other usb device connected, I'm connected to the pi through ssh). Then I've unplugged the dongle from the upper port and plugged into the lower usb port and it works, but it's not stable because hcitool commands fail from time to time. Any clue on how to fix the problem with this Belkin dongle? Could it be that the dongle needs a better power supply?

Below is the info of my system:

USB dongle_ usb_bluetooth_belkin_F8T016CW

Rasbian wheezy clean image (2012-10-28-wheezy-raspbian.zip) and then I've made an upgrade

Code: Select all

pi@raspberrypi ~ $ sudo apt-get upgrade

pi@raspberrypi ~ $ uname -a
Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux

USB dongle recognized

Code: Select all

pi@raspberrypi ~ $ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 012: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 016: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass)
Bus 001 Device 017: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface Subclass)
Bus 001 Device 018: ID 050d:016a Belkin Components Bluetooth Mini Dongle

Install bluetooth

Code: Select all

pi@raspberrypi ~ $ apt-get install -y bluetooth bluez-utils blueman

Start bluetooth

Code: Select all

pi@raspberrypi ~ $ /etc/init.d/bluetooth start
[ ok ] Starting bluetooth: bluetoothd rfcomm.

pi@raspberrypi ~ $ hciconfig -a
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:19:0E:10:DA:AB  ACL MTU: 1021:8  SCO MTU: 64:1
        UP RUNNING
        RX bytes:20923 acl:0 sco:0 events:3580 errors:0
        TX bytes:871 acl:0 sco:0 commands:80 errors:0
        Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT
        Name: 'raspberrypi-0'
        Class: 0x420100
        Service Classes: Networking, Telephony
        Device Class: Computer, Uncategorized
        HCI Version: 2.1 (0x4)  Revision: 0x5184
        LMP Version: 2.1 (0x4)  Subversion: 0x420e
        Manufacturer: Broadcom Corporation (15)

but this command fails sometimes

Code: Select all

pi@raspberrypi ~ $ hciconfig -a
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:19:0E:10:DA:AB  ACL MTU: 1021:8  SCO MTU: 64:1
        UP RUNNING
        RX bytes:21200 acl:0 sco:0 events:3583 errors:0
        TX bytes:880 acl:0 sco:0 commands:83 errors:0
        Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT

Can't read local name on hci0: Connection timed out (110)

[sigger]

Hi,

i had a similar problem... i tried to run up two "identical" bluetooth adapters...
(Cambridge Silicon Radio, Ltd Bluetooth Dongle)
Multiple bluetooth adapters...

Scenarios:

• RPi with no other usb device attached besides one of the bt-adapter -> no problem

• RPi with no other usb device attached besides two of the exact bt-adapters (cheap stuff) -> also no problem

...
so no problem for the RPi to handle it, but that wasn't my final setup... and here comes the big problem:
If i tried to attach another usb device, with the help of an cheap usb-hub (powered or non-powered) than i come the the same case as you guys described...

$ sudo hciconfig hci1 up
or
$ sudo hciconfig -a (looks just the same ... no name and some missing information or errors appear)
$ ... timeout (110) etc.

My setup needed to move the two bt-adapter away from the RPi, so i tried to hook up both at one usb-hub and the hub directly to the RPi. Best result in this case was that one adapter was UP and the other was DOWN (unable the getting up).
Btw: the other usb port of the RPi was used by an EDIMAX wifi dongle.

$ lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 004: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 007: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

So i tried other usb-hubs (powered and non-powered) different power supplies... i also tried to hot/cold-plug the bt-adapters and hub... i switched the order of the usb adapters... also the order of the wifi and usb-hub at the RPi ... all tries with the same result as you guys described above.

Finally i found a solution that worked for me by luck.
If i plug the WI-Fi-dongle and a random usb-hub (powered or non-powered) directly into the RPi, than plug the 1ST of the BT-adapters into any port of the usb-hub AND THAN take another (same exact or different) usb-hub and plug them into any port of the first usb-hub and finally plug the 2ND BT-adapter into any port of the second usb-hub than it works very well.

Two usb-hubs insead of one. Unbelievable but true.

$ lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 012: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 009: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 001 Device 005: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]
Bus 001 Device 010: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 011: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB

Now i can to use both adapters without any problems. (up, down, piscan, noscan, lm none, accept ...)

In my opinion there is a timing problem in the kernel or something like that.
Reason in my opinion:
The upper "lsusb" printed device id's that are close to each other (006, 007)... the lower printed device id's that are further away from each other (010, 012)... that combined with the fact that usb is a "bus system" seems to solve the timing problem with hardware... not a great solution but better that no solution... kernel fix or something is still needed.

For your case i would hook up a usb-hub directly into the RPi and plug the BT-adapter in this hub, and if you want to use other usb-devices (keyboard, mouse etc.) you should use them with another usb-hub plugged at the other usb-port of the RPi or plugged into the first usb-hub.

Sounds stupid but worked for me:
a chain of usb-hubs with just one device attached (besides to the next usb-hub if available).

greetings
sigger