Date: Mon, 13 Jun 2005 11:47:50 -0700 From: Peter Wemm <peter@wemm.org> To: freebsd-amd64@freebsd.org Subject: Re: Athlon64 board with ECC support? Message-ID: <200506131147.50300.peter@wemm.org> In-Reply-To: <200506132038.25975.josemi@redesjm.local> References: <200506131616.j5DGGDfr067534@lurza.secnetix.de> <200506132038.25975.josemi@redesjm.local>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 13 June 2005 11:38 am, Jose M Rodriguez wrote: > El Lunes, 13 de Junio de 2005 18:16, Oliver Fromme escribi=F3: > > Hi, > > > > I'm currently evaluating possibilities to upgrade to a > > 64bit system (preferably AMD). I would like to get a > > single-processor Athlon64 system, no Opteron, because of > > heat, noise and power consumption (and price). > > > > Furthermore, I would like to have ECC RAM. However, it > > seems that this requirement is not easy to meet. > > > > So far, Google told me that the Athlon64 and the socket939 > > basically support ECC. However, it also requires support > > in the chipset and in the BIOS. I've looked at a few > > random socket939 board specs, and all of them allow the > > use of ECC memory, _but_ they don't support using it for > > actual error correction, i.e. they treat 72bit DIMMs like > > 64bit DIMMs and ignore the ECC part. This is not what I > > want, of course. > > > > Now my question is: Are there any Athlon64 (s939) boards > > that really support ECC RAM? Any recommendations? > > As far I know, only nvidia nforce4 have support for this. But this > may get you into problems with lan and disk (SATA). The system chipset has nothing to do with ECC support. Unlike on Intel=20 systems, memory is connected to the CPU, not the chipset. The chipset=20 (nforce vs via vs whatever) has no say in the matter. =2D-=20 Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200506131147.50300.peter>