public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan Grimes <ALONZOTG@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Epic list of total FAIL.
Date: Sat, 22 Aug 2015 01:52:00 -0400	[thread overview]
Message-ID: <55D80E00.4050508@verizon.net> (raw)
In-Reply-To: <2935590.ZJjmRnyj51@andromeda>

J. Roeleveld wrote:
> Please don't bother this list with more of your complaining until you grow up 
> and learn how to use computers properly.

I built my first machine nearly a quarter century ago. =|

That said, I spent the day doing diagnostics:


Findings:

1. There were a hell of a lot more memory errors than I had seen before.
2. There was a smudge on one of the dimm's contacts and some of the
usual dust on the CPU-facing one.
3. The motherboard was not developed by sane engineers. In a sane world,
there are two types of variables: measured variables and controlled
variables.
The RAM voltage would appear to be a controlled variable but it is also
a measured variable. In order to achieve a close approximation of 1.5v,
I had to set it to 1.530 volts. WTF...

4. an AMD K10 processor cannot successfully drive 8-ranks of high
density ram at 2x800 mhz -- BUT IT WILL TRY!!! I found all dimms to be
good either individually or in pairs, but the entire ram compliment of
four dims cannot be run at full speed at once with the CPU/motherboard I
have installed.

5. I found a set of settings that went through memtest fine but caused
linux to segfault and die. I backed off the FSB a few notches while
adjusting the multipliers to stay within the specified frequency for the
processor and it seems to be OK now.



-- 
IQ is a measure of how stupid you feel.

Powers are not rights.



  reply	other threads:[~2015-08-22  5:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-20 20:26 [gentoo-user] Epic list of total FAIL Alan Grimes
2015-08-20 20:37 ` Alan McKinnon
2015-08-20 21:09   ` [gentoo-user] " Grant Edwards
2015-08-20 21:18   ` [gentoo-user] " Emanuele Rusconi
2015-08-20 21:11 ` Terry Z.
2015-08-20 21:29 ` Fernando Rodriguez
2015-08-20 22:31   ` Alan Grimes
2015-08-21  1:20     ` wraeth
2015-08-21  1:49       ` Alan Grimes
2015-08-21  2:41         ` wraeth
2015-08-21  6:09           ` Alan McKinnon
2015-08-21 14:35             ` [gentoo-user] " Grant Edwards
2015-08-21 15:00               ` Alan Grimes
2015-08-21 16:28                 ` Grant Edwards
2015-08-21 17:07                 ` J. Roeleveld
2015-08-22  5:52                   ` Alan Grimes [this message]
2015-08-22  7:04                     ` Fernando Rodriguez
2015-08-22  8:18                       ` Dale
2015-08-22 11:25                         ` Mick
2015-08-22 11:47                           ` Alan McKinnon
2015-08-22 13:43                             ` Mick
2015-08-22 16:40                         ` Alan Grimes
2015-08-22 17:02                           ` Alan McKinnon
2015-08-22 23:28                           ` Dale
2015-08-25 20:43                             ` Frank Steinmetzger
2015-08-25 22:39                               ` Dale
2015-08-21 23:39                 ` Dale
2015-08-22  0:35                 ` Fernando Rodriguez
2015-08-21  1:45     ` [gentoo-user] " Fernando Rodriguez
2015-08-21 14:07     ` [gentoo-user] " James

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=55D80E00.4050508@verizon.net \
    --to=alonzotg@verizon.net \
    --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