From owner-freebsd-current@FreeBSD.ORG Wed Mar 9 23:10:59 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D20316A4CE; Wed, 9 Mar 2005 23:10:59 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACE9943D48; Wed, 9 Mar 2005 23:10:58 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j29NAw43000664; Wed, 9 Mar 2005 15:10:58 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j29NAwRb000663; Wed, 9 Mar 2005 15:10:58 -0800 Date: Wed, 9 Mar 2005 15:10:58 -0800 From: Brooks Davis To: alex Message-ID: <20050309231058.GA31288@odin.ac.hmc.edu> References: <20050309194028.GA17398@odin.ac.hmc.edu> <309e3f53330175bc5da8f788e71812bc@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline In-Reply-To: <309e3f53330175bc5da8f788e71812bc@gmail.com> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-current@freebsd.org cc: freebsd-usb@freebsd.org Subject: Re: KVM USB X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2005 23:10:59 -0000 --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [Please don't top-post.] On Wed, Mar 09, 2005 at 05:54:23PM -0500, alex wrote: > Brooks, >=20 > What I actually did and it seems to work was that I changed dev.conf =20 > this way: (I changed the device name to "ukbd1" instead of "ukbd0"=20 > because when my keyboard remounts itself after being unplugged its=20 > called "ukbd1". Do you think this may cause some other issues Im not=20 > aware of yet? Here is my modified dev.conf snippet. Ah, intresting. I suppose it's to too suprising that kbd0 doesn't=20 detach enough to let that slot be reused. If that works it's probably OK. -- Brooks > # When a USB keyboard arrives, attach it as the console keyboard > attach 100 { > device-name "ukbd1"; > action "test -c /dev/kbd1 && kbdcontrol -k /dev/kbd1 <=20 > /dev/console"; > }; > detach 100 { > device-name "ukbd1"; > action "kbdcontrol -k /dev/kbd0 < /dev/console"; > }; >=20 >=20 > On Mar 9, 2005, at 2:40 PM, Brooks Davis wrote: >=20 > >On Wed, Mar 09, 2005 at 02:10:49PM -0500, Alex Welycz wrote: > >>All, > >> > >>I'm using FreeBSD 5.3 and I've run into a bit of a problem. I am using > >>a KVM switch that does not keep a live connection to the computer when > >>switching between computers ie. the computers show that the usb > >>keyboard/mouse are unplugged when you switch between them. My problem > >>occurs when the i switch from my Windows box back to my FreeBSD box. > >>The USB deamon on the BSD box shows that the keyboard is recognized > >>and loads it but when i try to use the keyboard nothing comes up. The > >>USB keyboard does work when I reboot the BSD box and dont switch > >>between computers. Now how I get the USB keyboard to work when i > >>switch between computers I have to run this script. > >> > >>sleep 15 > >>kbdcontrol -k /dev/kbd1 < /dev/ttyv0 > /dev/null > >> > >>Apparently when I reboot the box everything works fine, the USB > >>keyboard is accessed as > >> > >>kbd0 -> ukbd0 > >> > >>but when I switch between boxes and switch back the keyboard doesnt > >>get mounted at > >> > >>kbd0 -> ukbd0 but instead is mounted at kbd1 -> ukbd1. > >> > >>So my question is how do I get FreeBSD to always mount the keyboard as > >>kbd0 -> ukbd0 and not kbd1 -> ukbd1 > >> > >>Because upon bootup my kbdcontrol is called as: > >> > >> kbdcontrol -k /dev/kbd0 < /dev/ttyv0 > /dev/null and cannot be called > >>wih kbd1 because at bootup that device does not exist, and also that > >>device disappears when I swicth to my other computer so kbdcontrol > >>sets itself back to kbd0. > > > >This is caused by a bug in /etc/devd.conf that I fixed a week ago in 5. > >Just change the line to refer to ukbd0 instead of bogusly refering to > >kbd1. The problem was caused by crappy examples in the manpage making > >me think you had to use the generic /dev/kbd# device not the specific > >/dev/ukdb# device with kbdcontrol. > > > >-- Brooks > > > >--=20 > >Any statement of the form "X is the one, true Y" is FALSE. > >PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFCL4KBXY6L6fI4GtQRAgc6AKC21GGW5qshmndtS42C4DDyO8wBeACgmZW0 //c6J5jn4UgUto06yOm4ujw= =XUfH -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0--