mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: root@mauve.demon.co.uk
To: rwhite@casabyte.com (Robert White)
Cc: linux-kernel@vger.kernel.org
Subject: Re: my dual channel DDR 400 RAM won't work on any linux distro
Date: Wed, 16 Apr 2003 23:05:12 +0100 (BST)	[thread overview]
Message-ID: <200304162205.XAA15178@mauve.demon.co.uk> (raw)
In-Reply-To: <PEEPIDHAKMCGHDBJLHKGCEMNCHAA.rwhite@casabyte.com> from "Robert White" at Apr 16, 2003 01:53:34 PM

> 
> I had one-hell of a problem myself relating to memory on my new cutting edge
> motherboard.  The problem, it turned out, had everything to do with the
> motherboard and the often marginal quality of the ram.  Much investigation
> revealed that there were only a few manufacturers of ram that the MoBoard
> would "support"
> 
> In lay speak, I could put any damn thing I wanted into the first slot, but
> anything I did with the second and subsequent slots went all haywire.
> 
> The BS layman's speak they gave me at the store was that they had seen a lot
> of cases where having "double sided SIMMs" (they were oh-so-usefully
> classifying the memory based on whether there were chips on just one side,
> or on both sides of the circuit card 8-) in the second and subsequent slots
> never worked.

This has a little basis in fact.

"Double sided SIMMs" can have higher capacitances on the data lines, as there
are more pins connected to the socket.
This means more loading, especially at high speed.

Add in marginal designs, and it can make a difference.


  parent reply	other threads:[~2003-04-16 21:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-16 14:59 Brien
2003-04-16 16:51 ` Bruce Harada
2003-04-16 20:53 ` Robert White
2003-04-16 21:01   ` Brien
2003-04-16 22:05   ` root [this message]
2003-04-17  1:16     ` Mike Dresser
2003-04-17  5:34   ` Peter Svensson
     [not found] <200304161511.h3GFBoe7000614@81-2-122-30.bradfords.org.uk>
2003-04-16 15:41 ` Brien
2003-04-16 15:47   ` Mr. James W. Laferriere
2003-04-16 15:58   ` Charles Cazabon
2003-04-16 16:10   ` Chris Friesen
2003-04-17 12:46     ` mbs
2003-04-17 12:45       ` Alan Cox
     [not found]   ` <1050506129.28586.121.camel@dhcp22.swansea.linux.org.uk>
2003-04-16 16:38     ` Brien
2003-04-16 17:01       ` John Bradford
2003-04-16 18:15         ` Brien
2003-04-16 19:28           ` John Bradford
2003-04-16 20:51             ` Brien
2003-04-17  8:12               ` John Bradford
2003-04-20 16:58 Walt H

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=200304162205.XAA15178@mauve.demon.co.uk \
    --to=root@mauve.demon.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rwhite@casabyte.com \
    /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

all inboxes | Powered by JetHome®