Bluetooth with Broadcom chip a no go?


16 posts
by Mike Leach » Wed Jun 27, 2012 9:08 pm
I have tried to get Bluetooth working with the Arch distro, Squeeze distro, and now the new Wheezy distro with no success. I have just about narrowed the problem down to the Broadcom component of the dongle. Both the Belkin and Targus dongles I have been testing use the same Broadcom chip.
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. 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.

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”. (bluez-utils is installed with the Bluetooth package)

Linux raspberrypi 3.1.9+ #125 PREEMPT Sun Jun 17 16:09:36 BST 2012 armv6l

Modified the /etc/bluetooth/hcid.conf to the following:


pi@raspberrypi ~ $ cat /etc/bluetooth/hcid.conf
# HCId options
options {
# Automatically initialize new devices
autoinit yes;

#(Change security to "auto")
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security auto;

# Pairing mode
pairing multi;

#(You only need a pin helper if you are using <=bluez-libs-2.x and <=bluez-utils-2.x)
#(Change pin_helper to use /etc/bluetooth/pin-helper)
# PIN helper
#pin_helper /etc/bluetooth/pin-helper;
}

# Default settings for HCI devices
device {
#(Set your device name here, you can call it anything you want)
# Local device name
# %d - device id
# %h - host name
name "BlueZ at %h (%d)";

# Local device class
class 0x3e0100;

# Inquiry and Page scan
iscan enable; pscan enable;

# Default link mode
lm accept;

# Default link policy
lp rswitch,hold,sniff,park;

#(Leave as is, if you don't know what exactly these do)
# Authentication and Encryption (Security Mode 3)
#auth enable;
#encrypt enable;
}

Tried to bring up the dongle…

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

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 005: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
Bus 001 Device 006: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass)
Bus 001 Device 007: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface Subclass)
Bus 001 Device 008: ID 0a5c:2154 Broadcom Corp.

pi@raspberrypi ~ $ hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:0A:3A:84:78:5E ACL MTU: 1021:8 SCO MTU: 64:1
DOWN
RX bytes:435 acl:0 sco:0 events:8 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

pi@raspberrypi ~ $ sudo hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

pi@raspberrypi ~ $ sudo hcitool dev
Devices:

pi@raspberrypi ~ $ sudo hcitool scan
Device is not available: No such device

pi@raspberrypi ~ $ sudo hcitool inq
Inquiring ...
Inquiry failed.: No such device

The results above are exactly the same regardless of the distro or Belkin or Targus dongle.
Posts: 11
Joined: Tue Jun 05, 2012 3:13 pm
by Mike Leach » Thu Jun 28, 2012 3:28 am
FOLLOWUP:

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 first one I tried was the "PPA USB Bluetooth Adapter v2.0 + EDR" (model 9017v) and it worked instantly...

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 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 006: ID 413c:2003 Dell Computer Corp. Keyboard
Bus 001 Device 007: ID 413c:3200 Dell Computer Corp. Mouse

pi@raspberrypi ~ $ hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:15:83:52:A5:C5 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:39616 acl:1561 sco:0 events:1502 errors:0
TX bytes:9101 acl:69 sco:0 commands:1244 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 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: 0x520100
Service Classes: Networking, Object Transfer, Telephony
Device Class: Computer, Uncategorized
HCI Version: 2.1 (0x4) Revision: 0x149c
LMP Version: 2.1 (0x4) Subversion: 0x149c
Manufacturer: Cambridge Silicon Radio (10)

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.
Posts: 11
Joined: Tue Jun 05, 2012 3:13 pm
by doowttam » Sat Jun 30, 2012 5:54 am
Unfortunately for me, I read your post right after I got my bluetooth adapter home. Mine is a IOGEAR GBU421, but it has the same Broadcom chipset you mentioned. I'm getting perfect behavior on my x86 machine, but the same behavior you had on the Raspberry Pi.
Posts: 2
Joined: Sat Jun 30, 2012 5:51 am
by Mike Leach » Sat Jun 30, 2012 4:36 pm
Funny how that works... ;) I originally spent decent money on a Belkin because it was such a known brand thinking surely it would work, and as it turns out the $9 no name off brand was the ticket.
Posts: 11
Joined: Tue Jun 05, 2012 3:13 pm
by RoystonS » Tue Jul 03, 2012 7:32 pm
Interestingly, my (old) Class 1 Broadcom BT dongle appears to be working fine. Note that I've (half-)upgraded from squeeze to wheezy, so that may be related:

