Please try the attached patch, and run memtest for a while (overnight
would probably be best), and let me/us know the results. If this seems
to correct the issue, then I'll work on a patch to initialize the
extra ranks.
Thanks,
Corey
On Tue, Aug 3, 2010 at 5:38 PM, Corey Osgood <[email protected]> wrote:
> Yeah, I'm wondering if it's maybe that there's 2 ranks and each one
> needs to be initialized seperately, but only one is getting
> initialized. IT took away internet access on my linux box at work, so
> I can write a patch to test it out, but I can't send it until I get
> home (in about 7 hours)
>
> -Corey
>
> On Tue, Aug 3, 2010 at 10:41 AM, ron minnich <[email protected]> wrote:
>> Well, in the worst-case scenario, as a test, you can modify the
>> raminit and just force it to use only 512M. Just as a test. I do this
>> sometimes when I have ram issues.
>>
>> ron
>>
>> --
>> coreboot mailing list: [email protected]
>> http://www.coreboot.org/mailman/listinfo/coreboot
>>
>
Index: src/northbridge/via/cn700/raminit.c
===================================================================
--- src/northbridge/via/cn700/raminit.c (revision 5682)
+++ src/northbridge/via/cn700/raminit.c (working copy)
@@ -152,6 +152,14 @@
ranks = spd_read_byte(ctrl->channel0[0], SPD_NUM_DIMM_BANKS);
ranks = (ranks & 0x07) + 1;
+ if(ranks > 1)
+ {
+ printk(BIOS_DEBUG, "ranks = %02x, setting ranks = 1 to debug. please run memtest to check ram initialization\n", ranks);
+ ranks = 1;
+ } else {
+ printk(BIOS_DEBUG, "ranks = %02x, this is not the problem\n", ranks);
+ }
+
density = spd_read_byte(ctrl->channel0[0],
SPD_DENSITY_OF_EACH_ROW_ON_MODULE);
switch (density) {
--
coreboot mailing list: [email protected]
http://www.coreboot.org/mailman/listinfo/coreboot
