Hi Frederico,
On 26.11.2016 22:57, Federico Amedeo Izzo wrote:
> On 11/23/2016 10:14 AM, Zoran Stojsavljevic wrote:
>>
>> 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 ar
On 11/23/2016 10:14 AM, Zoran Stojsavljevic wrote:
>
> 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 th
Hello Charlotte++,
On Wed, Nov 23, 2016 at 2:40 AM, Charlotte Plusplus <
pluspluscharlo...@gmail.com> wrote:
> Edit devicetree.cb and set: register "max_mem_clock_mhz" = "666"
>
Good to know! Thank you for the tip, so Federico can try quick check and
see if this does work as workaround for now.
Thank you all for your support,
My x201 is a Nehalem architecture, not IVB (Ivy Bidge I suppose)
On 11/23/2016 02:40 AM, Charlotte Plusplus wrote:
>
> On Tue, Nov 22, 2016 at 4:28 PM, Zoran Stojsavljevic
> mailto:zoran.stojsavlje...@gmail.com>>
> wrote:
>
> If MCU is later, could you, please,
Hello
On Tue, Nov 22, 2016 at 4:28 PM, Zoran Stojsavljevic <
zoran.stojsavlje...@gmail.com> wrote:
> If MCU is later, could you, please, explain how you did this in IVB
> Coreboot code (since this might be beneficial to Federico's attempts)?
>
Edit devicetree.cb and set:
register "max_mem_clo
Hello
On Tue, Nov 22, 2016 at 2:50 PM, Kyösti Mälkki
wrote:
>
>> I tried using the MRC blob to compare the timings, but I must have done
>> something wrong in my code as it didn't work at all
>>
>
> See following commits:
> 5c10abe nb/intel/sandybridge: increase MMCONF_BASE_ADDRESS
> 0306e6a i
Hello Charlotte ++,
Forgive me/apologies for my ignorance in some parts... I would like to ask
few questions since I am not clear on some data here.
On Tue, Nov 22, 2016 at 8:30 PM, Charlotte Plusplus <
pluspluscharlo...@gmail.com> wrote:
> I have had similar issues with Corsair ram on the W520
Hi
On Tue, Nov 22, 2016 at 9:30 PM, Charlotte Plusplus <
pluspluscharlo...@gmail.com> wrote:
> I have had similar issues with Corsair ram on the W520 recently: sometimes
> not booting at all, sometimes being unstable (in memest) after a succesfull
> raminit.
>
> The only way I could get the 4 dim
I have had similar issues with Corsair ram on the W520 recently: sometimes
not booting at all, sometimes being unstable (in memest) after a succesfull
raminit.
The only way I could get the 4 dimms to work was to hardcode some SPDs, or
set the MCU to a much slower speed.
Like you, I found removing
On Tue, Nov 22, 2016 at 3:35 PM, Federico Amedeo Izzo
wrote:
> Hello,
>
> I have a problem with my ThinkPad X201 (nehalem)
>
> I have two sticks of Samsung 4GB 2Rx8 PC3-10600S (1333MHz)
> When i use only one of them in one of the two slots, the computer boots
> fine,
> but when i use both of them
Hello Federico,
I would like to suggest one quick probe: to reprogram your flash with
Nehalem's true BIOS, and see if use case with both DDRAMs' are going to
bring OS (whatever it is, assuming Linux) up. This can give to you two
possibilities:
[1] Both DDRAMs with BIOS work (then you have problem
11 matches
Mail list logo
