Date: Wed, 29 Mar 2000 10:02:03 +0100 From: Steve Roome <steve@sse0691.bri.hp.com> To: "Brandon D. Valentine" <bandix@looksharp.net> Cc: freebsd-stable@freebsd.org Subject: Re: New kernel with its ATA drivers damages the filesystem Message-ID: <20000329100203.A94487@moose.bri.hp.com> In-Reply-To: <Pine.BSF.4.21.0003282253220.63207-100000@turtle.looksharp.net>; from bandix@looksharp.net on Tue, Mar 28, 2000 at 10:56:57PM -0500 References: <20000328223420.C10913@got.wedgie.org> <Pine.BSF.4.21.0003282253220.63207-100000@turtle.looksharp.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 28, 2000 at 10:56:57PM -0500, Brandon D. Valentine wrote: > On Tue, 28 Mar 2000, Jason Garman wrote: > > >Whats your motherboard? I just trashed an ASUS P2V (which also has a VIA > >chipset on it) -- same problems, under all OSes that used DMA on the > >drive. Unfortunate, really. Got a new Abit BE6 instead, works like a > >dream. Highly recommended. > > Yeah, this is the same reason I'm hesitant to jump into the Athlon > world. The companies that have been backing AMD's chips are just > horrible at chipsets. I'd still much prefer a good, solid Intel > chipset, and for IDE/UDMA definitely a PIIX- series controller. Too > bad, because otherwise the Athlon is a nice platform. I've had VIA chipsets since as long as I can remember (started with freebsd on 2.1) and they've been fine, [not withstanding pilot error, overclocking too far and putting just plain wrong or silly settings in the BIOS.] IMHO, on an comparison (using same release times) the VIA chipsets have performed admirably (often far better, but never far worse) than the Intel offering. Even the SiS chipsets I started with were prefectly reliable, and also at least as good performers as their rivals. My Athlon500 + FIC SD11 is fine, the only problem being I needed a BIOS upgrade for my 34Gb IDE disk because I bought the board as soon as it hit the market =( It runs make worlds (3.4-stable) in about 40 mins, and I can thrash any part of the hardware just as hard as on any other machine without causing an FIC-only problem. All I want now is a -march=athlon gcc/egcs flag in 3.4-stable. Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000329100203.A94487>