From owner-freebsd-hackers@freebsd.org Sat Feb 20 00:13:05 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 44E0BAAEB30 for ; Sat, 20 Feb 2016 00:13:05 +0000 (UTC) (envelope-from luislupe@gmx.com) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 AD86E9BA for ; Sat, 20 Feb 2016 00:13:04 +0000 (UTC) (envelope-from luislupe@gmx.com) Received: from localhost ([95.95.94.35]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MQQzk-1aPF9Y0pdk-00TpdJ for ; Sat, 20 Feb 2016 01:12:56 +0100 Date: Sat, 20 Feb 2016 00:12:54 +0000 From: "Luis P. Mendes" To: freebsd-hackers@freebsd.org Subject: kbdmux disabled - error -> keyboard is not useable Message-ID: <20160220001254.GD73442@hp.tbl> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-Provags-ID: V03:K0:SmJQnxiMHpyc+7hxFchPmxUlenlj1OyzMRbX+ppRQcEpW8U1C8F YMUhKiZv439HsWxso4LVNucFlpWlptF4qSheqy13v1brPqA6Srl+pS6PV8lZTdTFsIFpson 3VPLs+1EX91kyOGU3MdNqZ5NvXnO1N1XB+75GuRqMRjWzTuFRGW0MmZBr4ItNx9C8dVxVI0 VtVNWlAqLZ2ms6FaRS4+A== X-UI-Out-Filterresults: notjunk:1;V01:K0:iegtsDeN+o0=:LpsTLKKKXW7LHHkOy+eaId yxrBWYgpqaMLC+S0jtbAWtREL0wRJOq/JC30oup4VtO5p9sW4tFBLcUXatvWwkXKWZCfQA2md d2hZqk5pF1cfhoqCk3IYtslfK7NoLOjTnazH0HfDBNhk3T0zckw4fAmo30GyRxNPagG08LyKf WUaJaiUi08/OF4AdRZgA5JzcCSCvjCTezowarkjIcMgSwroGAwP078o9JjsQ6MqKppkRNR4HM s5xSkVrFXQAb14OxpReFInnhwjKEz7YlNeECTyGWPpLp58W221dk6QE9V6CwemV0ffQbwY8bB yUb8YjbQyMRMheiY/5sjpU9XRH1kSGYEwLOLbK9POhx+9Xvx1xKc57CIojJbB3z6ZMX0fZ10P 649uerTwDf88LU99+XtTw61teNjxIiGoZ9ZnAVpRlI1sHb9bSsCRqgMgBLk2iWMjQEHqB4lMw +jUWS7bqXh+gtzonv/opQrOHalFMAhcQjLz85YKzoaZSwxqPDqrDZm0379CIGGqQe6LL+VSqT TLoW7Nsg9x9kr0HFkXDqid30h+icqqjYZ3jDxeR8MSgWTaZHIK2iNJsWL3PkiwHNGaAXH29mo j0L7wJCNbeh1tWdqMajKAkX7s8Na1b8xMcB5gprnr1GTpRCOIhQ5XK4okcpsF2J9K33R8MbsK Dn8HdUvelZrXyi6lH82NpIrdJIqu2IBmTanfArN56i8XYomArScGFq1FMKJOsvwLD/IBOFbUc 64ZnePJWo5aGb/sAslGM5J7ARwaLVqGztsuV7RJ4MfMDKTE3HAJS/R3Tsgk= 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: Sat, 20 Feb 2016 00:13:05 -0000 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