Date: Sat, 02 May 2009 14:25:29 +0200 From: Dominic Fandrey <kamikaze@bsdforen.de> To: Bruce Cran <bruce@cran.org.uk> Cc: freebsd-stable@freebsd.org Subject: Re: bluetooth troubleshooting Message-ID: <49FC3BB9.6000200@bsdforen.de> In-Reply-To: <20090502114958.76c46f25@gluon.draftnet> References: <49FBF3C2.8010809@bsdforen.de> <20090502114958.76c46f25@gluon.draftnet>
next in thread | previous in thread | raw e-mail | index | archive | help
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!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49FC3BB9.6000200>