hcitool scan fails to see bluetooth keyboard

BartG · 03-07-2014, 04:22 AM

(crossposting from the Raspbmc forums)

Hi,

I've recently bought a Raspberry Pi and have installed Raspbmc on it. Both are really great, but I do have some problems with it. The problem that I'd like to deal with first is connecting my bluetooth keyboard to my RPi. This seems to be a linux issue rather than a raspbmc issue so I thought to ask it on this forum too. I also need to mention that I'm fairly new to Linux, so I'd appreciate if you talk slow and don't use big words

My Problem:
I have a bluetooth dongle connected to my RPi and a bluetooth keyboard that I want to connect to it. I followed the steps in this useful guide to get things running. When I run lsusb I get te following result:

Quote:

root@raspbmc:/home/pi# lsusb
Bus 001 Device 002: ID 0424:9514 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 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 005: ID 04d9:1818 Holtek Semiconductor, Inc.

Then I put my keyboard in discoverable mode and run hcitool scan. The result is an empty list:

Quote:

root@raspbmc:/home/pi# hcitool scan
Scanning ...
root@raspbmc:/home/pi#

Whatever I do the list remains empty and it just doesn't show my keyboard. I've rebooted the RPi multiple times, but that didn't help. The dongle seems to be working ok, the keyboard too, but it's not being displayed. I've tried the same dongle and keyboard under Windows 7 and I didn't encounter any problem; it will show up and connect just fine. I've tried to find an answer through google, but I couldn't find anything that helped me.

When I run hciconfig -a I get the following result:

Quote:

root@raspbmc:/home/pi# hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 00:09: DD:50:12:48 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:1063 acl:0 sco:0 events:36 errors:0
TX bytes:388 acl:0 sco:0 commands:35 errors:0
Features: 0xff 0xff 0x8f 0xf8 0x18 0x18 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'raspbmc-0'
Class: 0x420100
Service Classes: Networking, Telephony
Device Class: Computer, Uncategorized
HCI Version: 1.1 (0x1) Revision: 0x639
LMP Version: 1.1 (0x1) Subversion: 0x639
Manufacturer: Cambridge Silicon Radio (10)

If anyone can help me solve this issue, I'd appreciate it a lot!

BartG

pingwinowiewc · 03-07-2014, 06:06 AM

Check logs (/var/log) to see if any SSD drive has the same irq. Most often, this is the case.
Does your Linux use SSD mpad? if so - disable it

BartG · 03-07-2014, 08:05 AM

Thanks for the quick reply. In what file should I look, and what exactly am I looking for? There's a lot residing in the /var/log directory:

Quote:

root@raspbmc:/var/log# ls -l
total 5816
drwxr-xr-x 2 root root 4096 Jan 1 1970 ConsoleKit
-rw-r--r-- 1 root root 19931 Mar 6 15:17 alternatives.log
drwxr-xr-x 2 root root 4096 Jan 1 1970 apt
-rw-r----- 1 root adm 294336 Mar 7 10:13 auth.log
-rw-r--r-- 1 root root 57954 Dec 23 04:46 bootstrap.log
-rw-rw---- 1 root utmp 0 Dec 23 04:43 btmp
drwxr-xr-x 2 root root 4096 Mar 6 15:12 cups
-rw-r----- 1 root adm 1032595 Mar 7 11:20 daemon.log
-rw-r----- 1 root adm 277851 Mar 7 10:12 debug
-rw-r----- 1 root adm 10510 Mar 7 01:37 dmesg
-rw-r----- 1 root adm 10703 Mar 7 01:37 dmesg.0
-rw-r----- 1 root adm 4169 Mar 7 01:22 dmesg.1.gz
-rw-r----- 1 root adm 4284 Mar 7 01:11 dmesg.2.gz
-rw-r----- 1 root adm 4141 Mar 7 01:11 dmesg.3.gz
-rw-r----- 1 root adm 4234 Mar 6 17:26 dmesg.4.gz
-rw-r--r-- 1 root root 417068 Mar 6 15:20 dpkg.log
-rw-r--r-- 1 root root 24024 Mar 6 15:19 faillog
-rw-r--r-- 1 root root 1185 Mar 6 15:14 fontconfig.log
drwxr-xr-x 2 root root 4096 Jan 1 1970 fsck
drwxr-xr-x 2 root root 4096 Dec 28 23:22 hp
-rw-r----- 1 root adm 582974 Mar 7 11:20 kern.log
-rw-rw-r-- 1 root utmp 292292 Mar 7 10:13 lastlog
-rw-r----- 1 root adm 0 Jan 1 1970 lpr.log
-rw-r----- 1 root adm 0 Jan 1 1970 mail.err
-rw-r----- 1 root adm 0 Jan 1 1970 mail.info
-rw-r----- 1 root adm 0 Jan 1 1970 mail.log
-rw-r----- 1 root adm 0 Jan 1 1970 mail.warn
-rw-r----- 1 root adm 664953 Mar 7 11:22 messages
drwxr-xr-x 2 root root 4096 Jan 1 1970 news
drwxr-xr-x 2 ntp ntp 4096 May 18 2012 ntpstats
-rw-r--r-- 1 root root 38100 Mar 7 10:11 pm-powersave.log
drwxr-x--- 3 root adm 4096 Mar 5 11:58 samba
-rw-r----- 1 root adm 1756743 Mar 7 11:22 syslog
-rw-r--r-- 1 root root 118252 Mar 7 01:37 udev
drwxr-xr-x 2 root root 4096 Feb 26 2013 upstart
-rw-r----- 1 root adm 138329 Mar 7 11:22 user.log
-rw-rw-r-- 1 root utmp 80640 Mar 7 10:13 wtmp

