From owner-freebsd-hackers Sun Dec 2 16:11:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.altadena.net (ns.altadena.net [206.126.144.2]) by hub.freebsd.org (Postfix) with ESMTP id 1CAF437B419; Sun, 2 Dec 2001 16:11:40 -0800 (PST) Received: (from pete@localhost) by ns.altadena.net (8.11.6/8.8.8) id fB30BbQ29980; Sun, 2 Dec 2001 16:11:37 -0800 (PST) (envelope-from pete) From: Pete Carah Message-Id: <200112030011.fB30BbQ29980@ns.altadena.net> Subject: Re: Via 686b data corruption. In-Reply-To: from Mike Wade at "Dec 2, 2001 06:28:03 pm" To: Mike Wade Date: Sun, 2 Dec 2001 16:11:37 -0800 (PST) Cc: sos@freebsd.org, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=iso8859-1 Content-Transfer-Encoding: 7bit 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 > On Sun, 2 Dec 2001, Pete Carah wrote: > > > I'm seeing data corruption on the Promise channel of a A7V133, > > WITH the "southbridge fix" applied and NO sound card of any kind in > > the system (the built-in is disabled in the bios; current wouldn't boot > > at all with it enabled, when I bought the mb). All the cards are > > video (a TNT2 card of some kind) and network (Intel). > Hello! I've been working on the same problem myself... > > Do you observe data corruption when selecting the "safe" BIOS defaults > rather than the "optimized" defaults? No; didn't think of that. > Also how are you testing for data > corruption? md5 on the CD images ftp'd from freebsd.org. Doesn't seem to happen on short transfers (for some definition of "short" - the 4.4-mini.iso comes in right about half the time). Haven't tested one of the iso files onto the "main" IDE instead of the promise since I'm short of disk space there. The corruption appears to only be writing the disks; the md5 values are very consistent once written. -- Pete To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message