From owner-freebsd-questions Mon Jun 4 1:25:39 2001 Delivered-To: freebsd-questions@freebsd.org Received: from bumper.jellybaby.net (bumper.jellybaby.net [194.159.247.1]) by hub.freebsd.org (Postfix) with ESMTP id A70F937B401 for ; Mon, 4 Jun 2001 01:25:36 -0700 (PDT) (envelope-from simond@bumper.jellybaby.net) Received: (from simond@localhost) by bumper.jellybaby.net (8.9.2/8.9.2) id JAA83094; Mon, 4 Jun 2001 09:28:06 +0100 (BST) (envelope-from simond) Date: Mon, 4 Jun 2001 09:28:05 +0100 From: simond@irrelevant.org To: auto245751@hushmail.com Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 4.2 Installation - Keyboard Problem Message-ID: <20010604092805.A82783@irrelevant.org> References: <200106040637.XAA19665@user8.hushmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200106040637.XAA19665@user8.hushmail.com>; from auto245751@hushmail.com on Mon, Jun 04, 2001 at 06:25:57AM +0000 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jun 04, 2001 at 06:25:57AM +0000, auto245751@hushmail.com wrote: > I'm booting from the official FreeBSD 4.2-RELEASE CD. The kernel loads fine, > > but when it gets to the part where you have those three choices (text, visual, > > etc.) for kernel configuration, I notice my keyboard becomes unresponsive. > The arrow keys won't work, the enter key won't work, nothing. I have to > reboot the system. This is puzzling because the enter key works fine when > it says something like "hit enter to continue". Also, Windows 98, Windows > 2000, > and Redhat Linux 6.2 have no problem at all with my keyboard. I have the > same problem with FreeBSD when I try to do the installation from my old > 3.3-RELEASE CD. I am pretty sure the keyboard is detected, because I > _DON'T_ get that "keyboard: no" message. > > The computer is an Acer Veriton 5100. The hardware is in excellent condition. > > Help!!!!! OK, I have this problem myself, if you read the kernel boot output you'll see that it probably fails to attach the atkbd driver with error code 6, if you can get to the visual device config screen then you can simply set flags to 0 for atkbd0 -- Simon Dick simond@irrelevant.org "Why do I get this urge to go bowling everytime I see Tux?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message