Sdpcontrol search timeout in Motorola HS805 headset.

[faigozhu]

Maksim Yevmenkin <maksim.yevmenkin at savvis.net> writes:

...
...

> > F8T008. Another usb device is a usb mouse.
> > Both of them directly connection to my laptop, no usb hub.
> 
> i guess you could try to plug it into different usb slots. use
> 
> # usbdevs -dv
> 
> to see where it got connected. if you have usb hub around try to plug
> it through hub. i have f8t001 in my collection, and, it works for
> me. f8t001 is a broadcom bcm2033 chip based device, so i need to
> download firmware into it to make it work. i will see if i can get
> f8t008 cheap locally.
> 
> > dmesg|grep uhci
> > uhci0: <Intel 82801DB (ICH4) USB controller USB-A> port 0x1820-0x183f irq 16 at device 29.0 on pci0
> > uhci0: [GIANT-LOCKED]
> > usb0: <Intel 82801DB (ICH4) USB controller USB-A> on uhci0
> > uhci1: <Intel 82801DB (ICH4) USB controller USB-B> port 0x1840-0x185f irq 19 at device 29.1 on pci0
> > uhci1: [GIANT-LOCKED]
> > usb1: <Intel 82801DB (ICH4) USB controller USB-B> on uhci1
> > uhci2: <Intel 82801DB (ICH4) USB controller USB-C> port 0x1860-0x187f irq 18 at device 29.2 on pci0
> > uhci2: [GIANT-LOCKED]
> > usb2: <Intel 82801DB (ICH4) USB controller USB-C> on uhci2
> 
> what does
> 
> # usbdevs -dv
> 
> say?

usbdevs -dv
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
  uhub0
 port 1 powered
 port 2 powered
Controller /dev/usb1:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
  uhub1
 port 1 powered
 port 2 powered
Controller /dev/usb2:
addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00
  uhub2
 port 1 addr 2: low speed, power 100 mA, config 1, product 0x0000(0x0000), vendor 0x062a(0x062a), rev 0.00
   ums0
 port 2 powered
Controller /dev/usb3:
addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x0000), rev 1.00
  uhub3
 port 1 powered
 port 2 powered
 port 3 powered
 port 4 powered
 port 5 powered
 port 6 powered

> 
> > Is that any solution? Or, likely NDIS, to use windows native driver?
> 
> at this point, it does look like usb related problem. try different
> usb dongle. i recommend csr chip based devices. you can not use
> windows native driver with freebsd ndis'ulator. it wont work.
> 
> thanks,
> max

I am pretty sure I got l2ping works by a script but I just can't repeat it.

cat cmds.sh
#!/bin/sh
hccontrol -n ubt0hci create_connection 00:0b:2e:32:65:12
hccontrol -n ubt0hci read_connection_list 
#[msg:network is down]l2control -a 00:0b:2e:32:65:12 read_channel_list
l2ping -a 00:0b:2e:32:65:12



-- 
Many thanks,
Faigozhu