From owner-freebsd-hackers@freebsd.org Mon Feb 22 23:17:19 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 939EDAB0423 for ; Mon, 22 Feb 2016 23:17:19 +0000 (UTC) (envelope-from luislupe@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 09ADF1BBB for ; Mon, 22 Feb 2016 23:17:18 +0000 (UTC) (envelope-from luislupe@gmx.com) Received: from localhost ([95.95.94.35]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0La2Xx-1a67gZ3ME9-00lm1O for ; Tue, 23 Feb 2016 00:17:11 +0100 Date: Mon, 22 Feb 2016 23:17:08 +0000 From: "Luis P. Mendes" To: freebsd-hackers@freebsd.org Subject: Re: kbdmux disabled - error -> keyboard is not useable Message-ID: <20160222231708.GE73442@hp.tbl> References: <20160220001254.GD73442@hp.tbl> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20160220001254.GD73442@hp.tbl> User-Agent: Mutt/1.5.24 (2015-08-30) X-Provags-ID: V03:K0:CqmQomnkn99wP8hvZxJGTuXe6j1Fr/OQdnPAYje3nbrYI9+FZN6 FSqka9BDKE0T7TsRLWY4KfeEGriI7fMeRkaDx6ElOOTHRH1/nNpEqxxbc7N+zbZZREYL7zz Sbkh5ZtzqSnIvPAfAmaY5w6/mWUzOX/rJNx/y9NCj8Xr6nhT6cAOieac34ZCMtYCDqMpFLz K7tLiYvyd9qr8IZnMQYQg== X-UI-Out-Filterresults: notjunk:1;V01:K0:3aJ4X7N6mvU=:dgIF+uczi7kP2UeZ1y2Adm DJz6tTcV5aGY/P7Am89N6LiSKWrv3vfbH9aGxzXx3D/ZO/53BKCOaygRnJn82HgsmYbR3QMWi pokkjgjvV/pMHwszU8QD1W9m3qeomlKtLre/8wkteD53RJA//vYs3RA8ImuKNQjc7RWiinmq1 94cwtEACeKBdy3DREMbx89KekyFEWT6YS5irMZ2hqw4TMawyUN5kCcjtOWGOkhyROlAphLn08 NQ+SwhPKAxYGeuaO5BSZDuUi1mXXFXkHf2vxyzTSL8+WFAsYIhjs2q6Mf6TEbgu1PXdP58AGP yJrG72uje2Q6BT1GH7F29tUelz54TPyyBgy79J4dQRBQc3ah/DPUpS8Y3JzcGHISKXQF1crSw sxUTLg6l3A6+8RtbX0v3yL2ntK7lFDysC/HXow1LA44I1lier/ujTPra/oAdQQOdeyYffdR0Y qzyErTx0eL5Gm8G+AMpH0w1ny9KiL/krmr+rReZk731PEDGSeS1E3j4Fy9NkhUix5J2XyJw5+ GUNfcs1JBwMG+AMSADAizYtce0OaflzQ02ERtRorNwRHwEh4KHbugAnvpPQPwk/AYPB/zqS/s vyh+9igqp5dVl3pgGuuSkaajhGUnmv27zuEfZmpI8xCMIOZ1lUOyTR7QAmpcTio6w26mhYxql OySrVVXvSt8xmHtg+aozQXKR+uzA7xK8cJEOiJD6ELzZk4WpTGhdJqRk/gGL6RsNy2mUipDJc aSwMvdlr/drAszaOMpcxtowLmsVlRuKH8uY5fsVdrch5eWls/5puTRWXjRw= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Feb 2016 23:17:19 -0000 On 2016.02.20 00:12:54 +0000, Luis P. Mendes wrote: I got no replies to this, where should I post this problem? To another mailing list? Which one? Other place? Thanks in advance, Luis > Hi, > > -------------------------- > My FreeBSD version is: > # uname -a > FreeBSD leao 10.3-BETA1 FreeBSD 10.3-BETA1 #0 r295321: Fri Feb 5 > 17:02:27 WET 2016 > > I'm using stock kernel. > -------------------------- > > > I'm setting up a multiseat workstation, where two users, with two > monitors, two keyboards, two mice and two X sessions can be > connected to the same computer at the same time. > > For this to happen, one of the things that is necessary to do is to > disable kbdmux in order for the two keyboards to be considered > independent. > > In the past, I've accomplished this with syscon, which had other > problems. But now with vt, when I disable kbdmux either on > /boot/device.hints or in /boot/loader.conf with: > hint.kbdmux.0.disabled="1" > > No keys are recognized by the OS, although /var/log/messages seems to > know about the existence of the USB keyboard, although it shows an > error. > > > The steps I've taken: > 1. Have an USB keyboard attached to the motherboard. > The keyboard is a Logitech K120 with no multimedia keys, just a 105 > key with PT layout. The keyboard works fine when kbdmux is not > disabled, and works fine in every other computer/OS. > No AT keyboard used. > > > 2. In /boot/loader.conf, have these lines added: > ukbd_load="YES" > hint.kbdmux.0.disabled="1" > hint.atkbd.0.disabled="1" > hint.atkbdc.0.disabled="1" > > I tried it with both *atkbd* lines commented in and out and the > result is the same. > > > 3. In /etc/rc.conf > kbdcontrol -k /dev/ukbd0 < /dev/console > > > 4. After commenting the two atk lines in /boot/loader.conf, what I got > from: > # ll /dev/*kbd* > crw------- 1 root wheel 0x34 18 Fev 14:34 /dev/atkbd0 > lrwxr-xr-x 1 root wheel 6 18 Fev 14:34 /dev/kbd0@ -> atkbd0 > lrwxr-xr-x 1 root wheel 5 18 Fev 14:34 /dev/kbd1@ -> ukbd0 > crw------- 1 root wheel 0x81 18 Fev 14:34 /dev/ukbd0 > > > 5. In /var/log/messages, there are these lines: > # egrep -i -e 'kbd|keyb' messages > Feb 18 14:34:58 leao kernel: module_register_init: MOD_LOAD (kbdmux, > 0xffffffff805d4070, 0) error 6 > Feb 18 14:34:58 leao kernel: atkbdc0: > at port 0x60,0x64 on isa0 > Feb 18 14:34:58 leao kernel: atkbd0: irq 1 on atkbdc0 > Feb 18 14:34:58 leao kernel: kbd0 at atkbd0 > Feb 18 14:34:58 leao kernel: atkbd0: [GIANT-LOCKED] > Feb 18 14:34:58 leao kernel: ukbd0: on usbus0 > Feb 18 14:34:58 leao kernel: kbd1 at ukbd0 > Feb 18 14:34:58 leao kernel: uhid0: on usbus0 > > It seems there's an error 6 regarding kbdmux... > > > 6. # dmesg | grep kbd > module_register_init: MOD_LOAD (kbdmux, 0xffffffff805d4070, 0) error 6 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > ukbd0: on usbus0 > kbd1 at ukbd0 > > > This is the only thing keeping me from using my workstation the way I > need. I hope there's some fix to this. > > > How to correct this problem? Is this a bug? > > > -- > > > Luis Mendes > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" -- Luis Vale Mendes