Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Jun 1999 16:55:54 -0700
From:      Shawn Ramsey <shawn@cpl.net>
To:        Rick Hamell <hamellr@dsinw.com>
Cc:        questions@FreeBSD.ORG
Subject:   Re: AMD K6-2/380
Message-ID:  <19990615165554.B4766@cpl.net>
In-Reply-To: <Pine.WNT.3.95.990615162909.-96127D-100000@akane>; from Rick Hamell on Tue, Jun 15, 1999 at 04:29:45PM -0700
References:  <19990615131857.B9780@cpl.net> <Pine.WNT.3.95.990615162909.-96127D-100000@akane>

next in thread | previous in thread | raw e-mail | index | archive | help
> > 2000, it refuses to boot. 98 just reboots, and 2000 locks up at the login
> > prompt. I would expect the reverse to happen, IE WIndows works ok with
> > broken hardware, while FreeBSD doesn't. Anyone have any clues? I tried
> > changing the CPU and RAM, with no changes... I guess it could be a bad
> > motherboard, or at least damaged motherboard?
> 
> 	Have you downloaded the AMD patches for Windows? 

For 98? I thought 98 was already patched, or did have the same bug that
Win95 had with these processors? I've got another '98 system running the
same CPU just fine, and it was never patched. I tried putting another HD in
this system that has Windows 2000, but I wasn't sure if that was just
something with 2000 not liking having its MB changed or a problem with the
system.... but i've never seen a problem like this before, usually windows
will at least BOOT on problematic hardware, and FreeBSD has no problem
building world. (Did it three times, no problems)



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?19990615165554.B4766>