From owner-freebsd-hackers Wed Feb 20 12:58:40 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from snipe.prod.itd.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by hub.freebsd.org (Postfix) with ESMTP id 6189A37B405 for ; Wed, 20 Feb 2002 12:58:37 -0800 (PST) Received: from pool0067.cvx40-bradley.dialup.earthlink.net ([216.244.42.67] helo=mindspring.com) by snipe.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16ddoi-0002lb-00; Wed, 20 Feb 2002 12:58:21 -0800 Message-ID: <3C740DE2.B028B5A5@mindspring.com> Date: Wed, 20 Feb 2002 12:58:10 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Gallatin Cc: sos@freebsd.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: Serverworks ATA controller & data corruption References: <15475.50753.252494.269972@grasshopper.cs.duke.edu> <200202201953.g1KJrKq77437@freebsd.dk> <15476.1618.379112.915616@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable 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 Andrew Gallatin wrote: > S=F8ren Schmidt writes: > > However the Serverworks > > ROSB4 chips is not one I would recommend using, if you need serious > > ATA support on such a board, install a Promise TX2 or later or a > > HPT370 or later ... > = > I don't much care about serious ATA support on these machines -- Apparently, neither does the chip vendor. 8-p. > nearly all work is done on NFS volumes exported from an alpha. If I > can just trust PIO not to corrupt the system disk, then it will be > fine for me. > = > So.. Is PIO safe? Is there any sort of CRC being done on PIO data? He just said: if your chipset is programmed correctly by the BIOS, then there will not be a problem, but apparently, there is a very narrow band of "correctly" (perhaps even only a single state), and the vendor apparently does not default the chip into that state. FWIW, Julian had to fix a similar problem by programming the heck out of a Cyrix MediaGX chipset via a custom BIOS. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message