1 |
On Jan 20, 2008 10:43 PM, Thomas Kahle <tom111@×××.de> wrote: |
2 |
|
3 |
> -----BEGIN PGP SIGNED MESSAGE----- |
4 |
> Hash: SHA1 |
5 |
> |
6 |
> |
7 |
> Hi, |
8 |
> |
9 |
> I guess your kernel is configured to support only 1GB of RAM. In the |
10 |
> kernel configuration look for "Processor Type and Features" |
11 |
> There you find the Option. High Memory Support. |
12 |
> Probably it is set to "off". Set it to 4GB then recompile the kernel. |
13 |
> That should do it. |
14 |
|
15 |
That was already suggested in a previous reply :) |
16 |
I do have High Memory Support enabled with 4GB, still, it refuses to boot! |
17 |
|
18 |
> |
19 |
> |
20 |
> have fun |
21 |
> Tom |
22 |
> |
23 |
> José Pedro Saraiva wrote: |
24 |
> > Well, after all kinds of tests and trying different types of memory |
25 |
> > configurations, I can only conclude that my kernel boots normally with 1 |
26 |
> > GB of RAM installed but hangs when I have 2 GB of RAM installed. I can't |
27 |
> > find a logical reason for this to happen. |
28 |
> > |
29 |
> > Any pointers or suggestions are welcome, |
30 |
> > Regards |
31 |
> > |
32 |
> > On Jan 19, 2008 11:31 PM, José Pedro Saraiva <nocive@×××××.com |
33 |
> > <mailto:nocive@×××××.com>> wrote: |
34 |
> > |
35 |
> > Following your replies I've done the following, in an attempt to |
36 |
> > isolate the problem: |
37 |
> > (memory #1 - "old" memory, memory #2 - new memory) |
38 |
> > |
39 |
> > - Runned memtest on both memories with 0 errors |
40 |
> > - Booted with both memories... kernel hang |
41 |
> > - Booted with memory #1 on slot #1 successfully |
42 |
> > - Booted with memory #1 on slot #2 successfully |
43 |
> > - Booted with memory #2 on slot #1 successfully |
44 |
> > - Booted with memory #2 on slot #2 successfully |
45 |
> > - Booted with both memories on windows successfully |
46 |
> > |
47 |
> > For some reason, my kernel hangs if I have 2 GB of RAM installed. |
48 |
> > And I do have High memory support (4GB), although that doesn't seem |
49 |
> > relevant. |
50 |
> > Ideas? :X |
51 |
> > |
52 |
> > Thank you all for the quick replies. |
53 |
> > Cheers |
54 |
> > |
55 |
> > |
56 |
> > On Jan 19, 2008 2:29 PM, Hal Martin <hal.martin@×××××.com |
57 |
> > <mailto:hal.martin@×××××.com>> wrote: |
58 |
> > |
59 |
> > An alternative to running memtest (which is quite easy to do, I |
60 |
> > might |
61 |
> > add) would be to remove the original RAM and see if the computer |
62 |
> > boots |
63 |
> > with the new RAM only. |
64 |
> > |
65 |
> > Alternatively, you could just run memtest, as it is included |
66 |
> > with many |
67 |
> > BIOSs now. It doesn't take long to identify problems, if there |
68 |
> > are any. |
69 |
> > I find that test #5 is the best test for finding problems, |
70 |
> > however it |
71 |
> > tends to keep you in the dark until it's finished the test. |
72 |
> > |
73 |
> > |
74 |
> > -Hal |
75 |
> > |
76 |
> > |
77 |
> > Neil Bothwick wrote: |
78 |
> > > On Fri, 18 Jan 2008 22:58:59 +0000, José Pedro Saraiva wrote: |
79 |
> > > |
80 |
> > > |
81 |
> > >> I'm sure there's nothing wrong with the RAM, |
82 |
> > >> |
83 |
> > > |
84 |
> > > How? Have you run memtest? |
85 |
> > > |
86 |
> > > |
87 |
> > > |
88 |
> > |
89 |
> > -- |
90 |
> > gentoo-user@l.g.o |
91 |
> > <mailto:gentoo-user@l.g.o> mailing list |
92 |
> > |
93 |
> > |
94 |
> > |
95 |
> |
96 |
> -----BEGIN PGP SIGNATURE----- |
97 |
> Version: GnuPG v2.0.7 (GNU/Linux) |
98 |
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
99 |
> |
100 |
> iD8DBQFHk86lrpEWPKIUt7MRAtm6AJ9EbOJfcrxM7UoceMz3B2gdpKLn1gCfdMMh |
101 |
> +04EiTXdzcE5JOp6ON5IQOQ= |
102 |
> =SdgG |
103 |
> -----END PGP SIGNATURE----- |
104 |
> -- |
105 |
> gentoo-user@l.g.o mailing list |
106 |
> |
107 |
> |