public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: memtest fails, but is it the RAM?
Date: Wed, 11 Jul 2007 17:15:40 +0100	[thread overview]
Message-ID: <200707111715.42709.michaelkintzios@gmail.com> (raw)
In-Reply-To: <1184110152.6875.91.camel@orpheus>

[-- Attachment #1: Type: text/plain, Size: 2496 bytes --]

On Wednesday 11 July 2007 00:29, Iain Buchanan wrote:
> On Fri, 2007-07-06 at 00:40 +0000, James wrote:
> > Not sure this is useful, but, if you can get the system to boot, you
> > and look more closely at the memory specifics with the 'lshw' command.
>
> hey, neat command.  The system boots knoppix and windows fine, but I
> don't have gentoo on it (yet :) and I don't have lshw on any live cd I
> have...  It can take PC2100, PC2700 or PC3200 though.  I currently have
> 2x 512Mb PC3200 in it.

Use apt-get install to install the lshw package on Knoppix.  It has a small 
footprint and it should hopefully not exhaust your RAM.

> > If you can, swap the memory with another know good system for a few
> > days.... Something might show up as a problem
>
> I did that.  The new RAM (another PC3200) works ok, but memtest still
> fails at the same point (test 3).  This is confusing me.  the same
> live-cd runs memtest on my other machine (DDR2) without fail...
>
> The other funny thing about memtest is this:  The info it displays about
> the system is a bit strange.  Sometimes it shows a CPU clock of 2999MHz,
> sometimes 3000MHz; sometimes the RAM shows DDR398, sometimes DDR400.
> It's always the same for one particular run of memtest, but sometimes
> changes between boots.

Hmm, is there a BIOS firmware upgrade you could perhaps flash it with?

Can you swap around the RAM modules or remove them one at a time until you 
find the culprit?  (not sure if you tried that already).

> > > (Ultimately, I'm trying to diagnose a random reboot problem, which
> > > makes me suspicious of the memory, but I'm not sure)
> >
> > I always look at the temperature as the mobo makes it available,
> > or checking the temperature of the hard drive with 'hddtemp /dev/<drive>'
>
> I plotted some GPU and CPU temperatures while running some games, and
> they all go to a reasonable maximum and stop there.  I even turned the
> case fans off, and they don't go higher.
>
> The "random reboot" problem is now a "won't boot" problem!  I put the
> original RAM back in the same slots, and now the HD's, CD's, and fans
> spin up, but no display appears.  I hear a bios beep, and that's it.
> Maybe it's a MBoard issue?  Maybe a video card issue?  Hmmm, I don't
> want to replace the whole lot!

POST error.  Could be due to dodgy memory.  Have you tried removing the CMOS 
battery and then reflashing the BIOS with the latest firmware?
-- 
Regards,
Mick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2007-07-11 16:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06  0:25 [gentoo-user] memtest fails, but is it the RAM? Iain Buchanan
2007-07-06  0:40 ` [gentoo-user] " James
2007-07-10 23:29   ` Iain Buchanan
2007-07-11 14:36     ` Dan Farrell
2007-07-11 16:15     ` Mick [this message]

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=200707111715.42709.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.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