<div dir="ltr"><div>Just checking to make sure it was still populated... Now we know it is the internal memory that is the issue.</div><div><div><br></div></div><div>I suspect you may now be hitting the original issue that Stefan was trying to fix with the systemagent binary changes (<a href="http://review.coreboot.org/#/c/3568/">http://review.coreboot.org/#/c/3568/</a>) that were reverted to get this booting in the first place.</div>
<div><br></div><div>Stefan has uploaded a patch that applies on top of the earlier reverted patch. You could try to undo the revert, switch back to the systemagent-r6 binary, and apply this new patch that was just uploaded:<br>
</div><div><a href="http://review.coreboot.org/#/c/3831/1">http://review.coreboot.org/#/c/3831</a>/<br></div><div>(and maybe <a href="http://review.coreboot.org/#/c/3830/">http://review.coreboot.org/#/c/3830/</a> too? Stefan?)</div>
<div><br></div><div>Binary blobs ruin all the fun.</div><div><br></div><div>-duncan</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jul 29, 2013 at 2:50 PM, John Lewis <span dir="ltr"><<a href="mailto:jlewis@johnlewis.ie" target="_blank">jlewis@johnlewis.ie</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So the DIMM slot happens to be empty/seated badly on both our Lumpy's? Don't think so.<br><br>Mine acted like a brick with the SODIMM removed.<br>
<br>John.<div class="im"><br><br>Duncan Laurie <<a href="mailto:dlaurie@chromium.org" target="_blank">dlaurie@chromium.org</a>> wrote:<br><br><div dir="ltr">Lumpy should have 2GB of on-board memory and a DIMM slot that comes with a 2GB DIMM.<br>
<div><br></div><div>Coreboot seems to detect the on-board memory and finds the SPD binary for it, any chance the DIMM slot is empty?</div>
<div><br></div><div><pre style="white-space:pre-wrap;word-wrap:break-word">Memory Straps:
- memory capacity 2GB
- die revision 1
- vendor Samsung
CBFS: Looking for 'spd.bin' starting from 0x700000.
CBFS: Found file (offset=0x7dc000, len=1536).
</pre></div><div><br></div><div>I think the console output should show a summary after the MRC binary runs, but the verbose CBFS output is overflowing the buffer:<br></div><div><a href="http://review.coreboot.org/gitweb?p=coreboot.git;a=blob;f=src/northbridge/intel/sandybridge/raminit.c;h=3eb2fb3e79c01cfc8d75319b1089bb1aafde9806;hb=HEAD#l168" target="_blank">http://review.coreboot.org/gitweb?p=coreboot.git;a=blob;f=src/northbridge/intel/sandybridge/raminit.c;h=3eb2fb3e79c01cfc8d75319b1089bb1aafde9806;hb=HEAD#l168</a><br>
</div><div><br></div><div>-duncan<br></div><div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="im">On Mon, Jul 29, 2013 at 8:14 AM, Aaron Durbin <span dir="ltr"><<a href="mailto:adurbin@chromium.org" target="_blank">adurbin@chromium.org</a>></span> wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">Kyösti,<br>
<br>
I'm not certain it's just the last entry of the e820. mrc is just<br>
seeing 2GiB of ram and setting it up that way.<br>
<br>
TOUUD 0x100600000 TOLUD 0x7f200000 TOM 0x80000000<br>
MEBASE 0x7f800000<br>
IGD decoded, subtracting 32M UMA and 2M GTT<br>
TSEG base 0x7c800000 size 8M<br>
<div>Available memory below 4GB: 1992M<br>
</div>Available memory above 4GB: 6M<br>
</div><span><font color="#888888"><br>
-Aaron<br>
</font></span><div><div><br><div class="im">
On Mon, Jul 29, 2013 at 10:04 AM, Kyösti Mälkki <<a href="mailto:kyosti.malkki@gmail.com" target="_blank">kyosti.malkki@gmail.com</a>> wrote:<br>
> On Mon, 2013-07-29 at 15:19 +0100, John Lewis wrote:<br>
>> Where do I find/build cbmem binary?<br>
>><br>
>> Please find attached dmesg.<br>
><br>
> Hi<br>
><br>
> I have same issue. Only about 2Gib of 4GiB installed shows. I had not<br>
> noticed this until You pointed this out. Looks like a problem with the<br>
> last entry coreboot creates in e820 memory map.<br>
><br>
><br>
> This is from your dmesg, I see same with (close to) current master.<br>
><br>
> [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000001005fffff] usable<br>
><br>
><br>
> The coreboot image my Samsung 550 originally shipped with had this:<br>
><br>
> [ 0.000000] BIOS-e820: 0000000100000000 - 000000014fe00000 (usable)<br>
><br>
><br>
><br></div><div class="im">
> Kyösti<br>
><br>
<br>
--<br>
coreboot mailing list: <a href="mailto:coreboot@coreboot.org" target="_blank">coreboot@coreboot.org</a><br>
<a href="http://www.coreboot.org/mailman/listinfo/coreboot" target="_blank">http://www.coreboot.org/mailman/listinfo/coreboot</a><br>
</div></div></div></blockquote></div><br></div>
</blockquote></div><br></div>