From owner-freebsd-bluetooth@FreeBSD.ORG Tue Jun 28 01:01:49 2011 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFE75106564A for ; Tue, 28 Jun 2011 01:01:49 +0000 (UTC) (envelope-from freebsd-bluetooth@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id 4DDE68FC19 for ; Tue, 28 Jun 2011 01:01:49 +0000 (UTC) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.186]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPS id E85265C22; Tue, 28 Jun 2011 11:11:01 +1000 (EST) Message-ID: <4E092850.9090103@herveybayaustralia.com.au> Date: Tue, 28 Jun 2011 11:03:12 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20110204 Thunderbird/3.0.11 ThunderBrowse/3.3.4 MIME-Version: 1.0 To: Maksim Yevmenkin References: <4DF46049.6080206@herveybayaustralia.com.au> <4DF53A6F.9080701@herveybayaustralia.com.au> <4DF705C9.7020606@herveybayaustralia.com.au> <4DF7F13C.6090208@herveybayaustralia.com.au> <4DF8430C.3010104@herveybayaustralia.com.au> <4DFA7AB4.3010405@herveybayaustralia.com.au> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: bluetooth@freebsd.org Subject: Re: Asus bluetooth device - 0x1712 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, 28 Jun 2011 01:01:50 -0000 On 06/17/11 08:11, Maksim Yevmenkin wrote: > On Thu, Jun 16, 2011 at 2:50 PM, Da Rock > wrote: > >> On 06/17/11 03:22, Maksim Yevmenkin wrote: >> >>> [...] >>> >>> >>> >>>>>> Probably would if it recognised the product then. What is the correct >>>>>> way >>>>>> to >>>>>> do this then? I know about usbdevs, and the awk script to run, but does >>>>>> anything then need to be added to the driver to pick it up, or should >>>>>> that >>>>>> be all thats needed? >>>>>> >>>>>> >>>>> it does not look at the product. it looks at interface class, subclass >>>>> and protocol. are you sure you are loading ng_ubt(4) from loader.conf? >>>>> are there any error messages from ng_ubt(4) in /var/log/messages? >>>>> >>>>> >>>> devd.conf problem then? I haven't got it in loader.conf, but I did >>>> kldload- >>>> dmesg output (although the last 2 lines disappear when unloaded/loaded: >>>> >>>> ubt0: >>>> on >>>> usbus5 >>>> WARNING: attempt to domain_add(bluetooth) after domainfinalize() >>>> WARNING: attempt to domain_add(netgraph) after domainfinalize() >>>> >>>> >>> if you get ubt0 line then device was recognized and attached. >>> >>> those two WARNING messages are harmless >>> >>> >>> >>>> But ls dev shows no devices, and I can't start bluetooth services: >>>> >>>> >>> ng_ubt(4) does NOT create device nodes in /dev. this question pops up >>> very often. handbook should really be updated to mention this. >>> >>> >>> >>>> /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device >>>> ubt0 >>>> >>>> If it should work, then what am I doing wrong? >>>> >>>> >>> devd(8) will start/stop stack for you automatically. please check >>> devd.conf (look at ubt secion). there is no need to start stack by >>> hand any more. the error is because you are trying to start the stack >>> when its already been started. again, handbook should be updated to >>> reflect that. >>> >> Thanks Max. Sounds like there is updating required in the handbook- but how >> do I test whether its actually working or not? Those are the tests to show >> it works. Perhaps some more decisive tests should be included? >> > well, you could use hccontrol(8) and try to issue a couple of > diagnostic commands, i.e. read_bd_addr, read_local_name, etc. to see > if your device responds to those. Great- that worked. Apologies for the delay in reply, been a tad busy on a few things. > obexapp from ports (comms/obexapp) > is often used to transfer files to/from mobile phones/pdas. > Not all that useful in my experience, plus no need with the 'droid- just use sftp :) > rfcomm_pppd(8) and rfcomm_sppd(1) in combination with ppp(8) are often > used to create data link, i.e. use mobile phone data connection to > connect to the internet. btpand(8) can be used to build > ethernet-over-bluetooth lan. bthidd(8) can be used to connect your > bluetooth keyboard/mouse to your freebsd pc etc. etc. bluetooth audio > is lacking, i might get around to implementing a2dp profile and > possibly avrcp profile but no promises. > > in other word, try to use it and if something does not work - ask > and/or implement it :) > I'll check it out. I did read bluetooth.com, but there are no technical documents available there. Any particular place I should start looking? Also, how about power saving capabilities? Is it possible to turn it off- obviously apart from unloading the kernel module? > thanks, > max >