From owner-freebsd-stable@FreeBSD.ORG  Sat May  2 12:25:32 2009
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 C4D5C106566C
	for <freebsd-stable@freebsd.org>; Sat,  2 May 2009 12:25:32 +0000 (UTC)
	(envelope-from kamikaze@bsdforen.de)
Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79])
	by mx1.freebsd.org (Postfix) with ESMTP id 82A468FC0A
	for <freebsd-stable@freebsd.org>; Sat,  2 May 2009 12:25:32 +0000 (UTC)
	(envelope-from kamikaze@bsdforen.de)
Received: from mobileKamikaze.norad (unknown [88.130.204.127])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.bsdforen.de (Postfix) with ESMTP id D5FE78A01A0;
	Sat,  2 May 2009 14:25:30 +0200 (CEST)
Message-ID: <49FC3BB9.6000200@bsdforen.de>
Date: Sat, 02 May 2009 14:25:29 +0200
From: Dominic Fandrey <kamikaze@bsdforen.de>
User-Agent: Thunderbird 2.0.0.21 (X11/20090408)
MIME-Version: 1.0
To: Bruce Cran <bruce@cran.org.uk>
References: <49FBF3C2.8010809@bsdforen.de>
	<20090502114958.76c46f25@gluon.draftnet>
In-Reply-To: <20090502114958.76c46f25@gluon.draftnet>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 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 <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 02 May 2009 12:25:33 -0000

Bruce Cran wrote:
> On Sat, 02 May 2009 09:18:26 +0200
> Dominic Fandrey <kamikaze@bsdforen.de> wrote:
> 
>> # /etc/rc.d/bluetooth onestart ubt0
>> /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for
>> device ubt0 # /etc/rc.d/bluetooth onestart ubt1
>> /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for
>> device ubt1
>>
>> This error message gives me no idea of what is wrong. The handbook
>> mentions comms/hcidump for debugging, but I think this is meant
>> for analyzing bluetooth traffic.
>> As you can see I haven't gotten far enough to produce any traffic to
>> analyse. Is someone here familiar with bluetooth and can provide
>> me with a command that might reveal something about the nature
>> of my problem?
> 
> I think devd now automatically starts the Bluetooth stack when you
> plug in a recognised device, so you'll only be able to use onestart
> after first running onestop.
> 

So it's already working! I was confused because the output of

# 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]


Thanks a lot!