From owner-freebsd-questions@FreeBSD.ORG Tue Jun 10 14:08:41 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 711ED37B401 for ; Tue, 10 Jun 2003 14:08:41 -0700 (PDT) Received: from jane.spongocoel.com (gate.louisianaweekly.com [65.245.4.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95F1243F85 for ; Tue, 10 Jun 2003 14:08:40 -0700 (PDT) (envelope-from scrotch@sprynet.com) Received: from sprynet.com (localhost [127.0.0.1]) by jane.spongocoel.com (8.12.9/8.12.6) with ESMTP id h5AL8dPR002682 for ; Tue, 10 Jun 2003 16:08:40 -0500 (CDT) Date: Tue, 10 Jun 2003 16:08:39 -0500 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) From: Scott Saunders To: freebsd-questions@FreeBSD.ORG Content-Transfer-Encoding: 7bit In-Reply-To: <200306102047.aa60227@salmon.maths.tcd.ie> Message-Id: X-Mailer: Apple Mail (2.552) Subject: Re: USB keyboard and KVM X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2003 21:08:41 -0000 Thank you for your reply. But it's still not working. More below... On Tuesday, June 10, 2003, at 02:47 PM, Ian Dowse wrote: > In message <49AD623F-9B60-11D7-B332-003065D644E8@sprynet.com>, Scott > Saunders w > rites ... >> ... >> I added: >> kbdcontrol -k /dev/kbd0 < /dev/ttyv0 > /dev/null >> to the end of /etc/rc.i386 based on the FAQ. > > The above command will only run once when the machine boots, so you > need to have something that repeats this when the keyboard is > (effectively) plugged back in after being removed. Try adding the > following lines near the end of /etc/usbd.conf instead: > > device "Keyboard" > devname "ukbd0" > attach "kbdcontrol -k /dev/kbd0 < /dev/ttyv0" I added this and tried it with and without the kbdcontrol line in /etc/rc.i386. Unfortunately, it doesn't seem to make any difference. It certainly looks to my inexperienced eyes like it should. I can SSH in (and maybe this will be the permanent solution). If I run kbdcontrol -k /dev/kbd0 < /dev/ttyv0 while it's 'locked up' I get: kbdcontrol: cannot open /dev/kbd0: Device busy So maybe it didn't close down the connection to the keyboard? If that's anything like how it actually works. I tried plugging the keyboard directly into the machine (not through the KVM) while it was 'locked up', but that had no effect either. Are you using a set up like this, Ian? Thanks again, Scott Saunders