Thanks, Sejo. Looks like it's not seen: # hciconfig # But bluetoothd *is* running: # ps axww | grep blue 243 ? Ss 0:00 /usr/sbin/bluetoothd The device is not a USB device. It's an LSR TiWi-BLE module connected directly to the processor via UART (or SPI bus, not sure which). On May 2, 2014, at 12:02 , Sejo Ruiz <sejoruiz@xxxxxxxxx> wrote: > Hi Rick. > First of all, you should make sure that the device is recognized as a BT > device. Run hciconfig as sudo user to see if it returns something as > hci0. If you can see it, then you can do hciconfig hci0 up to set up the > interface and start playing. If not, then you could try to do lsusb and > see what devices are connected to the USB. If you cannot see your device > there, or something goes wrong, you can always try to check what is > going on by plugging the device off and on again and then type dmesg | > tail. Finally, make sure the bluetooth daemon is running. You can do > that by executing /etc/init.d/bluetoothd status (I'm not sure about this > last one) > NOTE: I suggest to execute all the commands with sudo. > -- Rick
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
