From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1HCbhU-0006XY-TV for garchives@archives.gentoo.org; Thu, 01 Feb 2007 13:10:05 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id l11D8wu0016608; Thu, 1 Feb 2007 13:08:58 GMT Received: from gabriel.sub.uni-goettingen.de (gabriel.sub.uni-goettingen.de [134.76.163.126]) by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id l11D50aZ011998 for ; Thu, 1 Feb 2007 13:05:00 GMT Received: by gabriel.sub.uni-goettingen.de (Postfix, from userid 8) id 2267A75F29; Thu, 1 Feb 2007 14:05:00 +0100 (CET) Received: from localhost (unknown [134.76.161.221]) by gabriel.sub.uni-goettingen.de (Postfix) with ESMTP id 3AB7C75F0F for ; Thu, 1 Feb 2007 14:04:59 +0100 (CET) Date: Thu, 1 Feb 2007 14:04:59 +0100 From: Hans-Werner Hilse To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Dodgy hardware?!?! Message-Id: <20070201140459.ea05cf86.hilse@web.de> In-Reply-To: <20070131063401.64af569e@pascal.spore.ath.cx> References: <45C08B1E.6000300@daveoxley.co.uk> <20070131063401.64af569e@pascal.spore.ath.cx> X-Mailer: Sylpheed 2.3.1 (GTK+ 2.10.9; i586-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Details: No, hits=0.4 required=5.0 tests=AWL,MANY_EXCLAMATIONS, PLING_QUERY autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on gabriel.sub.uni-goettingen.de X-Archives-Salt: 28432a7d-b529-4824-aeba-754e9b680b13 X-Archives-Hash: e857b0d1c6fdddb9254cd8eecf86b403 Hi, On Wed, 31 Jan 2007 06:34:01 -0600 Dan Farrell wrote: > On Wed, 31 Jan 2007 23:27:10 +1100 > Dave Oxley wrote: > > > Is there a way of testing the RAM? > > a great way, yes, and it's provided on the gentoo boot cds, even the > minimal. at the isolinux (boot:) prompt, just type memtest-86 and > patiently await the completion of just one test. But always remember that, given the hypothesis that the RAM is working OK, all memtest can do is to _negate_ this hypothesis. It can never verify that hypothesis. So it's always worth to start memtest -- after all, it might fail and you know for sure that RAM is bad (or memory timing or whatever, but it's faulty hardware then). But if it doesn't fail that doesn't mean that RAM is alright! -hwh -- gentoo-user@gentoo.org mailing list