From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 29 00:18:24 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 6FEFC16A41F for ; Tue, 29 Nov 2005 00:18:24 +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 7C26A43D76 for ; Tue, 29 Nov 2005 00:18: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 jAT0I8J24240; Mon, 28 Nov 2005 19:18:08 -0500 Message-ID: <438B9E3E.5020905@savvis.net> Date: Mon, 28 Nov 2005 16:18:06 -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> In-Reply-To: <86psok1jl6.fsf@fastmail.fm> Content-Type: text/plain; charset=ISO-8859-1; 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 00:18:24 -0000 >>> I have a Motorola HS805 headset and got the following message. >>> #sdpcontrol -a 00:0b:2e:32:65:12 search HSET Could not execute >>> command "search". Operation timed out >> >> did you try to repeat this command several times? does it always >> fail with timeout? > > yes. ok >>> It seems no response from the headset after sending >>> Link_Key_Reply? >> >> sigh... people, please, PLEASE, stop posting text hci dump. they >> are not very useful. they give me some idea, but what i really need >> is _binary_ hci dump. > > Sorry for that. The attached file is a binary file of "hcidump -w hcidump.log". thanks. unfortunately, this binary dump did not reveal the problem. i'd like you to try the following: 1) reboot 2) attach usb bluetooth dongle and start bluetooth stack 3) as root # hcidump -w headset.dump 4) as root # hccontrol -n ubt0hci create_connection 00:0b:2e:32:65:12 make sure hccontrol succeeded and created baseband connection. it should print connection handle. 5) wait a few seconds, and run % sdpcontrol -a 00:0b:2e:32:65:12 search HSET you may try step 5) a couple more times. please wait few seconds between each try. 6) kill hcidump with ^c and send me the headset.dump file also, i assume, you have paired less then 8 devices with this headset, correct? some headsets can only remember one host, but this one seems to be able to remember up to 8 (according to specs). also, if this is not too much trouble, you could reset the headset and try the steps 1-6 from above again. thanks, max