Skip site navigation (1)Skip section navigation (2)
From:      Matt Rohrer <rohrer@hawaii.edu>
To:        "Brian J. McGovern" <mcgovern@spoon.beta.com>
Cc:        Alex Charalabidis <alex@wnm.net>, brent@kearneys.ca, questions@FreeBSD.ORG, jfn@enteract.com
Subject:   Re: AMD Athlon and booting 
Message-ID:  <Pine.GSO.4.21.0003161507560.22292-100000@uhunix1>
In-Reply-To: <200003170046.TAA33942@spoon.beta.com>

next in thread | previous in thread | raw e-mail | index | archive | help
I just built an FIC SD-11/Athlon 500 box yesterday and installed 3.3
Release and CVSuped to 3.4 Stable with no problems.

I seem to remember something on the list a few days ago about the same
type of errors when using USB keyboards during install. Is your
keyboard USB?

On Thu, 16 Mar 2000, Brian J. McGovern wrote:

> 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
> 

-Matt




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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.21.0003161507560.22292-100000>