From owner-freebsd-stable Mon Nov 20 16:37:22 2000 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 273F237B479; Mon, 20 Nov 2000 16:37:20 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eAL0adS99764; Mon, 20 Nov 2000 16:36:39 -0800 (PST) (envelope-from dillon) Date: Mon, 20 Nov 2000 16:36:39 -0800 (PST) From: Matt Dillon Message-Id: <200011210036.eAL0adS99764@earth.backplane.com> To: Gerd Knops Cc: John Baldwin , Francisco Reyes , freebsd-stable@FreeBSD.ORG Subject: Re: 4.2 Showstopper? Belkin KVM switch problems with FreeBSD 4.2 References: <20001121002924.13031.qmail@camelot.bitart.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :.. :> using PS/2 keyboard and mouse ports. Perhaps it is something finicky :> with AT keyboards? Regardless, removing the 'flags 0x1' will fix your :> problem. The flag is needed so that people with USB keyboards have :> their keyboards recognized as the primary keyboard by the console :> driver on boot. :> :Thanks, that solved it! Might warrant a note in /usr/src/UPDATING. : :Gerd I've been wondering for a while now why I can't connect a keyboard up to a machine after it has booted... used to work, doesn't any more. Now I know. As much as I applaud the USB keyboard support, I think disabling the normal keyboard by default when it isn't found to be connected is a serious mistake. At the very least the normal keyboard driver should be installed if no other keyboard is found. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message