![]() ![]() 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |