<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 11/23/2016 10:14 AM, Zoran
Stojsavljevic wrote:<br>
</div>
<blockquote
cite="mid:CAGAf8Lx7_uuMFMRHey94B-ognJmgCo5H4HkRbeZtYj=UWAwT3g@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra">
<div class="gmail_quote">
<div>Federico, I have here also suggestion for you. You
should try to run only one DDR memory stick, and then
record the memory values (since I see from your logs that
they are identical for both memories/DDRs), and then to
try to hard-code them for both sticks, altogether avoiding
raminit.c setup, and see if this improves your situation?!</div>
</div>
</div>
</div>
</blockquote>
<p>Hi Zoran and others,</p>
<p>I finally flashed again coreboot after trying the Lenovo BIOS.<br>
I used the decode-dimms util to dump RAM info while on the Lenovo
BIOS with both RAM sticks,<br>
and run the same program on the coreboot BIOS with just one stick.</p>
<p>Sadly the output on coreboot is the same of the output on Lenovo
BIOS so no info gained by this.</p>
<p>I will attach the output from the Lenovo BIOS in case it turns
out useful.</p>
<p>The next step I will try will be to modify raminit.c of Nehalem
to accept hardcoded frequency as SandyBridge does,<br>
hoping that this will be a temporary fix to get the two DIMMs
working.<br>
</p>
</body>
</html>