From owner-freebsd-hardware  Tue Sep 16 01:18:12 1997
Return-Path: <owner-freebsd-hardware>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id BAA08210
          for hardware-outgoing; Tue, 16 Sep 1997 01:18:12 -0700 (PDT)
Received: from bedroom.saturn-tech.com ([207.229.19.33])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA08193
          for <hardware@FreeBSD.ORG>; Tue, 16 Sep 1997 01:18:08 -0700 (PDT)
Received: from localhost (drussell@localhost)
          by bedroom.saturn-tech.com (8.8.4/8.8.4) with SMTP
	  id CAA22068; Mon, 16 Sep 1996 02:19:12 -0600 (MDT)
X-Authentication-Warning: bedroom.saturn-tech.com: drussell owned process doing -bs
Date: Mon, 16 Sep 1996 02:19:12 -0600 (MDT)
From: Doug Russell <drussell@saturn-tech.com>
To: Michael Beckmann <beckmann@nacamar.net>
cc: William Maddox <maddox@p-1.Eng.Sun.COM>, hardware@FreeBSD.ORG
Subject: Re: Parity trouble with Asus mainboard
In-Reply-To: <3.0.3.32.19970916100515.01432790@mail.nacamar.de>
Message-ID: <Pine.BSF.3.95.960916021818.22066A-100000@bedroom.saturn-tech.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hardware@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


On Tue, 16 Sep 1997, Michael Beckmann wrote:

> >It is quite possible that the Gigabyte automatically disables ECC if you
> >don't actually have parity memory installed as an "idiot-proof" type
> >feature.  I honestly don't know for sure, though.
> 
> My Gigabyte 586 HX has three settings for parity: enabled, disabled and
> auto. I set it to enabled when I tried the parity SIMMs. Later I installed
> the normal SIMMs again and immediately got a parity error, so the parity
> check seems to work.

Hmmm...   That shoots THAT theory, then...  :)

Later......						<Doug>