freebsd-bluetooth Digest, Vol 242, Issue 2

[Anil Gulati]

On 11 November 2014 at 23:00,  <freebsd-bluetooth-request at freebsd.org> wrote:
>    1. Re: Logitech K810 Bluetooth keyboard (Iain Hibbert)
>    2. Re: Logitech K810 Bluetooth keyboard (Maksim Yevmenkin)

> so, i _think_ the keyboard is expecting link key because it was paired
> with this particular host device before.  since the keyboard is
> initiating request, then, it makes me think that the keyboard is _not_
> in the pairing mode.
>
> the questions is: why is the keyboard expecting the key, and, why is
> it not getting it. i vaguely recall (from the previous conversation)
> that the same two devices, i.e. host device and the keyboard were
> paired under another OS, i.e. windows. obviously, generated link key
> is _not_ available to other OS, i.e. freebsd. thus the keyboard must
> be re-paired under freebsd. now, if you boot into windows again, link
> keys would not match and re-pair would be needed again.

Sorry, I'm just catching up and hoping to get through to helping with
testing if possible

I have a Logitech K810 now using with fresh FreeBSD 10.1.

Note the K810 supports retention of three keys and has three pair
buttons dual purposed on the F1, F2, F3 keys for this purpose.

The first time I ran the bluetooth services on my FreeBSD 10.1 install
the pair with the K810 happened so quickly I wasn't quite sure when it
actually happened (nokey, nopin, configured bluetooth/hosts). But I
still got the same old problems next time and thereafter.

I can confirm there is no dual boot or other OS in my scenario. I
achieve pair, log out, reboot, and immediately have pairing problems.
No other devices or OSes involved. Keyboard seems to indicate it is in
pairing mode because the bluetooth blue LED flashes continuously,
which is supposed to mean 'looking for pair'. I also still get
problems even when I power down the keyboard, power up, and press the
'contact' button on the keyboard (and then press the F1 key, which is
required on the K810 to tell it which of the three memory slots you
want to use to record the key/pin in).

I'd really like to help but don't know how. I'm going to look at using
hcidump hcicontrol whatever and see if I can provide useful
information.

If I can get a set of commands to manually apply a connection and pair
set up for the known device MAC address etc. first of all this would
solve my problem (I can script the pair up) and secondly I may
understand better so I can troubleshoot.