Created attachment 107414 [details] bisect log # lsusb Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) # hciconfig -a hci0: Type: BR/EDR Bus: USB BD Address: 00:19:86:00:05:47 ACL MTU: 1017:8 SCO MTU: 64:0 DOWN RX bytes:457 acl:0 sco:0 events:16 errors:0 TX bytes:68 acl:0 sco:0 commands:16 errors:0 Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: Link mode: SLAVE ACCEPT # hciconfig hci0 up Can't init device hci0: Operation not supported (95)
Could you provide the output of hcidump or btmon when you try to run: $ hciconfig hci0 down $ hciconfig hci0 up
Created attachment 108161 [details] hcidump output
There's a discrepancy with the manufacturer of your device in the various pieces of information that you have provided. On the USB level (from your initial report) it's saying CSR: > # lsusb > Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth > Dongle (HCI mode) However, from your latest attachment on the HCI level it's saying Broadcom: > < HCI Command: Read Local Version Information (0x04|0x0001) plen 0 > > HCI Event: Command Complete (0x0e) plen 12 > Read Local Version Information (0x04|0x0001) ncmd 1 > status 0x00 > HCI Version: 2.0 (0x3) HCI Revision: 0x3000 > LMP Version: 2.0 (0x3) LMP Subversion: 0x420b > Manufacturer: Broadcom Corporation (15) So it doesn't seem like the original report and your attachment are for the same hardware (or if they are then the hardware is probably neither CSR nor Broadcom and more likely some cheap Asian clone)
(In reply to Johan Hedberg from comment #3) This is the same device. hciconfig and lsusb output (kernel 2.9.11): $ lsusb | grep -i bluetooth Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) $ hciconfig hci0 version hci0: Type: BR/EDR Bus: USB BD Address: 00:19:86:00:05:47 ACL MTU: 1017:8 SCO MTU: 64:0 HCI Version: 2.0 (0x3) Revision: 0x3000 LMP Version: 2.0 (0x3) Subversion: 0x420b Manufacturer: Broadcom Corporation (15)
(In reply to lbv5051 from comment #4) > (kernel 2.9.11): 3.9.11 //fix
This is the same issue as 60824, there's a patch there that fixes it.
I have tested patch from 60824 on 3.11.3 - works fine.
Created attachment 111861 [details] Bluetooth path
I testing path on 3.11.5 and it working.
This actuality to 3.11.x branch of kernel release (tested on 3.11.5 and 3.11.6 kernels)