Hi All,
I have a USB Bluetooth Dongle it detects but i am unable to use it,
Cannot pair with any mobile device or send any file.
I am using "Ubuntu 14.04 64-bit" with kernel version "3.13.0-65-generic"
Here is the output of dmesg,
[ 2920.744043] usb 3-1: new full-speed USB device number 3 using uhci_hcd
[ 2920.985498] usb 3-1: New USB device found, idVendor=0a12, idProduct=0001
[ 2920.985504] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2920.985507] usb 3-1: Product: Bluetooth V2.0 Dongle
[ 2920.985510] usb 3-1: Manufacturer: Bluetooth v2.0
[ 2921.818696] usbcore: registered new interface driver btusb
And lsusb,
Bus 003 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd
Bluetooth Dongle (HCI mode)
Please let me know if any more information is needed.
I wanted to know what is the issue with the device.
Thanking You,
--
Regards,
Anil Nair
Hi,
>>>> use hcidump. You are stuck with BlueZ 4 since Ubuntu refuses to upgrade to BlueZ 5.
>>>>
>>>
>>> The USB Dongle isnt being discovered nor Can I send or recieve any
>>> file, I used "hcicump" the only output that i am able to get is,
>>>
>>> HCI sniffer - Bluetooth packet analyzer ver 2.5
>>> device: hci0 snap_len: 1500 filter: 0xffffffffffffffff
>>
>> you need to run this as root. And then try hciconfig hci0 up and see if anything goes wrong.
>>
>> If you had btmon, then this would be a lot simpler to test. You just start btmon and then plug in the USB dongle and it would trace every single event.
>
> Generally btmon should be included in the Ubuntu distribution right? I
> tried compiling BlueZ5 from source but its showing me the I have a
> older DBus version. Anyways I will try with "hcidump" and will let you
> know.
>
HCI Event: Command Complete (0x0e) plen 4
Reset (0x03|0x0003) ncmd 1
status 0x00
> HCI Event: Command Complete (0x0e) plen 12
Read Local Supported Features (0x04|0x0003) ncmd 1
status 0x00
Features: 0xff 0xff 0x8d 0xfe 0x8f 0xf9 0x00 0x80
> HCI Event: Command Complete (0x0e) plen 12
Read Local Version Information (0x04|0x0001) ncmd 1
status 0x00
HCI Version: 2.0 (0x3) HCI Revision: 0x2000
LMP Version: 2.0 (0x3) LMP Subversion: 0x410d
Manufacturer: Broadcom Corporation (15)
> HCI Event: Command Complete (0x0e) plen 10
Read BD ADDR (0x04|0x0009) ncmd 1
status 0x00 bdaddr 00:1B:10:00:2A:EC
> HCI Event: Command Complete (0x0e) plen 11
Read Buffer Size (0x04|0x0005) ncmd 1
status 0x00
ACL MTU 1017:8 SCO MTU 64:0
> HCI Event: Command Complete (0x0e) plen 7
Read Class of Device (0x03|0x0023) ncmd 1
status 0x00 class 0x000000
> HCI Event: Command Complete (0x0e) plen 252
Read Local Name (0x03|0x0014) ncmd 1
status 0x00 name 'BCM2045B'
> HCI Event: Command Complete (0x0e) plen 6
Read Voice Setting (0x03|0x0025) ncmd 1
status 0x00 voice setting 0x0060
> HCI Event: Command Complete (0x0e) plen 5
Read Number of Supported IAC (0x03|0x0038) ncmd 1
> HCI Event: Command Complete (0x0e) plen 8
Read Current IAC LAP (0x03|0x0039) ncmd 1
IAC 0x9e8b33 (General Inquiry Access Code)
> HCI Event: Command Complete (0x0e) plen 4
Set Event Filter (0x03|0x0005) ncmd 1
status 0x00
> HCI Event: Command Complete (0x0e) plen 4
Write Connection Accept Timeout (0x03|0x0016) ncmd 1
status 0x00
> HCI Event: Command Complete (0x0e) plen 68
Read Local Supported Commands (0x04|0x0002) ncmd 1
status 0x00
Commands: ffffff03feffcfffffffffff0300f8ff07
> HCI Event: Command Complete (0x0e) plen 4
Write Inquiry Mode (0x03|0x0045) ncmd 1
status 0x00
> HCI Event: Command Complete (0x0e) plen 14
Read Local Extended Features (0x04|0x0004) ncmd 1
status 0x00 page 1 max 0
Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
> HCI Event: Command Complete (0x0e) plen 4
Set Event Mask (0x03|0x0001) ncmd 1
status 0x00
> HCI Event: Command Complete (0x0e) plen 4
Write Default Link Policy Settings (0x02|0x000f) ncmd 1
status 0x00
> HCI Event: Command Complete (0x0e) plen 8
Read Page Scan Activity (0x03|0x001b) ncmd 1
status 0x00 interval 2048 window 18
> HCI Event: Command Complete (0x0e) plen 4
Write Scan Enable (0x03|0x001a) ncmd 1
status 0x00
> HCI Event: Command Complete (0x0e) plen 4
Write Class of Device (0x03|0x0024) ncmd 1
status 0x00
> HCI Event: Command Complete (0x0e) plen 4
Write Local Name (0x03|0x0013) ncmd 1
status 0x00
> HCI Event: Command Complete (0x0e) plen 4
Write Current IAC LAP (0x03|0x003a) ncmd 1
status 0x00
> HCI Event: Command Complete (0x0e) plen 4
Write Scan Enable (0x03|0x001a) ncmd 1
status 0x00
>>>>>> include /sys/kernel/debug/usb/devices from this device.
>>>>>
>>>>> Did you mean the contents in the file? I did not understand.
>>>>
>>>> Yes, there will be section for your controller.
>>>>
>>>
>>> T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
>>> D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
>>> P: Vendor=0a12 ProdID=0001 Rev= 1.00
>>> S: Manufacturer=Bluetooth v2.0
>>> S: Product=Bluetooth V2.0 Dongle
>>> C:* #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=100mA
>>> I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
>>> E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
>>> E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
>>> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
>>> I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
>>> E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
>>> E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
>>> I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
>>> E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
>>> E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
>>> I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
>>> E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
>>> E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
>>> I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
>>> E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
>>> E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
>>> I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
>>> E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
>>> E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
>>> I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
>>> E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
>>> E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
>>> I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
>>> E: Ad=84(I) Atr=02(Bulk) MxPS= 32 Ivl=0ms
>>> E: Ad=04(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms
>>> I:* If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
>>
>> I highly doubt that this is a genuine CSR based dongle. The Rev= 1.00 is pretty much a dead give away that this is wrong and also the If#= 2 is not something you normally find on CSR dongles.
>
> Oh that was the only dongle available and its specifically written in
> the package works only with Windows.Generally its the other way round
> all my devices works in Linux and does not work properly in Windows. I
> was curious as to why its not working in Linux.
>
>> So my wild guess is that one of the HCI commands is actually failing in the init sequence. Now you just need to figure out which one. That happens if you get sold essentially a fake dongle.
>
> Okay they fooled Windows but could not fool Linux. :D.
rfkill had blocked my device. When I enabled it, the device started
working.:). It is working with latest stable kernel 4.2.2.
How can you come to know wheather the device is fake or no?
Thanks for the help Marcel. :).
I hope I can trouble you guys when I require any help. :).
--
Regards,
Anil Nair
HI,
>>> use hcidump. You are stuck with BlueZ 4 since Ubuntu refuses to upgrade to BlueZ 5.
>>>
>>
>> The USB Dongle isnt being discovered nor Can I send or recieve any
>> file, I used "hcicump" the only output that i am able to get is,
>>
>> HCI sniffer - Bluetooth packet analyzer ver 2.5
>> device: hci0 snap_len: 1500 filter: 0xffffffffffffffff
>
> you need to run this as root. And then try hciconfig hci0 up and see if anything goes wrong.
>
> If you had btmon, then this would be a lot simpler to test. You just start btmon and then plug in the USB dongle and it would trace every single event.
Generally btmon should be included in the Ubuntu distribution right? I
tried compiling BlueZ5 from source but its showing me the I have a
older DBus version. Anyways I will try with "hcidump" and will let you
know.
>>>>> include /sys/kernel/debug/usb/devices from this device.
>>>>
>>>> Did you mean the contents in the file? I did not understand.
>>>
>>> Yes, there will be section for your controller.
>>>
>>
>> T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
>> D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
>> P: Vendor=0a12 ProdID=0001 Rev= 1.00
>> S: Manufacturer=Bluetooth v2.0
>> S: Product=Bluetooth V2.0 Dongle
>> C:* #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=100mA
>> I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
>> E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
>> E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
>> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
>> I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
>> E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
>> E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
>> I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
>> E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
>> E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
>> I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
>> E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
>> E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
>> I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
>> E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
>> E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
>> I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
>> E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
>> E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
>> I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
>> E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
>> E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
>> I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
>> E: Ad=84(I) Atr=02(Bulk) MxPS= 32 Ivl=0ms
>> E: Ad=04(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms
>> I:* If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
>
> I highly doubt that this is a genuine CSR based dongle. The Rev= 1.00 is pretty much a dead give away that this is wrong and also the If#= 2 is not something you normally find on CSR dongles.
Oh that was the only dongle available and its specifically written in
the package works only with Windows.Generally its the other way round
all my devices works in Linux and does not work properly in Windows. I
was curious as to why its not working in Linux.
> So my wild guess is that one of the HCI commands is actually failing in the init sequence. Now you just need to figure out which one. That happens if you get sold essentially a fake dongle.
Okay they fooled Windows but could not fool Linux. :D.
--
Regards,
Anil Nair
Hi Anil,
>> use hcidump. You are stuck with BlueZ 4 since Ubuntu refuses to upgrade to BlueZ 5.
>>
>
> The USB Dongle isnt being discovered nor Can I send or recieve any
> file, I used "hcicump" the only output that i am able to get is,
>
> HCI sniffer - Bluetooth packet analyzer ver 2.5
> device: hci0 snap_len: 1500 filter: 0xffffffffffffffff
you need to run this as root. And then try hciconfig hci0 up and see if anything goes wrong.
If you had btmon, then this would be a lot simpler to test. You just start btmon and then plug in the USB dongle and it would trace every single event.
>>>> include /sys/kernel/debug/usb/devices from this device.
>>>
>>> Did you mean the contents in the file? I did not understand.
>>
>> Yes, there will be section for your controller.
>>
>
> T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
> D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=0a12 ProdID=0001 Rev= 1.00
> S: Manufacturer=Bluetooth v2.0
> S: Product=Bluetooth V2.0 Dongle
> C:* #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=100mA
> I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
> E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
> I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
> I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
> I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
> I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
> I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
> I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
> E: Ad=84(I) Atr=02(Bulk) MxPS= 32 Ivl=0ms
> E: Ad=04(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms
> I:* If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
I highly doubt that this is a genuine CSR based dongle. The Rev= 1.00 is pretty much a dead give away that this is wrong and also the If#= 2 is not something you normally find on CSR dongles.
So my wild guess is that one of the HCI commands is actually failing in the init sequence. Now you just need to figure out which one. That happens if you get sold essentially a fake dongle.
Regards
Marcel
Hi All,
I was exploring the linux source 4.2.2, I came accross the following
in the btusb.c,
static const struct usb_device_id blacklist_table[] = {
/* CSR BlueCore devices */
{ USB_DEVICE(0x0a12, 0x0001), .driver_info = BTUSB_CSR },
That is the VID and PID of my device,
Bus 003 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd
Bluetooth Dongle (HCI mode)
Its listed in blacklist is this the reason why the usb bluetooth
dongle is not working?
--
Regards,
Anil Nair
Hi,
>>>> Then again, you are running a 3.13 kernel, that is a pretty old kernel.
>>>
>>> You want me to try it with the latest stable release?
>>
>> That might actually help. Try to run a 4.2 kernel.
I tried the latest stable kernel 4.2, still the USB Bluetooth Dongle
does not seem to work.
Here is the dmesg output,
[ 125.384033] usb 3-1: new full-speed USB device number 3 using uhci_hcd
[ 125.624902] usb 3-1: New USB device found, idVendor=0a12, idProduct=0001
[ 125.624909] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 125.624914] usb 3-1: Product: Bluetooth V2.0 Dongle
[ 125.624919] usb 3-1: Manufacturer: Bluetooth v2.0
[ 125.624928] device: '3-1': device_add
[ 125.625001] bus: 'usb': add device 3-1
[ 125.625019] PM: Adding info for usb:3-1
[ 125.625102] bus: 'usb': driver_probe_device: matched device 3-1
with driver usb
[ 125.625105] bus: 'usb': really_probe: probing driver usb with device 3-1
[ 125.625111] usb 3-1: no default pinctrl state
[ 125.627928] device: '3-1:1.0': device_add
[ 125.627961] bus: 'usb': add device 3-1:1.0
[ 125.627982] PM: Adding info for usb:3-1:1.0
[ 125.628054] device: 'ep_81': device_add
[ 125.628079] PM: Adding info for No Bus:ep_81
[ 125.628082] device: 'ep_82': device_add
[ 125.628102] PM: Adding info for No Bus:ep_82
[ 125.628108] device: 'ep_02': device_add
[ 125.628132] PM: Adding info for No Bus:ep_02
[ 125.628135] device: '3-1:1.1': device_add
[ 125.628147] bus: 'usb': add device 3-1:1.1
[ 125.628157] PM: Adding info for usb:3-1:1.1
[ 125.628176] device: 'ep_83': device_add
[ 125.628200] PM: Adding info for No Bus:ep_83
[ 125.628203] device: 'ep_03': device_add
[ 125.628224] PM: Adding info for No Bus:ep_03
[ 125.628226] device: '3-1:1.2': device_add
[ 125.628240] bus: 'usb': add device 3-1:1.2
[ 125.628250] PM: Adding info for usb:3-1:1.2
[ 125.628265] device: 'ep_84': device_add
[ 125.628287] PM: Adding info for No Bus:ep_84
[ 125.628291] device: 'ep_04': device_add
[ 125.628310] PM: Adding info for No Bus:ep_04
[ 125.628313] device: '3-1:1.3': device_add
[ 125.628324] bus: 'usb': add device 3-1:1.3
[ 125.628336] PM: Adding info for usb:3-1:1.3
[ 125.628352] driver: 'usb': driver_bound: bound to device '3-1'
[ 125.628360] bus: 'usb': really_probe: bound device 3-1 to driver usb
[ 125.628378] device: 'ep_00': device_add
[ 125.628407] PM: Adding info for No Bus:ep_00
[ 125.701507] bus: 'usb': add driver btusb
[ 125.701535] bus: 'usb': driver_probe_device: matched device 3-1:1.0
with driver btusb
[ 125.701538] bus: 'usb': really_probe: probing driver btusb with
device 3-1:1.0
[ 125.701546] btusb 3-1:1.0: no default pinctrl state
[ 125.701576] driver: 'btusb': driver_bound: bound to device '3-1:1.1'
[ 125.701972] device: 'hci0': device_add
[ 125.702012] PM: Adding info for No Bus:hci0
[ 125.702035] device: 'rfkill0': device_add
[ 125.702060] PM: Adding info for No Bus:rfkill0
[ 125.702093] driver: 'btusb': driver_bound: bound to device '3-1:1.0'
[ 125.702099] bus: 'usb': really_probe: bound device 3-1:1.0 to driver btusb
[ 125.702106] bus: 'usb': driver_probe_device: matched device 3-1:1.2
with driver btusb
[ 125.702108] bus: 'usb': really_probe: probing driver btusb with
device 3-1:1.2
[ 125.702113] btusb 3-1:1.2: no default pinctrl state
[ 125.702128] btusb: probe of 3-1:1.2 rejects match -19
[ 125.702131] bus: 'usb': driver_probe_device: matched device 3-1:1.3
with driver btusb
[ 125.702133] bus: 'usb': really_probe: probing driver btusb with
device 3-1:1.3
[ 125.702136] btusb 3-1:1.3: no default pinctrl state
[ 125.702143] btusb: probe of 3-1:1.3 rejects match -19
[ 125.702170] usbcore: registered new interface driver btusb
--
Regards,
Anil Nair
Hi,
> use hcidump. You are stuck with BlueZ 4 since Ubuntu refuses to upgrade to BlueZ 5.
>
The USB Dongle isnt being discovered nor Can I send or recieve any
file, I used "hcicump" the only output that i am able to get is,
HCI sniffer - Bluetooth packet analyzer ver 2.5
device: hci0 snap_len: 1500 filter: 0xffffffffffffffff
>>> include /sys/kernel/debug/usb/devices from this device.
>>
>> Did you mean the contents in the file? I did not understand.
>
> Yes, there will be section for your controller.
>
T: Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0a12 ProdID=0001 Rev= 1.00
S: Manufacturer=Bluetooth v2.0
S: Product=Bluetooth V2.0 Dongle
C:* #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
I:* If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E: Ad=84(I) Atr=02(Bulk) MxPS= 32 Ivl=0ms
E: Ad=04(O) Atr=02(Bulk) MxPS= 32 Ivl=0ms
I:* If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)
>>> Then again, you are running a 3.13 kernel, that is a pretty old kernel.
>>
>> You want me to try it with the latest stable release?
>
> That might actually help. Try to run a 4.2 kernel.
I will have to compile the kernel from source and attach the kernel
image to Ubuntu right?
Is there any documentation avaliable?
--
Regards,
Anil Nair
Hi Anil,
> The following is the output from hciconfig,
>
> hci0: Type: BR/EDR Bus: USB
> BD Address: 00:1B:10:00:2A:EC ACL MTU: 1017:8 SCO MTU: 64:0
> DOWN
> RX bytes:474 acl:0 sco:0 events:18 errors:0
> TX bytes:74 acl:0 sco:0 commands:18 errors:0
so the device gets detected. Which means the basic part works just fine. Commands are also send and received. Question is just if anything is blocking to bring up the controller.
>
> Marcel By "btmon" did you mean "bt-monitor"? Running bt-monitor gives me,
>
> No Adapters found.
use hcidump. You are stuck with BlueZ 4 since Ubuntu refuses to upgrade to BlueZ 5.
>> include /sys/kernel/debug/usb/devices from this device.
>
> Did you mean the contents in the file? I did not understand.
Yes, there will be section for your controller.
>> Then again, you are running a 3.13 kernel, that is a pretty old kernel.
>
> You want me to try it with the latest stable release?
That might actually help. Try to run a 4.2 kernel.
Regards
Marcel
Hi All,
The following is the output from hciconfig,
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1B:10:00:2A:EC ACL MTU: 1017:8 SCO MTU: 64:0
DOWN
RX bytes:474 acl:0 sco:0 events:18 errors:0
TX bytes:74 acl:0 sco:0 commands:18 errors:0
Marcel By "btmon" did you mean "bt-monitor"? Running bt-monitor gives me,
No Adapters found.
> include /sys/kernel/debug/usb/devices from this device.
Did you mean the contents in the file? I did not understand.
> Then again, you are running a 3.13 kernel, that is a pretty old kernel.
You want me to try it with the latest stable release?
--
Regards,
Anil Nair
Hi Anil,
> I have a USB Bluetooth Dongle it detects but i am unable to use it,
> Cannot pair with any mobile device or send any file.
>
> I am using "Ubuntu 14.04 64-bit" with kernel version "3.13.0-65-generic"
>
> Here is the output of dmesg,
>
> [ 2920.744043] usb 3-1: new full-speed USB device number 3 using uhci_hcd
> [ 2920.985498] usb 3-1: New USB device found, idVendor=0a12, idProduct=0001
> [ 2920.985504] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> [ 2920.985507] usb 3-1: Product: Bluetooth V2.0 Dongle
> [ 2920.985510] usb 3-1: Manufacturer: Bluetooth v2.0
> [ 2921.818696] usbcore: registered new interface driver btusb
>
> And lsusb,
>
> Bus 003 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd
> Bluetooth Dongle (HCI mode)
>
> Please let me know if any more information is needed.
>
> I wanted to know what is the issue with the device.
include /sys/kernel/debug/usb/devices from this device. And you might want to run btmon to see if one of the HCI commands is causing a problem. You could also just call hciconfig and see if the device is actually registered since it seems to load the btusb driver.
Then again, you are running a 3.13 kernel, that is a pretty old kernel.
Regards
Marcel