From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JGNAF-00040D-99 for garchives@archives.gentoo.org; Sat, 19 Jan 2008 23:31:51 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F1CD3E04DB; Sat, 19 Jan 2008 23:31:29 +0000 (UTC) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 572C1E04DA for ; Sat, 19 Jan 2008 23:31:29 +0000 (UTC) Received: by py-out-1112.google.com with SMTP id w53so1900553pyg.25 for ; Sat, 19 Jan 2008 15:31:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=mv1wvWoNeQrk0W2q7DufGPJ60ddjl2lo37hRTcmoV6g=; b=KR/QdW0lj+UU2TBYnYytPdjCuOdlbJA4Tzmg5C8ooMqM48So/jMwvohhj6DBBVGDUPghFLYIhzWqgB/N3R85qb4VdkN01E2rgKITLdCQkv1mHE65ex8rILHRpzVAjnjTVijZb6PV3yaAOKHV/NqW+Tm8zMxIaxWtXnGUHMF5E7w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=iya+d8PjGK3KGIda3r+2wiefHK0qtQpZxbXn/LB0KoQKC9SNuxNK9XnJhhFlfjfejHWmlstdXRlw960/Uk9Hp8K40ROQlxIg32Z53GPMV7nUUiX+R/43t/Nep26+b8VZRhkQRfc3/Kr9JmiW62tu/ICKa+KJliztQ+/cgflsib8= Received: by 10.65.103.14 with SMTP id f14mr11082950qbm.12.1200785487944; Sat, 19 Jan 2008 15:31:27 -0800 (PST) Received: by 10.64.233.16 with HTTP; Sat, 19 Jan 2008 15:31:27 -0800 (PST) Message-ID: <12a679470801191531l759d93b5ld7b780057696fe34@mail.gmail.com> Date: Sat, 19 Jan 2008 23:31:27 +0000 From: "=?ISO-8859-1?Q?Jos=E9_Pedro_Saraiva?=" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] No kernel boot after inserting more ram In-Reply-To: <47920940.5080600@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_7145_23333241.1200785487935" References: <12a679470801181458y54f73ed8i6f81761b7e8f72b8@mail.gmail.com> <20080119111651.48e20495@loonquawl.digimed.co.uk> <47920940.5080600@gmail.com> X-Archives-Salt: 5c9172eb-1616-4a68-9862-87492b6875e1 X-Archives-Hash: c0376594cd59690c56b4edc922b82722 ------=_Part_7145_23333241.1200785487935 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Following your replies I've done the following, in an attempt to isolate th= e 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 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=E9 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 > > ------=_Part_7145_23333241.1200785487935 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Following your replies I've done the following, in an attempt to isolat= e the problem:
(memory #1 - "old" memory, memory #2 - new memo= ry)

- 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 successfu= lly
- Booted with memory #2 on slot #2 successfully
- Booted with bot= h 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 r= elevant.
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
ad= d) would be to remove the original RAM and see if the computer boots
wit= h 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=E9 P= edro Saraiva wrote:
>
>
>> I'm sure there's no= thing wrong with the RAM,
>>
>
> How? Have you run memtest?
>
>
= >

--

------=_Part_7145_23333241.1200785487935-- -- gentoo-user@lists.gentoo.org mailing list