Udayan Singh wrote: > okay.. here is what i tried.. first a cat of /proc/bus/usb/devices > with the bluetooth dongle, then a cat .... without the dongle and the > result is below.. > > > 36c36 > < B: Alloc= 27/900 us ( 3%), #Int= 1, #Iso= 2 > --- >> B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 > 46,74d45 > < T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 > < D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=16 #Cfgs= 1 > < P: Vendor=1131 ProdID=1001 Rev= 3.73 > < S: Product=ISSCBTA <-----------------------[ SNIP ]---------------------> > < I: If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none) > < > > the last one "< I: If#= 2 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 > Driver=(none)", does not have a driver, so how do i know if my device > is configured (has a driver) ? > > any inputs would be really good.. > It is harder to read as a diff output then just pasting the proper section from the file, but this does look like your bluetooth dongle. The Driver=(none) is not a good sign. From a Google search on the Product and vendor IDs, it looks like it may not work if plugged in at boot, but it starts working if you unplug it, and then plug it in again. It is worth a try. On another note, please do not top post, and try your reply. At the very least, trim off the signatures from the post. Mikkel -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting a bad thing?
Attachment:
signature.asc
Description: OpenPGP digital signature
