From owner-freebsd-current Tue Nov 26 20:43:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA25556 for current-outgoing; Tue, 26 Nov 1996 20:43:13 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA25549 for ; Tue, 26 Nov 1996 20:43:05 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id VAA07840; Tue, 26 Nov 1996 21:42:52 -0700 (MST) Date: Tue, 26 Nov 1996 21:42:52 -0700 (MST) Message-Id: <199611270442.VAA07840@rocky.mt.sri.com> From: Nate Williams To: Benjamin Lewis Cc: current@freebsd.org Subject: Re: Weird keyboard problem with COMPAT_LINUX In-Reply-To: <199611270151.UAA00471@ylana.vet.purdue.edu> References: <199611270151.UAA00471@ylana.vet.purdue.edu> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The machine probed and booted fine. The keyboard works fine when editing > the config using the -v option. However, when the login: prompt appears, > the keyboard seems totally wacked out: what I type isn't what ends up on > screen, CapsLock & NumLock don't have any effect on the LEDs, after a > while it seems to end up in "ControlLock", and other weird effects. If you don't use UserConfig it should work fine. This is a 'known' bug in both -current and 2.2 that is partially my fault, but I'm not longer able to effectively contribute to finding a fix. :( Soren was going to look into fixing at least for 2.2, so if we wait a while longer something will happen. Nate