From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 10 03:37:09 2014 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A824C879 for ; Mon, 10 Nov 2014 03:37:09 +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 5FD7FDB5 for ; Mon, 10 Nov 2014 03:37:09 +0000 (UTC) Received: by mail-vc0-f178.google.com with SMTP id hq12so972910vcb.23 for ; Sun, 09 Nov 2014 19:37:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=zFdwvvl2p8GvGIkmJvZjNA+Qx0BvxwiSxj8nlKL4SA8=; b=V6b7UOJiuQxBZPKeH6C97eOkP4b5n+6m2LGkXQu7Dh6GAAAt2fOFagrT5ukhFj1k00 /KGoKZ4TeNs326Bi2rBsqi44PI/hVmlHHY7KaU3Cb8HbPjpGUimtsAcNwVmMlRYtmSVw BM7WG/tNkEWs0HGcHqcPDjBPZ6vqEE/Lc68oNnwVyah9q4MkcvAYk8eeH6vOf8qr/Dls XLizzvVB8jyoMwn5jh+PlWT+zMgL/8dMYHQmgyBq/eDoBM2dkHfCLmgbngZxCgdG1Xyl qtcOdoVgrxCY08aXQEr+p66vS5drZjtxYphqDT4Ew0NikW8n/8vjPsIuYTch+df9LvLp DvbQ== MIME-Version: 1.0 X-Received: by 10.52.121.167 with SMTP id ll7mr16138967vdb.35.1415590628414; Sun, 09 Nov 2014 19:37:08 -0800 (PST) Received: by 10.31.138.72 with HTTP; Sun, 9 Nov 2014 19:37:08 -0800 (PST) Date: Mon, 10 Nov 2014 14:37:08 +1100 Message-ID: Subject: Re: Logitech K810 - freebsd-bluetooth Digest, Vol 241, Issue 2 From: Anil Gulati To: freebsd-bluetooth@freebsd.org, sk8harddiefast@gmail.com, maksim.yevmenkin@gmail.com Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 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, 10 Nov 2014 03:37:09 -0000 > 1. Re: Logitech K810 Bluetooth keyboard (Maksim Yevmenkin) > > Hi. I have a problem with my Bluetooth keyboard. Is a Logitech k810. The > > problem is the pairing process. Take hours to connect and lose pairing > > after reboot. > are you dual booting? i.e. switching OS and trying to use your > keyboard in both OSs ? > I have the same issue and use the same workaround as sk8harddiefast. Note my post: https://forums.freebsd.org/threads/logitech-k810-bluetooth-keyboard-updated-5-11-2014.39679/page-3#post-227687 This is the PR I created: http://www.freebsd.org/cgi/query-pr.cgi?pr=180722 This is not a result of dual boot / multiple pairings. See the log messages as posted in this thread: https://forums.freebsd.org/threads/logitech-k810-bluetooth-keyboard-updated-5-11-2014.39679/page-3#post-226796 Max, thanks very much for posting. I've worked on this a bit and tried to make sure no other bluetooth devices were in range etc. I routinely wait for pair for quite a few minutes. If you can suggest any tests I'd love to try them. K810 is a great keyboard and I wonder if there are impacts on other bluetooth devices. From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 10 21:18:31 2014 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6E28096C for ; Mon, 10 Nov 2014 21:18:31 +0000 (UTC) Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [IPv6:2001:4b98:c:538::195]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2C2A7CF6 for ; Mon, 10 Nov 2014 21:18:30 +0000 (UTC) Received: from mfilter31-d.gandi.net (mfilter31-d.gandi.net [217.70.178.162]) by relay3-d.mail.gandi.net (Postfix) with ESMTP id A286EA80B0; Mon, 10 Nov 2014 22:18:28 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at mfilter31-d.gandi.net Received: from relay3-d.mail.gandi.net ([217.70.183.195]) by mfilter31-d.gandi.net (mfilter31-d.gandi.net [10.0.15.180]) (amavisd-new, port 10024) with ESMTP id huKz6VF7YztQ; Mon, 10 Nov 2014 22:18:27 +0100 (CET) X-Originating-IP: 31.69.6.81 Received: from galant.ogmig.net (unknown [31.69.6.81]) (Authenticated sender: plunky@ogmig.net) by relay3-d.mail.gandi.net (Postfix) with ESMTPA id E8F00A80B1; Mon, 10 Nov 2014 22:18:21 +0100 (CET) Received: by galant.ogmig.net (Postfix, from userid 1000) id 908572600AD; Mon, 10 Nov 2014 21:20:51 +0000 (GMT) Date: Mon, 10 Nov 2014 21:20:51 +0000 (GMT) From: Iain Hibbert To: george ember Subject: Re: Logitech K810 Bluetooth keyboard In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-bluetooth@freebsd.org 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, 10 Nov 2014 21:18:31 -0000 On Fri, 7 Nov 2014, george ember wrote: > After reboot my hcibump -x > > ember@FreeBSD ~ $ sudo hcidump -x > Password: > HCIDump - HCI packet analyzer ver 1.5 > device: any snap_len: 65535 filter: 0xffffffffffffffff > > HCI Event: Connect Request(0x04) plen 10 > C5 F2 4D 20 1F 00 40 05 00 01 > < HCI Command: Accept Connection Request(0x01|0x0009) plen 7 > C5 F2 4D 20 1F 00 00 > > HCI Event: Command Status(0x0f) plen 4 > 00 01 09 04 > > HCI Event: Role Change(0x12) plen 8 > 00 C5 F2 4D 20 1F 00 00 > > HCI Event: Connect Complete(0x03) plen 11 > 00 0B 00 C5 F2 4D 20 1F 00 01 00 > < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4 > 0B 00 05 00 > > HCI Event: Command Complete(0x0e) plen 6 > 01 0D 08 00 0B 00 > > HCI Event: Link Key Request(0x17) plen 6 > C5 F2 4D 20 1F 00 > < HCI Command: Link Key Request Negative Reply(0x01|0x000c) plen 6 > C5 F2 4D 20 1F 00 > > HCI Event: Command Complete(0x0e) plen 10 > 01 0C 04 00 C5 F2 4D 20 1F 00 > > HCI Event: Disconn Complete(0x05) plen 4 > 00 0B 00 13 This seems consistent with the fact that you put "nokey" in the config file.. the FreeBSD host states that it does not have a key but presumably the keyboard is expecting one (if it has one stored for this host), so the connection is refused, with the reason given "Remote User Terminated Connection" (0x13 at the end) can you show a hcidump of the pairing process, when a PIN is given? also, after the keyboard is paired and the key is known (if you can get that far) what about the dump that time? also, with hcidump .. do you have -V switch? I don't remember if the version available in ports has that (it gives more detail) but if not, feel free to post the actual dump file, as later hcidump (I use 2.5) shows more information, I think regards, iain From owner-freebsd-bluetooth@FreeBSD.ORG Mon Nov 10 23:28:36 2014 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D4444C7B for ; Mon, 10 Nov 2014 23:28:36 +0000 (UTC) Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (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 64B3CC77 for ; Mon, 10 Nov 2014 23:28:36 +0000 (UTC) Received: by mail-wg0-f52.google.com with SMTP id b13so10111218wgh.25 for ; Mon, 10 Nov 2014 15:28:34 -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 :cc:content-type; bh=zbq0qX6fRZwJv4mBQFXPOPmEG9x9TkwRE/k0GBtohxs=; b=OLfhh5Gw8+4PN1OWPTQeoti/N1bxoxhGtUtONs/AwKCYG3lz6BWTHbqOh13Go2nPJ5 gJ70rbfxU5+7w8uwQz+WnScv7W2caKB+WFhAXSrO2bm2f51dIUBmHthmsm1gjdjp/8j8 HXmQ1UxWEA7xNUD/2SC3kUhtaTRwx1q12WeCL28QcZbjC5ow/eknES4wKZNxq1K5i0ZW nEmUC6jZZJH6CPuMvo7DKmrga6Ufw6OXuL1O6kfybjvPOgtdsglUHoKnBo4CpuzTalxR sEEgZp1qzPZvF+DDkD0GcBmnWHM5KxBKZGSx77sLjc8gUWoETNqEn7cs/OXBTAKQVg4N +KhA== MIME-Version: 1.0 X-Received: by 10.180.101.102 with SMTP id ff6mr35642428wib.0.1415662114739; Mon, 10 Nov 2014 15:28:34 -0800 (PST) Received: by 10.27.170.2 with HTTP; Mon, 10 Nov 2014 15:28:34 -0800 (PST) In-Reply-To: References: Date: Mon, 10 Nov 2014 15:28:34 -0800 Message-ID: Subject: Re: Logitech K810 Bluetooth keyboard From: Maksim Yevmenkin To: Iain Hibbert Content-Type: text/plain; charset=UTF-8 Cc: george ember , "freebsd-bluetooth@freebsd.org" 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, 10 Nov 2014 23:28:37 -0000 On Mon, Nov 10, 2014 at 1:20 PM, Iain Hibbert wrote: > On Fri, 7 Nov 2014, george ember wrote: > >> After reboot my hcibump -x >> >> ember@FreeBSD ~ $ sudo hcidump -x >> Password: >> HCIDump - HCI packet analyzer ver 1.5 >> device: any snap_len: 65535 filter: 0xffffffffffffffff >> > HCI Event: Connect Request(0x04) plen 10 >> C5 F2 4D 20 1F 00 40 05 00 01 >> < HCI Command: Accept Connection Request(0x01|0x0009) plen 7 >> C5 F2 4D 20 1F 00 00 >> > HCI Event: Command Status(0x0f) plen 4 >> 00 01 09 04 >> > HCI Event: Role Change(0x12) plen 8 >> 00 C5 F2 4D 20 1F 00 00 >> > HCI Event: Connect Complete(0x03) plen 11 >> 00 0B 00 C5 F2 4D 20 1F 00 01 00 >> < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4 >> 0B 00 05 00 >> > HCI Event: Command Complete(0x0e) plen 6 >> 01 0D 08 00 0B 00 >> > HCI Event: Link Key Request(0x17) plen 6 >> C5 F2 4D 20 1F 00 >> < HCI Command: Link Key Request Negative Reply(0x01|0x000c) plen 6 >> C5 F2 4D 20 1F 00 >> > HCI Event: Command Complete(0x0e) plen 10 >> 01 0C 04 00 C5 F2 4D 20 1F 00 >> > HCI Event: Disconn Complete(0x05) plen 4 >> 00 0B 00 13 > > This seems consistent with the fact that you put "nokey" in the config > file.. the FreeBSD host states that it does not have a key but presumably > the keyboard is expecting one (if it has one stored for this host), so the > connection is refused, with the reason given "Remote User Terminated > Connection" (0x13 at the end) yes :) 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. i've asked the question about dual booting, and, it it does not seem to be the case. so, was the keyboard re-paired? or same pair of devices used with another OS? last time i suggested to pair devices under freebsd. obtain link key from bthid.keys file and program it directly into the host device. this way, device will use it and re-pair would not be needed. another suggestion is to use different dongle with different OS. this was link keys would not clash. > can you show a hcidump of the pairing process, when a PIN is given? also, > after the keyboard is paired and the key is known (if you can get that > far) what about the dump that time? yes, so basically, i think, all is needed is to re-pair keyboard under freebsd. and then make sure to never re-pair it with the same devices on another OS. then it will "just work" thanks max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Nov 11 17:25:32 2014 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3ECD1ED for ; Tue, 11 Nov 2014 17:25:32 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (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 CFC47C6E for ; Tue, 11 Nov 2014 17:25:31 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id bs8so2361244wib.5 for ; Tue, 11 Nov 2014 09:25:30 -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 :cc:content-type; bh=VQWYBA+4O5U/xdazdVC8XZ0G73BDOzkKGSB5Lb4Nrxc=; b=j6gZ3LbHMzbXRE9Iqd/bMM7wyxTZ0+lo1pApWcNAtIxmYsTs83994uy6GKuZIpXThR rGswtZv10m7axuqCrVpKuuv9onFXhOQ8W0IMUSZiPIBhfa0l5SOmK+Nohrc0PJVz+24l wjNhhKmT/+K2r5TYTs7VcC7kokWrZHoiVoKaxiZpG1tPGLEb7O5VVnxRlkRLmCI0KiJa Ayt9pzmFK6Ddw/kDg1uvTdBDrqlUXVbDw9A2mgNzv1gWiYFs64bg5JLQPcY0B625T86b M36G55WxeTl45fQYFgOFkAscndBAPZs6rBNEvJiAaCEY4WG0YFwJA5H5fcj8vnuXSoCg dp1w== MIME-Version: 1.0 X-Received: by 10.194.52.68 with SMTP id r4mr56572760wjo.82.1415726730156; Tue, 11 Nov 2014 09:25:30 -0800 (PST) Received: by 10.27.170.2 with HTTP; Tue, 11 Nov 2014 09:25:30 -0800 (PST) In-Reply-To: References: Date: Tue, 11 Nov 2014 09:25:30 -0800 Message-ID: Subject: Re: Logitech K810 Bluetooth keyboard From: Maksim Yevmenkin To: george ember Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-bluetooth@freebsd.org" 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: Tue, 11 Nov 2014 17:25:32 -0000 On Tue, Nov 11, 2014 at 12:36 AM, george ember wrote: > This is my hcidump -x after reboot (keyboard trying to pair) with pin option sorry, but none of those dumps show PIN request. something is not quite right here. i need access to the hardware to see what's really going on. thanks, max