root@raspberrypi:/home/pi# uname -a
Linux raspberrypi 3.1.9+ #66 Thu May 17 16:56:20 BST 2012 armv6l GNU/Linux
root@raspberrypi:/home/pi# dmesg
[snip]
usb 1-1.3: new full speed USB device number 4 using dwc_otg
usb 1-1.3: New USB device found, idVendor=0a5c, idProduct=2101
usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1.3: Product: Class1 BT Dongle
usb 1-1.3: Manufacturer: Broadcom Corp
Bluetooth: Generic Bluetooth USB driver ver 0.6

root@raspberrypi:/home/pi# hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:19:86:00:0E:CF ACL MTU: 1017:8 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:2437 acl:0 sco:0 events:84 errors:0
TX bytes:810 acl:0 sco:0 commands:65 errors:0
Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80
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.0 (0x3) Revision: 0x4000
LMP Version: 2.0 (0x3) Subversion: 0x430e
Manufacturer: Broadcom Corporation (15)

root@raspberrypi:/home/pi# 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 004: ID 0a5c:2101 Broadcom Corp. BCM2045 Bluetooth

root@raspberrypi:/home/pi# hcitool scan
Scanning ...
A0:75:91:38:CE:B3 Royston phone

I haven't tried to get any further, but I can at least do a scan and see my phone.

Cheers,
Royston.
Posts: 1
Joined: Mon May 28, 2012 12:45 pm
by Steep » Tue Jul 03, 2012 8:06 pm
If you're UK based, Tescos own Technika brand Nano Bluetooth Adaptor has the Cambridge chipset and works fine, costs about £5.97
Posts: 145
Joined: Fri May 18, 2012 8:03 pm
by geekyaleks » Sat Oct 27, 2012 10:14 pm
doowttam wrote:Unfortunately for me, I read your post right after I got my bluetooth adapter home. Mine is a IOGEAR GBU421, but it has the same Broadcom chipset you mentioned. I'm getting perfect behavior on my x86 machine, but the same behavior you had on the Raspberry Pi.



I have PRECISELY the same dongle, and PRECISELY the same problem.. I think I will return it.
Posts: 4
Joined: Sat Oct 27, 2012 9:23 pm
by rgvraspi » Mon Nov 19, 2012 10:12 pm
I also have an IO Gear GBU421 lying around which I wanted to get working on my Raspberry Pi but that idea went out the window after reading this post. It seems to recognize it, but of course that's as far as it gets.

I remember it working fine in Ubuntu on an old PC I had. So is it just that the appropriate driver hasn't been compiled into the Kernel for the Raspberry Pi Linux Distributions? It's a pity as this Bluetooth device was a very common inexpensive device to buy locally. I have two of them myself, one of which is still in use on my PC (running Windows 7 though)
Posts: 31
Joined: Sat Nov 03, 2012 3:38 pm
Location: USA
by rgvraspi » Mon Dec 24, 2012 6:24 am
I thought I would post an update.:)

I had seen the IOGear GBU321 listed on the Verified Peripherals as working. I don't know how long it had been there, but I thought seeing as the GBU421 is basically a 'refreshed' version of the GBU321 with a similar chipset, I would give mine another go and sure enough it now works!

