[coreboot] Samsung 550 Chromebook own Coreboot

[John Lewis]

Also, later on in dbmem console output "Available memory below 4GB: 
1992M"

On 29/07/2013 15:39, John Lewis wrote:

> Right, here is cbmem console output, which was "-c" not "-l". As you
> can see, it says fairly early on it recognises 2GB not 4. It's not
> exactly verbose about why. I also noticed later in the dmesg output 
> that
> "[ 1.071359] [drm] Memory usable by graphics device = 2048M", that
> doesn't mean it's reserved, does it?
>
> On 29/07/2013 15:31, Aaron Durbin wrote:
>
>> It's under the 'util' directory in the coreboot repository:
>
>
http://review.coreboot.org/gitweb?p=coreboot.git;a=tree;f=util/cbmem;h=14fbe6c462edf294e247e95616700cee7a6f46db;hb=refs/heads/master
>
>> From this: [ 0.000000] e820: BIOS-provided physical RAM map: [
>> 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] 
>> usable
>> [ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff]
>> reserved [ 0.000000] BIOS-e820: [mem
>> 0x00000000000f0000-0x00000000000fffff] reserved [ 0.000000] 
>> BIOS-e820:
>> [mem 0x0000000000100000-0x000000001fffffff] usable [ 0.000000]
>> BIOS-e820: [mem 0x0000000020000000-0x00000000201fffff] reserved [
>> 0.000000] BIOS-e820: [mem 0x0000000020200000-0x000000003fffffff] 
>> usable
>> [ 0.000000] BIOS-e820: [mem 0x0000000040000000-0x00000000401fffff]
>> reserved [ 0.000000] BIOS-e820: [mem
>> 0x0000000040200000-0x000000007c6dffff] usable [ 0.000000] BIOS-e820:
>> [mem 0x000000007c6e0000-0x000000007f1fffff] reserved [ 0.000000]
>> BIOS-e820: [mem 0x00000000f0000000-0x00000000f3ffffff] reserved [
>> 0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000001005fffff] 
>> usable
>> Adding up the reported usable memory should jive with your
>> expectations. As for needing console, yes, you will need to compile
>> with console. CONFIG_EARLY_CBMEM_INIT=y CONFIG_CONSOLE_CBMEM=y On 
>> Mon,
>> Jul 29, 2013 at 9:19 AM, John Lewis <jlewis at johnlewis.ie [6]> wrote:
>>
>>> Where do I find/build cbmem binary? Please find attached dmesg. On
>>> 29/07/2013 14:43, Aaron Durbin wrote:
>>>
>>>> Can you provide the full firmware log and dmesg? 'cbmem -l' should
>>>> give you the firmware log. On Sun, Jul 28, 2013 at 7:47 AM, John
>>>> Lewis <jlewis at johnlewis.ie [3][3]> wrote:
>>>>
>>>>> Guys, I have noticed that not all the 4 GB or RAM is showing, and
>>>>> I get this message in the kernel: [ 0.000000] Memory:
>>>>> 1914260k/4200448k available (6486k kernel code, 2160136k absent,
>>>>> 126052k reserved, 6780k data, 1412k init) Any idea what the
>>>>> problem is (mrc.bin), and what I might do to workaround? John. --
>>>>> coreboot mailing list: coreboot at coreboot.org [1] [1] [1]
>>>>> http://www.coreboot.org/mailman/listinfo/coreboot [2] [2] [2]
>>> Links: ------ [1] mailto:coreboot at coreboot.org [4] [4] [2]
>>> http://www.coreboot.org/mailman/listinfo/coreboot [5] [5]
>
> Links:
> ------
> [1] mailto:coreboot at coreboot.org
> [2] http://www.coreboot.org/mailman/listinfo/coreboot
> [3] mailto:jlewis at johnlewis.ie
> [4] mailto:coreboot at coreboot.org
> [5] http://www.coreboot.org/mailman/listinfo/coreboot


Links:
------
[1] mailto:coreboot at coreboot.org
[2] http://www.coreboot.org/mailman/listinfo/coreboot
[3] mailto:jlewis at johnlewis.ie
[4] mailto:coreboot at coreboot.org
[5] http://www.coreboot.org/mailman/listinfo/coreboot