How can I check if my linux uses SSD mpad? How can I disable it?

pingwinowiewc · 03-07-2014, 12:04 PM

bootstrap.log -> see if its loaded on boot (and possible errors)
faillog
dmesg
syslog
udev

also go into console and check dmesg > dmseg.txt This will produce file dmseg.txt where will the output be. Examine it and look for some Bluetooth error/s.....

BartG · 03-07-2014, 04:23 PM

I couldn't find any mention of errors in the dmesg file, and the only bluetooth related text I could find was:

Quote:

Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
usbcore: registered new interface driver btusb

Which looks ok to me.

The syslog did turn up some interesting things:

Code:

Mar  7 01:11:58 raspbmc bluetoothd[1050]: Failed to init gatt_example plugin
Mar  7 01:22:13 raspbmc bluetoothd[1000]: Bluetooth daemon 4.99
Mar  7 01:22:13 raspbmc bluetoothd[1000]: Starting SDP server
Mar  7 01:22:13 raspbmc NetworkManager[854]: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files
Mar  7 01:22:13 raspbmc bluetoothd[1000]: Failed to init alert plugin
Mar  7 01:22:13 raspbmc bluetoothd[1000]: Failed to init time plugin
Mar  7 01:22:13 raspbmc bluetoothd[1000]: Failed to init gatt_example plugin
Mar  7 01:37:35 raspbmc bluetoothd[1007]: Bluetooth daemon 4.99
Mar  7 01:37:35 raspbmc bluetoothd[1007]: Starting SDP server
Mar  7 01:37:35 raspbmc bluetoothd[1007]: Failed to init alert plugin
Mar  7 01:37:35 raspbmc bluetoothd[1007]: Failed to init time plugin
Mar  7 01:37:35 raspbmc NetworkManager[850]: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files
Mar  7 01:37:35 raspbmc bluetoothd[1007]: Failed to init gatt_example plugin
Mar  7 01:37:36 raspbmc NetworkManager[730]: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files
Mar  7 01:37:36 raspbmc bluetoothd[1022]: Bluetooth daemon 4.99
Mar  7 01:37:36 raspbmc bluetoothd[1022]: Starting SDP server
Mar  7 01:37:36 raspbmc bluetoothd[1022]: Failed to init alert plugin
Mar  7 01:37:36 raspbmc bluetoothd[1022]: Failed to init time plugin
Mar  7 01:37:36 raspbmc bluetoothd[1022]: Failed to init gatt_example plugin
Mar  7 01:37:36 raspbmc bluetoothd[1022]: Listening for HCI events on hci0
Mar  7 01:37:36 raspbmc bluetoothd[1022]: HCI dev 0 up
Mar  7 01:37:36 raspbmc bluetoothd[1022]: Proximity GATT Reporter Driver: Operation not permitted (1)
Mar  7 01:37:36 raspbmc bluetoothd[1022]: Could not get the contents of DMI chassis type
Mar  7 01:37:36 raspbmc bluetoothd[1022]: Unable to load keys to adapter_ops: Function not implemented (38)
Mar  7 01:37:37 raspbmc bluetoothd[1022]: Adapter /org/bluez/1022/hci0 has been enabled
Mar  7 11:20:48 raspbmc bluetoothd[1022]: HCI dev 0 down
Mar  7 11:20:48 raspbmc bluetoothd[1022]: Adapter /org/bluez/1022/hci0 has been disabled
Mar  7 11:20:48 raspbmc bluetoothd[1022]: HCI dev 0 unregistered
Mar  7 11:20:48 raspbmc bluetoothd[1022]: Stopping hci0 event socket
Mar  7 11:20:48 raspbmc bluetoothd[1022]: Unregister path: /org/bluez/1022/hci0
Mar  7 19:44:44 raspbmc NetworkManager[832]: <warn> bluez error getting default adapter: The name org.bluez was not provided by any .service files
Mar  7 19:44:45 raspbmc bluetoothd[1052]: Bluetooth daemon 4.99
Mar  7 19:44:45 raspbmc bluetoothd[1052]: Starting SDP server
Mar  7 19:44:46 raspbmc bluetoothd[1052]: Failed to init alert plugin
Mar  7 19:44:46 raspbmc bluetoothd[1052]: Failed to init time plugin
Mar  7 19:44:47 raspbmc bluetoothd[1052]: Failed to init gatt_example plugin
Mar  7 20:05:13 raspbmc kernel: Modules linked in: bcm2708_wdog bnep rfcomm bluetooth rfkill xt_state iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_
ipv4 ipv6 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter ip_tables x_tables snd_soc_bcm2708_i2s regmap_mmio snd_soc_core snd_compress regmap_i2c regmap_spi s
nd_pcm snd_page_alloc snd_timer snd i2c_bcm2708
Mar  7 19:44:43 raspbmc bluetoothd[1054]: Bluetooth daemon 4.99
Mar  7 19:44:43 raspbmc bluetoothd[1054]: Starting SDP server
Mar  7 19:44:43 raspbmc bluetoothd[1054]: Failed to init alert plugin
Mar  7 19:44:43 raspbmc bluetoothd[1054]: Failed to init time plugin
Mar  7 19:44:44 raspbmc bluetoothd[1054]: Failed to init gatt_example plugin
Mar  7 19:44:44 raspbmc bluetoothd[1054]: Listening for HCI events on hci0
Mar  7 19:44:45 raspbmc bluetoothd[1054]: HCI dev 0 up
Mar  7 19:44:45 raspbmc bluetoothd[1054]: Proximity GATT Reporter Driver: Operation not permitted (1)
Mar  7 19:44:45 raspbmc bluetoothd[1054]: Could not get the contents of DMI chassis type
Mar  7 19:44:45 raspbmc bluetoothd[1054]: Unable to load keys to adapter_ops: Function not implemented (38)
Mar  7 19:44:45 raspbmc bluetoothd[1054]: Adapter /org/bluez/1054/hci0 has been enabled
Mar  7 21:25:10 raspbmc bluetoothd[1033]: Bluetooth daemon 4.99
Mar  7 21:25:10 raspbmc bluetoothd[1033]: Starting SDP server
Mar  7 21:25:10 raspbmc bluetoothd[1033]: Failed to init alert plugin
Mar  7 21:25:10 raspbmc bluetoothd[1033]: Failed to init time plugin
Mar  7 21:25:10 raspbmc bluetoothd[1033]: Failed to init gatt_example plugin
Mar  7 21:25:10 raspbmc bluetoothd[1033]: Listening for HCI events on hci0
Mar  7 21:25:11 raspbmc bluetoothd[1033]: HCI dev 0 up
Mar  7 21:25:11 raspbmc bluetoothd[1033]: Proximity GATT Reporter Driver: Operation not permitted (1)
Mar  7 21:25:11 raspbmc bluetoothd[1033]: Could not get the contents of DMI chassis type
Mar  7 21:25:11 raspbmc bluetoothd[1033]: Unable to load keys to adapter_ops: Function not implemented (38)
Mar  7 21:25:11 raspbmc bluetoothd[1033]: Adapter /org/bluez/1033/hci0 has been enabled

But I have no idea what to make of them. Is it the error in getting the default adapter? Can it be the failure to init the alert, time, or gatt_ecample plugins? Maybe something else?