public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Farrell <dan@spore.ath.cx>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: memtest fails, but is it the RAM?
Date: Wed, 11 Jul 2007 09:36:12 -0500	[thread overview]
Message-ID: <20070711093612.23227300@pascal.spore.ath.cx> (raw)
In-Reply-To: <1184110152.6875.91.camel@orpheus>

On Wed, 11 Jul 2007 08:59:12 +0930
Iain Buchanan <iaindb@netspace.net.au> wrote:

> 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!

Ever hear of a POST code?  if not, look up the post codes for your
bios / motherboard and you may be able to get a head start on diagnosis
there.  

>> Often power supplies will run ok can then glitch causing a
>> reboot. It cannot hurt to swap the power supply to see if that 
>> fixes the random reboots....  

This happens sometimes with cheap power supplies, it's true.  One
temporary and inconsistant solution is to remove all unnecessary power
suckers, like hds, case fans (which evidently do nothing for you
anyway) and cdrom.  That might get it working, but not for long no
doubt.  

>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.

Wow, that is wierd.  Have you tried looking for BIOS updates?
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-07-11 14:41 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 [this message]
2007-07-11 16:15     ` Mick

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=20070711093612.23227300@pascal.spore.ath.cx \
    --to=dan@spore.ath.cx \
    --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