Ubuntu
bluez package

  1. Bug #416487
  2. Comment #1

Comment 1 for bug 416487

Revision history for this message
Mario Limonciello (superm1) wrote :

To start out, is the device being identified as a bluetooth device?

Take a look if btusb is getting loaded:

$ btusb

If it is, make sure that

$ hciconfig

lists it.

If it's listed, try to reset the device using

$ sudo hciconfig hci0 reset

If that works, then it's a kernel bug and your device needs a reset quirk.