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 -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
