mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Brien" <admin@brien.com>
To: "John Bradford" <john@grabjohn.com>
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 11:41:28 -0400	[thread overview]
Message-ID: <003801c3042e$a6bcbea0$6901a8c0@athialsinp4oc1> (raw)
In-Reply-To: <200304161511.h3GFBoe7000614@81-2-122-30.bradfords.org.uk>

Hi again,

(Thanks for replying, John.)

I ran Memtest86, and there're 290 errors that showed up from test 7. But the
thing that I don't understand is, if I use either of the RAM modules alone,
Linux loads and runs perfectly for as long as I've tried; Could it possibly
be a problem with something besides the RAM (e.g. motherboard, CPU)? And I
still don't know if my RAM setup is even supported by Linux -- I'm guessing
that it is though (?).

----- Original Message -----
From: "John Bradford" <john@grabjohn.com>
To: "Brien" <admin@brien.com>
Sent: Wednesday, April 16, 2003 11:11 AM
Subject: Re: my dual channel DDR 400 RAM won't work on any linux distro


> > I have a Gigabyte SINXP1394 motherboard, and 2 Kingston 512 MB DDR 400
(CL
> > 2.5) RAM modules installed. Whenever I try to install any Linux
> > distribution, I always get a black screen after the kernel loads
>
> Can you run Memtest86 on it for an hour or two, and confirm that there
> is nothing wrong with the memory?  Sometimes really obscure faults
> happen to get triggered with Linux, even if the machine appears to
> work with other operating systems.
>
> (By the way, good choice getting a Gigabyte board, I always use them,
> and never have problems with them).
>
> John.
>
>



       reply	other threads:[~2003-04-16 15:29 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200304161511.h3GFBoe7000614@81-2-122-30.bradfords.org.uk>
2003-04-16 15:41 ` Brien [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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
2003-04-17  1:16     ` Mike Dresser
2003-04-17  5:34   ` Peter Svensson

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='003801c3042e$a6bcbea0$6901a8c0@athialsinp4oc1' \
    --to=admin@brien.com \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®