From owner-freebsd-questions Tue Jun 15 13:18:24 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 945E315663 for ; Tue, 15 Jun 1999 13:18:15 -0700 (PDT) (envelope-from shawn@luke.cpl.net) Received: (from shawn@localhost) by luke.cpl.net (8.9.3/8.9.3) id NAA14279 for questions@freebsd.org; Tue, 15 Jun 1999 13:18:57 -0700 (PDT) Message-ID: <19990615131857.B9780@cpl.net> Date: Tue, 15 Jun 1999 13:18:57 -0700 From: Shawn Ramsey To: questions@freebsd.org Subject: AMD K6-2/380 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, this is completly off-topic, but.... I have a AMD k6-2/380 that seemingly works perfectly in FreeBSD. It is even able to build a kernel and make a 3-stable fine. (I did not time it though). But in Windows, 98 or 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? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message