From owner-freebsd-questions Tue Jun 15 16:55:35 1999 Delivered-To: freebsd-questions@freebsd.org Received: from luke.cpl.net (luke.cpl.net [209.150.92.68]) by hub.freebsd.org (Postfix) with ESMTP id DDE3014BF6 for ; Tue, 15 Jun 1999 16:55:26 -0700 (PDT) (envelope-from shawn@luke.cpl.net) Received: (from shawn@localhost) by luke.cpl.net (8.9.3/8.9.3) id QAA20801; Tue, 15 Jun 1999 16:55:55 -0700 (PDT) Message-ID: <19990615165554.B4766@cpl.net> Date: Tue, 15 Jun 1999 16:55:54 -0700 From: Shawn Ramsey To: Rick Hamell Cc: questions@FreeBSD.ORG Subject: Re: AMD K6-2/380 References: <19990615131857.B9780@cpl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: ; from Rick Hamell on Tue, Jun 15, 1999 at 04:29:45PM -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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