On Jan 20, 2008 10:43 PM, Thomas Kahle <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Hi, > > I guess your kernel is configured to support only 1GB of RAM. In the > kernel configuration look for "Processor Type and Features" > There you find the Option. High Memory Support. > Probably it is set to "off". Set it to 4GB then recompile the kernel. > That should do it.
That was already suggested in a previous reply :) I do have High Memory Support enabled with 4GB, still, it refuses to boot! > > > have fun > Tom > > José Pedro Saraiva wrote: > > 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 <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> 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 <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> 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 > > <mailto:gentoo-user@lists.gentoo.org> mailing list > > > > > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.7 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFHk86lrpEWPKIUt7MRAtm6AJ9EbOJfcrxM7UoceMz3B2gdpKLn1gCfdMMh > +04EiTXdzcE5JOp6ON5IQOQ= > =SdgG > -----END PGP SIGNATURE----- > -- > gentoo-user@lists.gentoo.org mailing list > >
