From owner-freebsd-stable@FreeBSD.ORG Mon May 4 14:55:23 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C360106564A for ; Mon, 4 May 2009 14:55:23 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id E41648FC18 for ; Mon, 4 May 2009 14:55:22 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 15B67336F95; Mon, 4 May 2009 10:55:22 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 04 May 2009 10:55:22 -0400 X-Sasl-enc: 7QeG2VcX9yvQL9tI10bFJ/aX/tGi695D2w3tb36/VHP0 1241448921 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 4319D28D93; Mon, 4 May 2009 10:55:21 -0400 (EDT) Message-ID: <49FF01D6.5020607@incunabulum.net> Date: Mon, 04 May 2009 15:55:18 +0100 From: Bruce Simpson User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: Daniel O'Connor References: <49FBF3C2.8010809@bsdforen.de> <20090502114958.76c46f25@gluon.draftnet> <49FC3BB9.6000200@bsdforen.de> <200905042020.24783.doconnor@gsoft.com.au> In-Reply-To: <200905042020.24783.doconnor@gsoft.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Bruce Cran , Dominic Fandrey , freebsd-stable@freebsd.org Subject: Re: bluetooth troubleshooting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 May 2009 14:55:23 -0000 Daniel O'Connor wrote: > On Sat, 2 May 2009, Dominic Fandrey wrote: > >> # hccontrol -n ubt0hci inquiry >> Inquiry complete. Status: No error [00] >> >> is pretty lame compared to what should appear according to the >> handbook: >> >> % hccontrol -n ubt0hci inquiry >> Inquiry result, num_responses=1 >> Inquiry result #0 >> BD_ADDR: 00:80:37:29:19:a4 >> Page Scan Rep. Mode: 0x1 >> Page Scan Period Mode: 00 >> Page Scan Mode: 00 >> Class: 52:02:04 >> Clock offset: 0x78ef >> Inquiry complete. Status: No error [00] >> > > Depends what's in range. > > Your command indicates to me that there are no _discoverable_ BT modules > in range. (Note the discoverable part :) > > Not all devices need be INQUIRE-able. Some may not have INQUIRE scan enabled. In that case you need to know the Bluetooth address of the device you're looking for so you can PAGE it. If you're expecting to see a mobile phone or other handheld device you might need to enable discoverability on the device itself. There are also other IAC codes used for INQUIRY, but generally these aren't used. cheers, BMS