Re: [coreboot] Samsung 550 Chromebook own Coreboot

[John Lewis]

Hi all,

Just want to confirm where we are in terms of things working or not.

The new system-agent binary works and recognises all 4 GB of RAM as 
long as an additional pei data field is added to Stefan's patches in 
http://review.coreboot.org/#/c/3831/ as detailed by Kyösti in the 
comments.

The patches in http://review.coreboot.org/#/c/3830/ don't appear to do 
anything for mrc.cache (it's still zero size) and this (or perhaps 
something else) results in a time to SeaBIOS prompt of between 5 to 9 
seconds.

I added a 64 GB SSD this afternoon, which I have working, but something 
strange went on with geometry - if I tried to dd the partition itself 
back it would crap out at 2 GB (this was after dd'ing the backed up mbr 
onto the new drive). If I dd'ed the whole device it worked, but the 
partition wouldn't mount, and fdisk would report that the partition was 
too large for the device. Luckily, after reboot, it worked anyway. :)

Summary: if we could get rid of the 5 to 9 second delay, and just 
confirm the drive detection geometry is A1 I think we are there.

John.

Samsung 550 Chromebook own Coreboot

[Aaron Durbin]

On Wed, Jul 31, 2013 at 9:24 AM, John Lewis  wrote:
> Hi all,
>
> Just want to confirm where we are in terms of things working or not.
>
> The new system-agent binary works and recognises all 4 GB of RAM as long as
> an additional pei data field is added to Stefan's patches in
> http://review.coreboot.org/#/c/3831/ as detailed by Kyösti in the comments.
>
> The patches in http://review.coreboot.org/#/c/3830/ don't appear to do
> anything for mrc.cache (it's still zero size) and this (or perhaps something
> else) results in a time to SeaBIOS prompt of between 5 to 9 seconds.

Can you show us 'ls -l $(obj)/mrc.cache' ? I didn't see
CONFIG_MRC_CACHE_SIZE in your .config. Also, what does 'cbfstool
image.rom print' say now? Build logs with V=1 would be helpful to see
what is occurring when mrc.cache is being created.
> I added a 64 GB SSD this afternoon, which I have working, but something
> strange went on with geometry - if I tried to dd the partition itself back
> it would crap out at 2 GB (this was after dd'ing the backed up mbr onto the
> new drive). If I dd'ed the whole device it worked, but the partition
> wouldn't mount, and fdisk would report that the partition was too large for
> the device. Luckily, after reboot, it worked anyway. :)
>
> Summary: if we could get rid of the 5 to 9 second delay, and just confirm
> the drive detection geometry is A1 I think we are there.
>
> John.