From owner-freebsd-hackers Tue Jun 18 13:18: 5 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from darius.2y.net (korpen-86-208.ip-pluggen.com [212.181.86.208]) by hub.freebsd.org (Postfix) with ESMTP id 4642637B40D; Tue, 18 Jun 2002 13:17:58 -0700 (PDT) Received: by darius.2y.net (Postfix, from userid 1001) id 338511C1A; Tue, 18 Jun 2002 22:17:57 +0200 (CEST) Date: Tue, 18 Jun 2002 22:17:57 +0200 From: Morsal Rodbay To: Jordan K Hubbard Cc: C J Michaels , Greg Lehey , FreeBSD Questions , FreeBSD Hackers Subject: Re: Does FreeBSD have a problem with some AMD processors? Message-ID: <20020618221756.C62776@darius.2y.net> Reply-To: Morsal Rodbay References: <20020531023132.A36723@darius.2y.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from jkh@queasyweasel.com on Thu, May 30, 2002 at 05:53:07PM -0700 X-Operating-System: FreeBSD 4.5 [up 3:27] X-Return-Path: morsal@swipnet.se Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Someone mentioned this MTRR problem earlier, I even tried a patch but it was unsuccessful. I think I'll make a new try with FreeBSD 4.6, maybe things will be more successful then. On Thu, May 30, 2002 at 05:53:07PM -0700, Jordan K Hubbard wrote: > I'll bet you wouldn't have any trouble running -stable on it. There was a > problem with MTRR support which still needs a little fixing in order to > shut down properly but that's nowhere near as bad as X not running. Fix > should be in FreeBSD 4.6 as well. > > - Jordan > > > On Thursday, May 30, 2002, at 17:31 US/Pacific, Morsal Rodbay wrote: > > > I recenetly bought an Athlon XP 1800+... and it turned out that it wouldnt > > run XFree. Everything worked well besides X. Since a workstation without X > > is useless I was forced to switch to WinXP and it's very stable so there is > > nothing wrong with the hardware which means it's a FreeBSD issue. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message