I have a different solution for my GBU321 - which again, I bought because it's on the wiki (and I hope to add this note to the wiki, too).
I haven't tried to get any further, but I can at least do a scan and see my phone. Manufacturer: Broadcom Corporation lsusbīus 001 Device 004: ID 0a5c:2101 Broadcom Corp. LMP Version: 2.0 (0x3) Subversion: 0x430e RX bytes:2437 acl:0 sco:0 events:84 errors:0
#GBU421 BLUETOOTH PERIPHERAL DEVICE DRIVER#
Usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0īluetooth: Generic Bluetooth USB driver ver hciconfig -aīD Address: 00:19:86:00:0E:CF ACL MTU: 1017:8 SCO MTU: 64:8 Usb 1-1.3: New USB device found, idVendor=0a5c, idProduct=2101
#GBU421 BLUETOOTH PERIPHERAL DEVICE FULL#
Usb 1-1.3: new full speed USB device number 4 using dwc_otg Linux raspberrypi 3.1.9+ #66 Thu May 17 16:56: armv6l dmesg Note that I've (half-)upgraded from squeeze to wheezy, so that may be uname -a Interestingly, my (old) Class 1 Broadcom BT dongle appears to be working fine. This reinforces my suspicion that the "Broadcom" based dongles should be avoided and the "Cambridge Silicon Radio" based dongles should be the first you should try. Manufacturer: Cambridge Silicon Radio (10) LMP Version: 2.1 (0x4) Subversion: 0x149c Service Classes: Networking, Object Transfer, Telephony Keyboardīus 001 Device 007: ID 413c:3200 Dell Computer Corp. The first one I tried was the "PPA USB Bluetooth Adapter v2.0 + EDR" (model 9017v) and it worked ~ $ lsusbīus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)īus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. I stopped by Fry's on the way home this evening and picked up a handful of $9.99 bluetooth dongles of varying manufacturing origin. The results above are exactly the same regardless of the distro or Belkin or Targus dongle. Link mode: SLAVE ~ $ sudo hciconfig hci0 upĬan't init device hci0: Connection timed out ~ $ sudo hcitool ~ $ sudo hcitool scanĭevice is not available: No such ~ $ sudo hcitool inq Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 TX bytes:75 acl:0 sco:0 commands:18 errors:0įeatures: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83 RX bytes:435 acl:0 sco:0 events:8 errors:0 Keyboard (Boot Interface Subclass)īus 001 Device 007: ID 0a5c:4503 Broadcom Corp. Tried to bring up the ~ $ sudo /etc/init.d/bluetooth startīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.īus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.īus 001 Device 005: ID 0a5c:4500 Broadcom Corp. # Authentication and Encryption (Security Mode 3) #(Leave as is, if you don't know what exactly these do) #(Set your device name here, you can call it anything you want) #(Change pin_helper to use /etc/bluetooth/pin-helper)
#(You only need a pin helper if you are using <=bluez-libs-2.x and <=bluez-utils-2.x) # auto - Use local PIN for incoming connections Modified the /etc/bluetooth/nf to the ~ $ cat /etc/bluetooth/nf Linux raspberrypi 3.1.9+ #125 PREEMPT Sun Jun 17 16:09: armv6l (bluez-utils is installed with the Bluetooth package) The results below are from a fresh Wheezy distro with the latest apt-get update, apt-get upgrade, rpi-update, and I have installed packages “bluetooth”, and “blueman”. I am not opposed to heading out to track one down, but I thought before I do that I would put this out there for any comments or suggestions. Over the course of the last two weeks I have read every post related to Bluetooth on this forum and it appears that the common denominator linking success stories is the “Cambridge Silicon Radio” based dongles. Both the Belkin and Targus dongles I have been testing use the same Broadcom chip. I have just about narrowed the problem down to the Broadcom component of the dongle. I have tried to get Bluetooth working with the Arch distro, Squeeze distro, and now the new Wheezy distro with no success.
0 kommentar(er)
