From owner-freebsd-questions  Wed Mar  1 13:36:15 1995
Return-Path: questions-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id NAA00251 for questions-outgoing; Wed, 1 Mar 1995 13:36:15 -0800
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id NAA00241; Wed, 1 Mar 1995 13:36:08 -0800
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id IAA11147; Thu, 2 Mar 1995 08:23:06 +1100
Date: Thu, 2 Mar 1995 08:23:06 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199503012123.IAA11147@godzilla.zeta.org.au>
To: jeffh@cybernetics.net, michael@cybernetics.net
Subject: Re: 021095-SNAP
Cc: bugs@FreeBSD.org, questions@FreeBSD.org, sos@freefall.cdrom.com,
        wpaul@freefall.cdrom.com
Sender: questions-owner@FreeBSD.org
Precedence: bulk

>> I've not been able to boot the latest snapshot version on at least 3 
>> machines at my disposal.  They are all of varying configurations and 

>I had this same thing happen to me.  What always get me by it (this may 
>be totally different from what's happening with you) is to repeatedly tap 
>the num lock key while it's booting.

Recent bootstraps probe the keyboard.  It would appear that the probe is
simpler than possible.  It only does about half of what the keyboard probe
in syscons does.  In particular, it doesn't read the second byte returned
in response to the reset command.  It doesn't test that the data it reads
is ready, but the much longer delay than in syscons probably allows things
to work.  The syscons probe seems to be missing a test for the data to be
ready in one place.

Bruce