public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "José Pedro Saraiva" <nocive@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] No kernel boot after inserting more ram
Date: Sun, 20 Jan 2008 21:47:48 +0000	[thread overview]
Message-ID: <12a679470801201347w2d1d01c4y92a9079fd26580bd@mail.gmail.com> (raw)
In-Reply-To: <12a679470801191531l759d93b5ld7b780057696fe34@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2006 bytes --]

Well, after all kinds of tests and trying different types of memory
configurations, I can only conclude that my kernel boots normally with 1 GB
of RAM installed but hangs when I have 2 GB of RAM installed. I can't find a
logical reason for this to happen.

Any pointers or suggestions are welcome,
Regards

On Jan 19, 2008 11:31 PM, José Pedro Saraiva <nocive@gmail.com> wrote:

> Following your replies I've done the following, in an attempt to isolate
> the problem:
> (memory #1 - "old" memory, memory #2 - new memory)
>
> - Runned memtest on both memories with 0 errors
> - Booted with both memories... kernel hang
> - Booted with memory #1 on slot #1 successfully
> - Booted with memory #1 on slot #2 successfully
> - Booted with memory #2 on slot #1 successfully
> - Booted with memory #2 on slot #2 successfully
> - Booted with both memories on windows successfully
>
> For some reason, my kernel hangs if I have 2 GB of RAM installed.
> And I do have High memory support (4GB), although that doesn't seem
> relevant.
> Ideas? :X
>
> Thank you all for the quick replies.
> Cheers
>
>
> On Jan 19, 2008 2:29 PM, Hal Martin <hal.martin@gmail.com> wrote:
>
> > An alternative to running memtest (which is quite easy to do, I might
> > add) would be to remove the original RAM and see if the computer boots
> > with the new RAM only.
> >
> > Alternatively, you could just run memtest, as it is included with many
> > BIOSs now. It doesn't take long to identify problems, if there are any.
> > I find that test #5 is the best test for finding problems, however it
> > tends to keep you in the dark until it's finished the test.
> >
> >
> > -Hal
> >
> >
> > Neil Bothwick wrote:
> > > On Fri, 18 Jan 2008 22:58:59 +0000, José Pedro Saraiva wrote:
> > >
> > >
> > >> I'm sure there's nothing wrong with the RAM,
> > >>
> > >
> > > How? Have you run memtest?
> > >
> > >
> > >
> >
> > --
> > gentoo-user@lists.gentoo.org mailing list
> >
> >
>

[-- Attachment #2: Type: text/html, Size: 2699 bytes --]

  reply	other threads:[~2008-01-20 21:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18 22:58 [gentoo-user] No kernel boot after inserting more ram José Pedro Saraiva
2008-01-19  0:04 ` Mick
2008-01-19  0:10 ` Philip Webb
2008-01-19  0:26   ` Mike
2008-01-19  0:37     ` Ricardo Saffi Marques
2008-01-19  1:01 ` Statux
2008-01-19 11:16 ` Neil Bothwick
2008-01-19 14:29   ` Hal Martin
2008-01-19 23:31     ` José Pedro Saraiva
2008-01-20 21:47       ` José Pedro Saraiva [this message]
2008-01-20 22:43         ` Thomas Kahle
2008-01-21 15:11           ` José Pedro Saraiva
2008-01-20 22:55         ` de Almeida, Valmor F.

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=12a679470801201347w2d1d01c4y92a9079fd26580bd@mail.gmail.com \
    --to=nocive@gmail.com \
    --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