public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Nelson, David \(ED, PAR&D\)" <David.Nelson2@astrazeneca.com>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] Dodgy hardware?!?!
Date: Thu, 1 Feb 2007 13:24:31 -0000	[thread overview]
Message-ID: <3D60AF2712C16D42A38076E52FD6E3D23F0D72@ukmcrdembx01.rd.astrazeneca.net> (raw)
In-Reply-To: <20070201140459.ea05cf86.hilse@web.de>


> -----Original Message-----
> From: Hans-Werner Hilse [mailto:hilse@web.de]
> Sent: 01 February 2007 13:05
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] Dodgy hardware?!?!
> 
> 
> Hi,
> 
> On Wed, 31 Jan 2007 06:34:01 -0600 Dan Farrell 
> <dan@spore.ath.cx> wrote:
> 
> > On Wed, 31 Jan 2007 23:27:10 +1100
> > Dave Oxley <dave@daveoxley.co.uk> 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


I would also note that leaving it for a few hours is generally recommended. I have used memtest86 to identify a few bad sticks of ram and all have shown errors within the first few tests, but it cant hurt to run it a little longer.

In addition - if you have multiple DIMMs and find one is bad, run memtest again after removing the faulty DIMM to make sure the others are fine.

As for the graphics card in the system in question - check that the cooling fan is working correctly. I had some awful artifacting in Linux on a card a year or so ago when the GPU fan snuffed it and the GPU was overheating (the heatsink was hot to the touch such that you couldn't hold a finger on it for long!).

--
djn

Disclaimer: I represent no-one else in my emails to this list. Use any advice given at your own risk.

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-02-01 13:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-31 12:27 [gentoo-user] Dodgy hardware?!?! Dave Oxley
2007-01-31 12:34 ` Dan Farrell
2007-02-01 13:04   ` Hans-Werner Hilse
2007-02-01 13:24     ` Nelson, David (ED, PAR&D) [this message]
2007-01-31 13:00 ` Alan McKinnon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D60AF2712C16D42A38076E52FD6E3D23F0D72@ukmcrdembx01.rd.astrazeneca.net \
    --to=david.nelson2@astrazeneca.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox