"Inquiry failed: Connection timed out" - question again

hello.

i know this question was raised on numerous lists before and different
answers were given, however i have never found a satisfying answer,
i hope i do not annoy people by asking it again.
i try to use a usb bluetooth (an MSI in my case) device (using debian
and sometimes openwrt)

i guess you all know this situation:

  # hcitool scan
  Scanning ...
  Inquiry failed: Connection timed out

then you try 

  hciconfig -a
  hci0:   Type: USB
        BD Address: 08:00:xx:xx:xx:xx ACL MTU: 339:4 SCO MTU: 64:9
        UP RUNNING 
        RX bytes:45 acl:0 sco:0 events:4 errors:0
        TX bytes:6 acl:0 sco:0 commands:13 errors:0
        Features: 0xff 0x3b 0x05 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH HOLD SNIFF PARK 
        Link mode: SLAVE ACCEPT 
  Can't read local name on hci0: Connection timed out (110)

or "error (5)"

in some answers i was told to do 

  hcitool hci0 reset

however, this sometimes failed as well, if not it might improve the
situation, sometimes not, so im not sure if its really connected to the
issue. sometimes rebooting or replugging the BT usb device helped (for
a while)

in the beginning i thought it had to do with the question if the device
is connected via a hub or not, but it failed without a hub in between,
too.

can anybody point me to a real answer to this problem which tells me
what is causing this? furthermore, what exactly is the best way to
avoid it and what does "reset" do (if it helps at all)

is this at all hardware related? related to the usb device, the usb
controller?

thx,
w.




 







-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/