From owner-freebsd-questions Thu Mar 16 16:48:50 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 7D95237B815 for ; Thu, 16 Mar 2000 16:48:47 -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 TAA33942; Thu, 16 Mar 2000 19:46:05 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <200003170046.TAA33942@spoon.beta.com> To: Alex Charalabidis Cc: brent@kearneys.ca, questions@FreeBSD.ORG, jfn@enteract.com Subject: Re: AMD Athlon and booting In-reply-to: Your message of "Thu, 16 Mar 2000 18:43:33 CST." Date: Thu, 16 Mar 2000 19:46:05 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, I, too, have an SD-11. No crashes yet with a week or so of run time. I'm getting ready to reinstall and run some heavy graphics processing on it. I'll let you know if I hit anything. OTOH, the keyboard missing problem has shown up on several (non-FIC) Athlon motherboards I have access to. -Brian > On Thu, 16 Mar 2000, Brian J. McGovern wrote: > > > 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. M y > > "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 prob ing > > may need some work for Athlon processors, so i'm cc'ing this to the hacker s > > 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. > > > The problem might actually be with the SD-11 board. I built two K7 500s on > SD-11 boards a while ago (3.4-STABLE) and am not at all happy with them. > In fact, I was able to bring only one of them into production and live > with it randomly crashing every now and then... the other one crashed too > frequently and is headed for the RMA department. What I've seen points to > a motherboard problem and not a FreeBSD problem so, if anyone has evidence > to the contrary, I'd like to hear it. > > > -ac > > -- > ============================================================== > Alex Charalabidis (AC8139) 5050 Poplar Ave, Ste 170 > Systems Administrator Memphis, TN 38157 > WebNet Memphis (901) 432 6000 > Author, The Book of IRC http://www.bookofirc.com/ > ============================================================== > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message