Much more convenient in getting files to the Raspberry Pi than sending them via email etc. Also saves wear and tear plugging in a USB stick just for the odd photo etc.
Posts: 31
Joined: Sat Nov 03, 2012 3:38 pm
Location: USA
by Kurtosis » Sat Jan 05, 2013 6:48 am
I think I solved the problem with Broadcom chip. More specifically, I got the Broadcom Corp. BCM92046DG-CL1ROM Bluetooth 2.1 Adapter to work (http://www.amazon.ca/IOGEAR-Bluetooth-A ... 429&sr=8-3).

I followed multiple guides (http://forum.stmlabs.com/showthread.php?tid=4273 ... ) to set it up and the device never showed up using Raspian Wheezy or Raspbmc.
Code: Select all
hcitool dev
Devices:

Yet the device was present but DOWN
Code: Select all
hciconfig
hci0:   Type: BR/EDR  Bus: USB
   BD Address: 00:02:72:23:E7:BA  ACL MTU: 1021:7  SCO MTU: 64:1
   DOWN
   RX bytes:316 acl:0 sco:0 events:7 errors:0
   TX bytes:49 acl:0 sco:0 commands:13 errors:0

I tried to mount it using and it would timeout.
Code: Select all
hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

Did a lot of Googling and a lot of forum grinding, and I found that the driver for this card should be btusb (http://hardware4linux.info/component/42167/).

I did an lsmod, and I saw
Code: Select all
bluetooth             197924  21 bnep,btusb,rfcomm

After reading a post about someone saying that it did not work on raspberry pi but it did on ubuntu (viewtopic.php?f=28&t=8014), I noticed his ubuntu lsmod looked something like this
Code: Select all
bluetooth     148869   12 hdip,btusb,bnep,rfcomm

It seems that bnep is the problem. I simply blacklisted bnep (http://pc-freak.net/blog/remove-disable ... x-servers/)
Code: Select all
root@deb:~# echo 'blacklist bnep' >> /etc/modprobe.d/bluetooth.conf

(I did it with nano, via sudo to create the file and write to it).

After a reboot, the interface was down, I brought it up and it worked. I scanned and found my PS3 Remote control on the first try.

Hope this helps.
Posts: 1
Joined: Sat Jan 05, 2013 6:18 am
by arobson13 » Tue Jan 15, 2013 5:31 pm
rgvraspi wrote:I thought I would post an update.:)

I had seen the IOGear GBU321 listed on the Verified Peripherals as working. I don't know how long it had been there, but I thought seeing as the GBU421 is basically a 'refreshed' version of the GBU321 with a similar chipset, I would give mine another go and sure enough it now works!


You were able to get the GBU421 Bluetooth adapter working with the Raspberry Pi?

Can you post your method?
Posts: 5
Joined: Tue Jan 15, 2013 5:15 pm
by swartre » Sun Feb 03, 2013 4:58 am
I picked up the IOGEAR dongle because the wiki said it worked, but I'm having the same problem on raspbian, even after disabling bnep.

I saw the PPA device at Fry's too ($9.99 vs $24.99 for the IOGEAR device) - will return the IOGEAR part and try PPA tomorrow. Will add it to the wiki if I get it working, in the hope I can save someone a few hours of trouble.
Posts: 2
Joined: Sun Oct 28, 2012 4:33 pm
by dougbtv » Wed Feb 13, 2013 4:13 pm
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 tried the bnep method, to no avail, and annoyingly enough -- I was getting this kinda flaky result. Sometimes I'd boot, and my hci0 would be up, sometimes it wouldn't be up.

So after much digging around, spending way more time on this than I expected... (And even after ordering a cheapy $5 extra bluetooth dongle with a Cambridge Silicon chipset to try! [which didn't work that well, actually. But I didn't hammer on it like I did with this one.])

...I finally stumbled upon this: https://github.com/raspberrypi/linux/issues/66

The fix that I found was to add in your /boot/cmdline.txt, add “dwc_otg.speed=1″ near the end.

My cmdline.txt now reads:

dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline dwc_otg.speed=1 rootwait

From what I understand, the USB speed appears to be the issue. I was able to enable bnep, and it still worked, too.

For more information, I also documented this in my blog @ http://dougbtv.com/?p=245

[deleted and re-added as I wasn't sure how to edit -- If you can. For typos / clarification]
Posts: 1
Joined: Tue Feb 12, 2013 9:27 pm
by OtherCrashOverride » Wed Feb 13, 2013 5:05 pm
From what I understand, the USB speed appears to be the issue.


I have a Broadcom bluetooth adapter BCM92045B3 and fought with it for a good while too. It turns out that there are issues with the Pi USB silicon and/or stack and split transactions. The solution for me was 1) current firmware and kernel, and most importantly, 2) plugging the device directly into the PI (Model B) instead of a powered USB hub.

Hope this bit of info saves someone the headache I had.

(An indicator of this issue is TX Timeout messages talking to the device in the system logs)
Posts: 582
Joined: Sat Feb 02, 2013 3:25 am
by funky81 » Fri Jul 05, 2013 9:22 pm
Any news for this?
I've just recently update the latest rpi update (dated july 5th)
but still doesnt work.

Please help....
Posts: 4
Joined: Fri Jul 05, 2013 9:10 pm
by tomihasa » Tue Apr 22, 2014 2:49 pm
I have been able to make Raspberry Pi work with Apple Wireless Keyboard and Targus dongle (bought in 2010 or so). My setup:

Raspberry Pi: Model B
Linux: Raspbian "wheezy" (Debian 7, LXDE) (kernel 3.10) (release 2014-01-07)
USB hub: Belkin Hi-Speed USB 2.0 Pocket Hub, F5U217
Power adapter: Sony Xperia Tipo
Keyboard 1: Apple Keyboard without Numeric Keypad
Keyboard 2: Apple Wireless Keyboard
Mouse: Logitech Mini Optical Mouse Plus+
Bluetooth dongle: Targus USB Bluetooth 2.1 Adapter (Targus Europe, EAN code: 5024442956201)

Setting things up:

pi@raspberrypi ~ $ uname -a
Linux raspberrypi 3.10.25+ #622 PREEMPT Fri Jan 3 18:41:00 GMT 2014 armv6l GNU/Linux

pi@raspberrypi ~ $ dmesg
--- (...) ---
[ 3.319507] usb 1-1.3: new high-speed USB device number 4 using dwc_otg
[ 3.430032] usb 1-1.3: New USB device found, idVendor=0409, idProduct=005a
[ 3.441571] usb 1-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 3.454535] hub 1-1.3:1.0: USB hub found
[ 3.463440] hub 1-1.3:1.0: 4 ports detected
[ 3.749587] usb 1-1.3.2: new high-speed USB device number 5 using dwc_otg
[ 3.868890] usb 1-1.3.2: New USB device found, idVendor=05ac, idProduct=1005
[ 3.880785] usb 1-1.3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.892881] usb 1-1.3.2: Product: Keyboard Hub
[ 3.901768] usb 1-1.3.2: Manufacturer: Apple Inc.
[ 3.910989] usb 1-1.3.2: SerialNumber: 000000000000
[ 3.921204] hub 1-1.3.2:1.0: USB hub found
[ 3.930111] hub 1-1.3.2:1.0: 3 ports detected
[ 4.219494] usb 1-1.3.2.2: new low-speed USB device number 6 using dwc_otg
[ 4.344338] usb 1-1.3.2.2: New USB device found, idVendor=05ac, idProduct=021e
[ 4.356166] usb 1-1.3.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4.368388] usb 1-1.3.2.2: Product: Apple Keyboard
[ 4.377709] usb 1-1.3.2.2: Manufacturer: Apple Inc.
[ 4.479529] usb 1-1.3.2.3: new low-speed USB device number 7 using dwc_otg
[ 4.598496] usb 1-1.3.2.3: New USB device found, idVendor=046d, idProduct=c016
[ 4.610503] usb 1-1.3.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 4.622762] usb 1-1.3.2.3: Product: Optical USB Mouse
[ 4.632447] usb 1-1.3.2.3: Manufacturer: Logitech
--- (...) ---
[ 76.009504] usb 1-1.3.4: new full-speed USB device number 8 using dwc_otg
[ 76.119718] usb 1-1.3.4: New USB device found, idVendor=0a5c, idProduct=4500
[ 76.119757] usb 1-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 76.119776] usb 1-1.3.4: Product: BCM2046B1
[ 76.119793] usb 1-1.3.4: Manufacturer: Broadcom
[ 76.131522] hub 1-1.3.4:1.0: USB hub found
[ 76.132721] hub 1-1.3.4:1.0: 3 ports detected
[ 76.409999] usb 1-1.3.4.1: new full-speed USB device number 9 using dwc_otg
[ 76.516036] usb 1-1.3.4.1: New USB device found, idVendor=0a5c, idProduct=4502
[ 76.516073] usb 1-1.3.4.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 76.524264] input: HID 0a5c:4502 as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4.1/1-1.3.4.1:1.0/input/input3
[ 76.526807] hid-generic 0003:0A5C:4502.0004: input,hidraw3: USB HID v1.11 Keyboard [HID 0a5c:4502] on usb-bcm2708_usb-1.3.4.1/input0
[ 76.600059] usb 1-1.3.4.2: new full-speed USB device number 10 using dwc_otg
[ 76.706057] usb 1-1.3.4.2: New USB device found, idVendor=0a5c, idProduct=4503
[ 76.706100] usb 1-1.3.4.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 76.721478] input: HID 0a5c:4503 as /devices/platform/bcm2708_usb/usb1/1-1/1-1.3/1-1.3.4/1-1.3.4.2/1-1.3.4.2:1.0/input/input4
[ 76.730992] hid-generic 0003:0A5C:4503.0005: input,hidraw4: USB HID v1.11 Mouse [HID 0a5c:4503] on usb-bcm2708_usb-1.3.4.2/input0
[ 76.810094] usb 1-1.3.4.3: new full-speed USB device number 11 using dwc_otg
[ 76.919062] usb 1-1.3.4.3: New USB device found, idVendor=0a5c, idProduct=2153
[ 76.919102] usb 1-1.3.4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 76.919123] usb 1-1.3.4.3: Product: BCM92046DG-CL1ROM
[ 76.919142] usb 1-1.3.4.3: Manufacturer: Broadcom Corp
[ 76.919159] usb 1-1.3.4.3: SerialNumber: 00190E089AE7
--- (...) ---

