From owner-freebsd-questions  Sun Apr  2 17:13:34 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from napalm.plano.sterling.com (napalm.plano.sterling.com [138.42.1.34])
	by hub.freebsd.org (Postfix) with ESMTP id 19E0337B59F
	for <questions@freebsd.org>; Sun,  2 Apr 2000 17:13:31 -0700 (PDT)
	(envelope-from alan.edmonds@sterling.com)
Received: from sterling.com (ras-0019.plano.sterling.com [10.1.48.128])
	by napalm.plano.sterling.com (8.9.1b+Sun/8.9.1) with ESMTP id TAA15434;
	Sun, 2 Apr 2000 19:13:07 -0500 (CDT)
Message-ID: <38E7E1FE.873A0E86@sterling.com>
Date: Sun, 02 Apr 2000 19:12:46 -0500
From: Alan Edmonds <alan.edmonds@sterling.com>
X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.0-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Nicolas Blais <nicblais@hotmail.com>
Cc: questions@freebsd.org
Subject: Re: Keyboard at boot prob.
References: <20000403000624.67599.qmail@hotmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

There's some kind of timing issue with the keyboard probe as I recall.
I don't remember the exact situation.  I'm glad you fixed it.

I don't know anything about current.freebsd.org.  I've never heard 
of it.....


Nicolas Blais wrote:
> 
> >Check the archives for this list.  I think someone had the same problem.
> >
> >I think they fixed it by holding down numlock during the boot (or
> >something like that)......
> >
> >Alan
> 
> Thanks, it worked!  Well, what I actually did was setting off the "Numlock
> enabled at startup" option in my BIOS.
> 
> BTW, is current.freebsd.org down?
> Bye.
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message