public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Bacott <cbacot@runbox.com>
To: Ronald Bultje <rbultje@ronald.bitfreak.net>,
	Chris Siebenmann <cks@utcc.utoronto.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: >128 MB RAM stability problems (again)
Date: Wed, 4 Jul 2001 15:57:43 -0500	[thread overview]
Message-ID: <01070415574300.01307@darkstar> (raw)
In-Reply-To: <01Jul4.172916edt.62972@gpu.utcc.utoronto.ca> <994322676.768.0.camel@tux>
In-Reply-To: <994322676.768.0.camel@tux>

> So.... this leads to the conclusion that the memory is okay, and that
> something else must be the problem.... Could it still be a failing power
> supply or something? It seems both computers have a 230 W power supply.
> Might be a problem, I guess, I can buy a 400 W thingy if that makes
> sense.

Can't comment. Another post states that they are using a 400W with problems. 

> Other solutions I heard:
> - antistatic wrist strap: already have one :-)
> - BIOS fiddling... What exactly should I look for? They are, as far as I
> can see, identical memory sticks, probably both from different
> suppliers, but besides that quite the same....
> - are there different brands of memory of different quality and might
> that be a possible cause of the problems? And if so - what are good
> memory brands and what are the bad ones?
> - I mixed different types of SDRAM... Could be it.... My mainboard
> manual is not really clear about this.... And I have no clue what brand
> of memory I bought... they are all 133 MHz SDRAM sticks, some 64 MB,
> some 128 MB.... MB manual says it can handle all 64/128 MB sticks...
> - <your solution here :-)>
Are you mixing connector types, ie gold/silver (I can't remember what they 
are made of )? This _will_ give you problems, among which including 
stability. You should _always_ match connectors with the mainboard. I 
apologize if you already know this. 

> Anyway, thanks for any advice until now and thanks for listening again,
> hope to hear more solutions.

See above, I'm just throwing out a potential solution.

-- 
Chris Bacott

  reply	other threads:[~2001-07-05  8:56 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <01Jul4.172916edt.62972@gpu.utcc.utoronto.ca>
2001-07-05  8:44 ` >128 MB RAM stability problems (again) Ronald Bultje
2001-07-04 20:57   ` Chris Bacott [this message]
2001-07-05  7:22   ` StarTux
2001-07-05  8:40   ` Reza Roboubi
2001-07-05 10:50     ` Ronald Bultje
2001-07-05 15:41       ` Reza Roboubi
2001-07-05  9:15   ` D. Stimits
2001-07-04 20:45 Ronald Bultje
2001-07-04 19:11 ` J Sloan
2001-07-04 19:20 ` Charles Cazabon
2001-07-04 19:29 ` Alan Cox
2001-07-04 19:47   ` William Scott Lockwood III
2001-07-05  3:16   ` Bill Pringlemeir
2001-07-05  6:37     ` Ragnar Hojland Espinosa
2001-07-05 15:38       ` Bill Pringlemeir
2001-07-04 19:44 ` mark
2001-07-04 20:01 ` Jeffrey W. Baker
2001-07-04 20:05 ` George Bonser
2001-07-04 22:11 ` D. Stimits
2001-07-04 23:47 ` Peter Bornemann
2001-07-05  1:22   ` Reza Roboubi
2001-07-05  1:43     ` Charles Cazabon
2001-07-05  1:58     ` George Bonser
2001-07-05 15:51 ` Don Krause
2001-07-05 17:22   ` Gary White (Network Administrator)
2001-07-05 20:45 ` Peter A. Castro
2001-07-06 17:55   ` Ronald Bultje
2001-07-09 14:24     ` Andreas Bombe
  -- strict thread matches above, loose matches on Subject: below --
2001-07-04 20:06 Alessandro Motter Ren
2001-07-04 20:16 ` George Bonser
2001-07-04 20:52 ` Ronald Bultje

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=01070415574300.01307@darkstar \
    --to=cbacot@runbox.com \
    --cc=cks@utcc.utoronto.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rbultje@ronald.bitfreak.net \
    /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