pi@raspberrypi ~ $ sudo aptitude install bluetooth
The following NEW packages will be installed:
acl{a} avahi-daemon{a} bc{a} bind9-host{a} bluetooth bluez{a} bluez-alsa{a} bluez-cups{a} bluez-gstreamer{a}
colord{a} cups{a} cups-filters{a} cups-ppdc{a} dc{a} foomatic-db-compressed-ppds{a} foomatic-db-engine{a}
foomatic-filters{a} geoip-database{a} ghostscript-cups{a} hpijs{a} hplip{a} hplip-data{a} libart-2.0-2{a}
libavahi-core7{a} libbind9-80{a} libcap-ng0{a} libcupscgi1{a} libcupsdriver1{a} libcupsfilters1{a}
libcupsmime1{a} libcupsppdc1{a} libdns88{a} libescpr1{a} libgeoip1{a} libgusb2{a} libgutenprint2{a} libhpmud0{a}
libieee1284-3{a} libisc84{a} libisccc80{a} libisccfg82{a} liblwres80{a} libnss-mdns{a} libperl5.14{a} libsane{a}
libsane-common{a} libsane-extras{a} libsane-extras-common{a} libsane-hpaio{a} libsensors4{a} libslp1{a}
libsnmp-base{a} libsnmp15{a} mscompress{a} printer-driver-all{a} printer-driver-c2050{a} printer-driver-c2esp{a}
printer-driver-cjet{a} printer-driver-escpr{a} printer-driver-foo2zjs{a} printer-driver-gutenprint{a}
printer-driver-hpcups{a} printer-driver-hpijs{a} printer-driver-m2300w{a} printer-driver-min12xxw{a}
printer-driver-pnm2ppa{a} printer-driver-postscript-hp{a} printer-driver-ptouch{a} printer-driver-pxljr{a}
printer-driver-sag-gdi{a} printer-driver-splix{a} python-gobject-2{a} python-imaging{a} python-pexpect{a}
python-renderpm{a} python-reportlab{a} python-reportlab-accel{a} sane-utils{a} ssl-cert{a}
--- clip ---

