From owner-freebsd-stable Fri Aug 31 4:56: 3 2001 Delivered-To: freebsd-stable@freebsd.org Received: from femail6.sdc1.sfba.home.com (femail6.sdc1.sfba.home.com [24.0.95.86]) by hub.freebsd.org (Postfix) with ESMTP id 1AFF737B403 for ; Fri, 31 Aug 2001 04:55:57 -0700 (PDT) Received: from home.com ([24.2.168.159]) by femail6.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010831115556.TJUN26423.femail6.sdc1.sfba.home.com@home.com> for ; Fri, 31 Aug 2001 04:55:56 -0700 Message-ID: <3B8F79C0.D4781D1B@home.com> Date: Fri, 31 Aug 2001 07:49:20 -0400 From: Ted Sikora X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.5 i686) X-Accept-Language: en-US, en MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: Re: FreeBSD and Athlon Processors References: <5.1.0.14.0.20010831044409.00c26c38@rfnj.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Allen Landsidel wrote: > > At 01:22 8/31/2001 -0700, Darryl Okahata wrote: > > > Do a google groups search on "via chipset ide corruption". You > >might be surprised at what you find. Just because you don't have > >problems, doesn't mean that the problem doesn't exist. > > Ok I'll give you that much. > > But the flip side of that coin is that just because some people are having > problems doesn't mean that it's defective hardware, or even if it is > hardware, it doesn't by definition mean it's the chipset. > > I remember when the Athlons first came out, and before I ordered my MSI, I > did a usenet search on "athlon problems" or something to that extent. I > picked the board that seemed to only appear in response to peoples > problems, with the owner saying "well I have an MSI-6167 and I'm not having > any of those problems." Soon after the athlons came out people were > complaining all over the place about stability issues, hangs, crashes, and > all kinds of problems. As it turns out, the great majority of these > problems were -other- cheap hardware used in building the machines and > other forms of user error such as : > > 1. Overclocking without adequate knowledge of how to do so effectively > (I won't say overclocking in general because a great many people, including > myself, overclock without any problems.) > > 2. An in adequate power supply. AMD is very specific about how much > power the Athlon needs to operate, and so is nVidia about their AGP > graphics cards. Ignore these -requirements- at your peril. > > 3. Incompatible or defective memory. The original athlons required > unbuffered PC100 memory. People using PC66 memory or buffered dimms had > problems, and they deserved them. > There's always going to be incompatabilities between boards what works on one won't on another even with supposedly identical components. I use nothing but AMD Slot-A/Socket-A/K6 with VIA and ALi chipsets on FreeBSD. After disabling APM in the kernel when the microtime error first appeared I have had zero problems. In fact I can't ever remember having such stable machines like I enjoy now. -- Ted Sikora tsikora@ntplx.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message