From owner-freebsd-questions@FreeBSD.ORG Tue Jan 7 08:30:30 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0F817A83 for ; Tue, 7 Jan 2014 08:30:30 +0000 (UTC) Received: from blue.qeng-ho.org (blue.qeng-ho.org [217.155.128.241]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8F3031EC9 for ; Tue, 7 Jan 2014 08:30:29 +0000 (UTC) Received: from fileserver.home.qeng-ho.org (localhost [127.0.0.1]) by fileserver.home.qeng-ho.org (8.14.7/8.14.5) with ESMTP id s078UGCb005927; Tue, 7 Jan 2014 08:30:16 GMT (envelope-from freebsd@qeng-ho.org) Message-ID: <52CBBB18.80302@qeng-ho.org> Date: Tue, 07 Jan 2014 08:30:16 +0000 From: Arthur Chance User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Polytropon , "Christopher J. Ruwe" Subject: Re: Logitech unifying receivers and keyboard ordering (ukbd0/1) References: <20140106192049.1e62a580@dijkstra.cruwe.de> <20140106203112.d5fbc6a7.freebsd@edvax.de> In-Reply-To: <20140106203112.d5fbc6a7.freebsd@edvax.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jan 2014 08:30:30 -0000 On 06/01/2014 19:31, Polytropon wrote: > On Mon, 6 Jan 2014 19:20:49 +0100, Christopher J. Ruwe wrote: >> I am sorry, I know that my question has been addressed quite recently, >> but I cannot find the post, I do not know why. >> >> I have a Logitech mouse with unifying Bluetooth receiver and a >> keyboard attached by USB "wire". When I boot with both devices >> attached, the non-existent keyboard unifying Bluetooth attached >> keyboard becomes ukbd0 and the "wired" ukbd1. Accordingly, my real >> keyboard does not work on either syscons as well as X11 and I cannot >> type on the non-existent. >> >> What I would like to have the "wired2 and "real" keyboard to attach to >> ukbd0 and if that must be the non-existent to ukbd1. What I do now is >> to unplug the Bluetooth dongle when booting to ensure that ordering. I >> usually forget that on first boot, though, ensuring my first rush of >> wild swearing each morning. > > Depending on your kernel konfiguration, there may be two options: > > First, the kbdmux component should enable all detected keyboards > to work "in parallel", so switching from one to another is not > needed, especially if one of them doesn't even exist. A typical > situation is when an AT keyboard (PS/2 keyboard connector) and > a USB keyboard (USB connector) are present. > > Then, there's the kbdcontrol program that allows switching key- > boards. This program can be called by devd to perform the required > action when the USB keyboard is present (or not present). As I > don't own any BT hardware, I can't be more specific on how this > kind of keyboard will be represented to the OS, sorry. > > See "man kbdmux" and "man kbdcontrol" for details. > > Also take a look at /etc/rc.d/syscons. I see that it responds to an rc.conf variable "keyboard".