From owner-freebsd-questions  Thu Mar 16 16:14:28 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.147.249.166])
	by hub.freebsd.org (Postfix) with ESMTP
	id 7F4B337BD24; Thu, 16 Mar 2000 16:14:23 -0800 (PST)
	(envelope-from mcgovern@spoon.beta.com)
Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1])
	by spoon.beta.com (8.9.3/8.9.3) with ESMTP id TAA33374;
	Thu, 16 Mar 2000 19:11:38 -0500 (EST)
	(envelope-from mcgovern@spoon.beta.com)
Message-Id: <200003170011.TAA33374@spoon.beta.com>
To: brent@kearneys.ca
Cc: questions@freebsd.org, hackers@freebsd.org, jfn@enteract.com
Subject: RE: AMD Athlon and booting
Date: Thu, 16 Mar 2000 19:11:38 -0500
From: "Brian J. McGovern" <mcgovern@spoon.beta.com>
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hey, guys. I went a slightly different route than playing with the numlock key
to get FreeBSD running. The problem seems to really be the -P (probe the 
keyboard) boot option, and it setting -D and -h when it doesn't find it. My
"workaround" was to make boot floppies, and edit boot.conf to remove the -P
(or delete the file if there are no other options). 

Once done, it just happily boots up and installs. Looks like keyboard probing
may need some work for Athlon processors, so i'm cc'ing this to the hackers
list, so hopefully, some console guru can take a look at it. 

Also, if no one has done it so far, let me know, and I'll submit a pr.

	-Brian


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