From owner-freebsd-questions Thu Mar 16 9:38:45 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id BCFAA37C013 for ; Thu, 16 Mar 2000 09:38:42 -0800 (PST) (envelope-from jfn@shell-2.enteract.com) Received: from shell-2.enteract.com (jfn@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.9.3/8.9.3) with ESMTP id LAA68432; Thu, 16 Mar 2000 11:38:37 -0600 (CST) (envelope-from jfn@shell-2.enteract.com) Received: (from jfn@localhost) by shell-2.enteract.com (8.9.3/8.9.3) id LAA79789; Thu, 16 Mar 2000 11:38:36 -0600 (CST) (envelope-from jfn) Date: Thu, 16 Mar 2000 11:38:36 -0600 (CST) From: Jeremy Nelson Message-Id: <200003161738.LAA79789@shell-2.enteract.com> To: freebsd-questions@freebsd.org To: brent@kearneys.ca Subject: Re: AMD Athlon and booting. X-Newsgroups: mpc.lists.freebsd.questions,muc.lists.freebsd.questions In-Reply-To: <20000316081601.B38453@kearneys.ca> References: <20000316091624.A7641@cb670867-b.mdsn1.wi.home.com> Organization: Damage, org. Cc: Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sorry to barge in on the middle of this, but i had this exact same problem, and was able to work out how to fix it. >On Thu, Mar 16, 2000 at 09:16:24AM -0600, Barth Weishoff wrote: >> >> I have an AMD Athlon based system that is locking upon bootup while trying >> to boot from either the distro CD (3.4-R and 4.0-RC3) or the floppy disks. >> >> The system will display this message: >> >> /boot.config: -P >> Keyboard: no >> >> BTX loader 1.00 BTX version is 1.01 >> >> At this point the machine locks. The machine configuration is as follows: >> >> AMD Athlon 650MHz >> FIC SD-II mainboard - http://www.fic.com.tw/motherboards/sd11/sd11intro.htm [rest snipped] I found that the problem had something to do with numlock. I was able to confirm this by testing this about two dozen times. Here is what i found: If is off, your keyboard will *not* be found, and you're stuck. I tried various togglings of , and what i found worked the best is to set your bios to turn on at boot-up, and then turn off and then immediately back on while the bios is checking your memory. I know this sounds crazy, but it worked for me and I tried almost every other possible combination of tricks, and that was the one that caused the boot disk to find the keyboard. I basically have the exact same setup as you except that i have a K7-550. Note that this is only a problem for the boot disk. Once you have freebsd installed, you don't need to go through this again every time you boot. Jeremy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message