From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 29 17:43:12 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D1EC16A41F for ; Tue, 29 Nov 2005 17:43:12 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FFD343D6E for ; Tue, 29 Nov 2005 17:43:11 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jATHh9J17560; Tue, 29 Nov 2005 12:43:09 -0500 Message-ID: <438C932B.8090609@savvis.net> Date: Tue, 29 Nov 2005 09:43:07 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: faigozhu References: <863blgzdz0.fsf@fastmail.fm> <438B7FB0.5030704@savvis.net> <86psok1jl6.fsf@fastmail.fm> <438B9E3E.5020905@savvis.net> <86ek5019ld.fsf@fastmail.fm> <438BCE22.3050901@savvis.net> <86r79013sw.fsf@fastmail.fm> <438BDEFE.4050400@savvis.net> <86mzjokovf.fsf@fastmail.fm> In-Reply-To: <86mzjokovf.fsf@fastmail.fm> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: Sdpcontrol search timeout in Motorola HS805 headset. X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2005 17:43:12 -0000 ... >>>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. >> >>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 just try to re-plug the device in the different usb slots. see if it changes anything. > 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 l2control should use bd_addr of the _local_ device, i.e. bd_addr of your usb dongle. not headset's bd_addr. > l2ping -a 00:0b:2e:32:65:12 actually, if l2ping works then sdpcontrol should work too. l2ping requires l2cap transaction, which in turn requires acl data transfer and this requires usb bulk transfer. since usb bulk transfers do not work with your device, l2ping should fail too. it will timeout after about a minute and will print result anyway. thanks, max