Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Nov 2006 14:00:12 -0600
From:      Eric Anderson <anderson@centtech.com>
To:        Maksim Yevmenkin <maksim.yevmenkin@savvis.net>
Cc:        freebsd-bluetooth@freebsd.org, Jona Joachim <jona.joachim@free.fr>
Subject:   Re: Support for Bluetooth Keyboards?
Message-ID:  <456B43CC.1000107@centtech.com>
In-Reply-To: <456B292D.3000509@savvis.net>
References:  <20061126005413.0faaea7b@localhost>	<1164502329.816.8.camel@RabbitsDen.RabbitsLawn.verizon.net> <456B292D.3000509@savvis.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 11/27/06 12:06, Maksim Yevmenkin wrote:
> Alexandre "Sunny" Kovalenko wrote:
>> On Sun, 2006-11-26 at 00:54 +0100, Jona Joachim wrote:
>>> Hi!
>>> I wanted to know if Bluetooth keyboards are likely to work on FreeBSD.
>>> I'm looking at this marvellous object to be precise:
>>> http://www.thinkgeek.com/computing/input/8193/
>>>
>>> They say that they "were able to get the Bluetooth Virtual Laser
>>> Keyboard to work with Mac OSX using the built-in bluetooth support in
>>> the OS."
> 
> then it should work in releng_6 and -current.
> 
>> I am running Apple Bluetooth keyboard on -CURRENT. I order to accomplish
>> that, I have followed steps outlined by Eric Anderson here
>>
>> http://destari.blogspot.com/2006/01/setting-up-bluetooth-mouse-on-freebsd.html
>>
>> There seems to be a quirk in the bthidd which causes it reattach
>> keyboard every couple of minutes, so I am accustomed to seeing vkbd
>>> 10000 being attached but these seem to be harmless enough. YMMV,
>> though.
> 
> hmmm... i'd like to get more information on this. does this happen when 
> you type on the keyboard? or when keyboard is idle?
> 
> if this happens when the keyboard is idle, then, i'd guess, the keyboard 
> simply kills the bluetooth connection to conserve battery. if bluetooth 
> connection was in fact killed then bthidd(8) will close vkbd(4) device 
> and it will, in turn, detach vkbd(4) keyboard.
> 
> in any case, could you please get an hci dump (binary) when this happens 
> and sent it to me? or could you please tell me how to reproduce this 
> locally?


I see something like this too, but with mice.  I use a microsoft 
bluetooth explorer mouse, and when it disconnects and goes into battery 
sleep mode, and then comes back, it registers a new vkbd device.  Here's 
some snippets:

Nov 27 07:10:52 neutrino kernel: kbd: new array size 4
Nov 27 07:10:52 neutrino kernel: kbd1 at vkbd0
Nov 27 07:10:52 neutrino bthidd[833]: Accepted control connection from 
00:50:f2:e9:a1:f1
Nov 27 07:10:52 neutrino bthidd[833]: Accepted interrupt connection from 
00:50:f2:e9:a1:f1
Nov 27 08:01:38 neutrino bthidd[833]: Remote device 00:50:f2:e9:a1:f1 
has closed interrupt connection
Nov 27 08:05:20 neutrino kernel: kbd1 at vkbd1
Nov 27 08:05:20 neutrino bthidd[833]: Accepted control connection from 
00:50:f2:e9:a1:f1
Nov 27 08:05:20 neutrino bthidd[833]: Accepted interrupt connection from 
00:50:f2:e9:a1:f1
Nov 27 09:09:38 neutrino bthidd[833]: Remote device 00:50:f2:e9:a1:f1 
has closed interrupt connection
Nov 27 09:11:46 neutrino kernel: kbd1 at vkbd2
Nov 27 09:11:46 neutrino bthidd[833]: Accepted control connection from 
00:50:f2:e9:a1:f1
Nov 27 09:11:46 neutrino bthidd[833]: Accepted interrupt connection from 
00:50:f2:e9:a1:f1
Nov 27 09:36:33 neutrino bthidd[833]: Remote device 00:50:f2:e9:a1:f1 
has closed interrupt connection
Nov 27 09:38:36 neutrino kernel: kbd1 at vkbd3
Nov 27 09:38:36 neutrino bthidd[833]: Accepted control connection from 
00:50:f2:e9:a1:f1
Nov 27 09:38:37 neutrino bthidd[833]: Accepted interrupt connection from 
00:50:f2:e9:a1:f1
Nov 27 10:25:12 neutrino bthidd[833]: Remote device 00:50:f2:e9:a1:f1 
has closed interrupt connection
Nov 27 10:26:10 neutrino kernel: kbd1 at vkbd4
Nov 27 10:26:10 neutrino bthidd[833]: Accepted control connection from 
00:50:f2:e9:a1:f1
Nov 27 10:26:10 neutrino bthidd[833]: Accepted interrupt connection from 
00:50:f2:e9:a1:f1
Nov 27 10:34:12 neutrino bthidd[833]: Remote device 00:50:f2:e9:a1:f1 
has closed interrupt connection
Nov 27 10:36:13 neutrino kernel: kbd1 at vkbd5
Nov 27 10:36:13 neutrino bthidd[833]: Accepted control connection from 
00:50:f2:e9:a1:f1
Nov 27 10:36:13 neutrino bthidd[833]: Accepted interrupt connection from 
00:50:f2:e9:a1:f1
Nov 27 11:20:16 neutrino bthidd[833]: Remote device 00:50:f2:e9:a1:f1 
has closed interrupt connection
Nov 27 12:12:12 neutrino kernel: kbd1 at vkbd6
Nov 27 12:12:12 neutrino bthidd[833]: Accepted control connection from 
00:50:f2:e9:a1:f1
Nov 27 12:12:12 neutrino bthidd[833]: Accepted interrupt connection from 
00:50:f2:e9:a1:f1
Nov 27 13:05:15 neutrino bthidd[833]: Remote device 00:50:f2:e9:a1:f1 
has closed interrupt connection
Nov 27 13:40:29 neutrino kernel: kbd1 at vkbd7
Nov 27 13:40:29 neutrino bthidd[833]: Accepted control connection from 
00:50:f2:e9:a1:f1
Nov 27 13:40:29 neutrino bthidd[833]: Accepted interrupt connection from 
00:50:f2:e9:a1:f1


Eric




-- 
------------------------------------------------------------------------
Eric Anderson        Sr. Systems Administrator        Centaur Technology
An undefined problem has an infinite number of solutions.
------------------------------------------------------------------------



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?456B43CC.1000107>