pi@raspberrypi ~ $ 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 006: ID 05ac:021e Apple, Inc. Aluminum Mini Keyboard (ISO)
Bus 001 Device 007: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 001 Device 009: ID 0a5c:4502 Broadcom Corp. Keyboard (Boot Interface Subclass)
Bus 001 Device 010: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface Subclass)
Bus 001 Device 011: ID 0a5c:2153 Broadcom Corp.
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 005: ID 05ac:1005 Apple, Inc.
Bus 001 Device 008: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)

pi@raspberrypi ~ $ hcitool scan
Scanning ...
04:DB:56:CB:E5:1D Apple Wireless Keyboard

pi@raspberrypi ~ $ sudo apt-get install bluetooth bluez-utils blueman
--- (first try, I see errors, so let's update things first) ---

pi@raspberrypi ~ $ sudo apt-get update
--- clip ---

pi@raspberrypi ~ $ sudo apt-get install bluetooth bluez-utils blueman
--- (second try) ---
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
bluez-cups cups cups-filters foomatic-db-compressed-ppds foomatic-db-engine foomatic-filters ghostscript-cups hpijs
hplip imagemagick-common libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra0 libcupsfilters1 libhpmud0
liblqr-1-0 libmagickcore5 libmagickwand5 libopenobex1 libperl5.14 libpulse-mainloop-glib0 libsane-hpaio libsnmp15
notification-daemon obex-data-server perl perl-base perl-modules printer-driver-all printer-driver-foo2zjs
printer-driver-gutenprint printer-driver-hpcups printer-driver-hpijs printer-driver-m2300w printer-driver-min12xxw
printer-driver-postscript-hp printer-driver-pxljr printer-driver-sag-gdi printer-driver-splix python-cairo
python-gconf python-gobject python-gtk2 python-notify
--- clip ---

Bluetooth Manager GUI (Bluetooth Devices) was installed, so I started it.
- Scan: found Apple Wireless Keyboard
- Pairing: use random PIN (manually created PIN didn't work for me)

And that's it!
User avatar
Posts: 15
Joined: Sun May 05, 2013 5:23 pm
Location: Finland