From owner-freebsd-bluetooth@FreeBSD.ORG Thu Aug 11 16:31:39 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 4F4C716A41F for ; Thu, 11 Aug 2005 16:31:39 +0000 (GMT) (envelope-from maksim.yevmenkin@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3F5F43D49 for ; Thu, 11 Aug 2005 16:31:38 +0000 (GMT) (envelope-from maksim.yevmenkin@gmail.com) Received: by rproxy.gmail.com with SMTP id i8so319736rne for ; Thu, 11 Aug 2005 09:31:38 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=N2/pnntTzrGI3zywy+kmzciRhijARo9ojmM7aFDskWz9MZTpI1/sJDvFjxzywFTUfOItAf+UU4sz8jZv2SXZL8ltxdG3cot1DLcOOQcr0mTHqmEOa0s2Yzdw8g76VILT8QradAEbA5veL7ZnNrjC8gnXlVt4QhsSiRKK8pnNBVw= Received: by 10.38.97.60 with SMTP id u60mr700958rnb; Thu, 11 Aug 2005 09:31:38 -0700 (PDT) Received: by 10.38.208.5 with HTTP; Thu, 11 Aug 2005 09:31:38 -0700 (PDT) Message-ID: Date: Thu, 11 Aug 2005 09:31:38 -0700 From: Maksim Yevmenkin To: Bill Kirkland In-Reply-To: <42FB7A45.9060206@savvis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <42FB7A45.9060206@savvis.net> Cc: freebsd-bluetooth@freebsd.org Subject: Re: usb bluetooth 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: Thu, 11 Aug 2005 16:31:39 -0000 Bill, > I am having difficulties with the configuration of my sony DR-BT1 > wireless headset. > I have appended the output from diagnostic commands I believe to be relev= ent, > though it is apparent I am not understanding something ... any > assistance would be > greatly appreciated. lets take a look > Aug 10 20:32:22 ash syslogd: kernel boot file is /boot/kernel/kernel > Aug 10 20:32:22 ash kernel: ubt0: Broadcom Bluetooth USB Dongle, rev > 1.10/0.03, addr 2 > Aug 10 20:32:22 ash kernel: ubt0: Interface 0 endpoints: > interrupt=3D0x81, bulk-in=3D0x82, bulk-out=3D0x2 > Aug 10 20:32:22 ash kernel: ubt0: Interface 1 (alt.config 4) > endpoints: isoc-in=3D0x83, isoc-out=3D0x3; wMaxPacketSize=3D64; nframes= =3D5, > buffer size=3D320 [...] everything looks the way it should. no problem here > + hccontrol -n ubt0hci inquiry > Inquiry result, num_responses=3D1 > Inquiry result #0 > BD_ADDR: headset > Page Scan Rep. Mode: 0x1 > Page Scan Period Mode: 00 > Page Scan Mode: 00 > Class: 20:04:04 > Clock offset: 0x34de > Inquiry result, num_responses=3D1 > Inquiry result #0 > BD_ADDR: headset > Page Scan Rep. Mode: 0x1 > Page Scan Period Mode: 00 > Page Scan Mode: 00 > Class: 20:04:04 > Clock offset: 0x34de > Inquiry result, num_responses=3D1 > Inquiry result #0 > BD_ADDR: headset > Page Scan Rep. Mode: 0x1 > Page Scan Period Mode: 00 > Page Scan Mode: 00 > Class: 20:04:04 > Clock offset: 0x34de > Inquiry result, num_responses=3D1 > Inquiry result #0 > BD_ADDR: headset > Page Scan Rep. Mode: 0x1 > Page Scan Period Mode: 00 > Page Scan Mode: 00 > Class: 20:04:04 > Clock offset: 0x34de > Inquiry complete. Status: No error [00] this looks great too, except for duplicated inquiry response messages. i really puzzled why is this happening, but i can tell that this does not seem like bluetooth code fault. i have broadcom chip based bluetooth dongle myself (belkin f8t001) and it has similar behavior. i checked hcidump and in my case device indeed sends these duplicated inquiry response messages. i have never seen this with csr chip based bluetooth devices. > + hccontrol -n nbt0hci remote_name_request headset > Could not execute command "remote_name_request". Operation timed out this is strange. could you please run hcidump while you are doing "remote_name_request" and verify that you are getting back responses from the device? hcidump can be installed from the ports collection comms/hcidump. did you try to execute this command few times in a row?=20 you could also try to specify different "page scan repetition mode", "page scan mode" and "clock offset", i.e. beetle% hccontrol help remote_name_request Usage: remote_name_request The Remote_Name_Request command is used to obtain the user-friendly name of another Bluetooth unit. - xx:xx:xx:xx:xx:xx BD_ADDR or name - dd; page scan repetition mode [0-2] - dd; page scan mode [0-3] - xxxx; clock offset [0 - 0xffff] thanks, max