From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 24 03:30:30 2014 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BEE2D6CB for ; Mon, 24 Nov 2014 03:30:30 +0000 (UTC) Received: from mail-vc0-x232.google.com (mail-vc0-x232.google.com [IPv6:2607:f8b0:400c:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 77CDEF2D for ; Mon, 24 Nov 2014 03:30:30 +0000 (UTC) Received: by mail-vc0-f178.google.com with SMTP id hq11so3292516vcb.37 for ; Sun, 23 Nov 2014 19:30:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=xOFxSY/fE2fMxbnkhPfzn0nv8gShZsmk427RyJX6Lfg=; b=yd7qg48x7IcKLLnJCjdpSUwMVLJNhDsyc+mGOhoG1uGp0OCjB4kdhbptJcJxS63lRj XBUk5II5znu3yYgVcDHDf/rgO84a2q49BPeKwgv8Y808Rd7WFaxDgBVLsw0W9xnxFEY2 NTqq99vSgOjNROXbQaFh0LIQs5LF46AI4kDxZ7cjrDPk+1VaT2hSNG7vyMjdLAt6CE5O VaDYs5GWEoPYm073GufyEln7mP09B9UasGTmGl+8YtA86Z19ZzPJY5CHwSJQEaeTcetU IhG5yni06kpSSWBuZ9eO6Gs/FQpy+RorodyaBkSwGgPOC1MvaejHUeUxj7FHYC3A7DTy kiuw== MIME-Version: 1.0 X-Received: by 10.221.65.136 with SMTP id xm8mr11227197vcb.62.1416799829411; Sun, 23 Nov 2014 19:30:29 -0800 (PST) Received: by 10.31.138.72 with HTTP; Sun, 23 Nov 2014 19:30:29 -0800 (PST) In-Reply-To: References: Date: Mon, 24 Nov 2014 14:30:29 +1100 Message-ID: Subject: Re: freebsd-bluetooth Digest, Vol 242, Issue 2 From: Anil Gulati To: freebsd-bluetooth@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Nov 2014 03:30:30 -0000 On 11 November 2014 at 23:00, 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.