From owner-freebsd-questions Sat Sep 18 17:59:33 1999 Delivered-To: freebsd-questions@freebsd.org Received: from lexicon.ins.com (ns1.ins.com [199.0.193.15]) by hub.freebsd.org (Postfix) with ESMTP id 1B65814FF4 for ; Sat, 18 Sep 1999 17:59:31 -0700 (PDT) (envelope-from jayson_anderson@ins.com) Received: from notorious (iplsin33-060.dsl.gtei.net [4.3.33.60]) by lexicon.ins.com (8.8.8/8.8.8) with SMTP id RAA17493 for ; Sat, 18 Sep 1999 17:59:30 -0700 (PDT) Message-ID: <000501bf023a$5c720c00$0200a8c0@dsl.gtei.net> From: "Jayson Anderson" To: Subject: FreeBSD 3.2 boot kernel / AT Keyboard problem Date: Sat, 18 Sep 1999 20:00:25 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Quick question for those who may possess a quick answer: As I discovered today, the kern.flp image provided with FreeBSD 3.2 does not contain AT style keyboard support. This is confirmed at boot with the 'keyboard:no' message. The 3.2 ERRATA.TXT statement on the FreeBSD website claims this is due to lack of space, and that one should press the space bar to bring up a 'boot:' prompt. It is also said that after this occurs, one can type '-Dh' at the boot prompt and the AT keyboard will work hereafter. Perhaps this is an isolated incident, but in practice today, the space bar and multiple space bar/waiting combinations never yielded my 'boot:' prompt. Does anyone have any input or other knowledge of how to coax the AT keyboard to work ? Multiple known good keyboards were used and the port itself is known good under other unices. The boot disk(s) is known good via booting on other ps2 style machines. The hardware configuration in the machine is known conflict-free via other diagnostics and unices. The CMOS in the machine sees the AT port and is configured to use it. Building a custom boot image seems to be shunned by the FreeBSD website, saying it is a process that is not a viable solution under 3.2 due to completeness of the imagemaking process. Any input would be appreciated, and thanks jayson anderson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message