From owner-freebsd-stable Thu Jan 17 9: 5:21 2002 Delivered-To: freebsd-stable@freebsd.org Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by hub.freebsd.org (Postfix) with ESMTP id 022AB37B41A for ; Thu, 17 Jan 2002 09:05:15 -0800 (PST) Received: (from wayne@localhost) by manor.msen.com (8.9.3/8.9.3) id MAA68551 for freebsd-stable@FreeBSD.ORG; Thu, 17 Jan 2002 12:05:11 -0500 (EST) (envelope-from wayne) Date: Thu, 17 Jan 2002 12:05:11 -0500 From: "Michael R. Wayne" To: freebsd-stable@FreeBSD.ORG Subject: Re: Force keyboard detection flag? Message-ID: <20020117120511.W73347@staff.msen.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from doconnor@gsoft.com.au on Tue, Jan 15, 2002 at 06:21:30PM +1030 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I started to look through the kernel code for keyboard detection with plans toward having a sysctl that forces the keyboard at run time, rather than kernel compile. But I got sidetracked. Related problems come up so often that I am convinced that such a fix is required. Me finding time to implement is a problem. /\/\ \/\/ On Tue, Jan 15, 2002 at 06:21:30PM +1030, Daniel O'Connor wrote: > I was wondering if there is a flag to force the kernel to detect a PS/2 > keyboard even if it doesn't detect one. > > The usual answer is 'set atkbdc flags to 0x0' but you can't do that if you are > installing for the first time - when you boot -c the config prompt is printed > in an infinite loop :( > > The newer keyboards I have (Mitsubishi Diamond Touch) do not get detected by > FreeBSD so every time I need to install from a base CD I have to dig up my > detectable keyboard and hot swap it after the detection phase. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message