Asus bluetooth device - 0x1712

Da Rock freebsd-bluetooth at herveybayaustralia.com.au
Tue Jun 28 01:01:50 UTC 2011


On 06/17/11 08:11, Maksim Yevmenkin wrote:
> On Thu, Jun 16, 2011 at 2:50 PM, Da Rock
> <freebsd-bluetooth at herveybayaustralia.com.au>  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:<vendor 0x0b05 product 0x1712, class 224/1, rev 2.00/19.15, addr 2>
>>>>   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
>    



More information about the freebsd-bluetooth mailing list