Re: [coreboot] unable to build coreboot with grub

[John Lewis]

Hi,

It's in "Chipset Options" -> "Size of CBFS filesystem in ROM" - 0x200000 
or 0x400000 will work.

Cheers,

John.

On 12/10/14 10:51, Vipin Gahlaut wrote:
> Thanks Vladimir,
>
> Can you please let me know how to increase the ROM size?
>
> -----Original Message-----
> From: Vladimir 'φ-coder/phcoder' Serbinenko [mailto:[e-mail]
> ]
> Sent: Sunday, October 12, 2014 3:02 PM
> To: Vipin Gahlaut; coreboot
> Subject: Re: [coreboot] unable to build coreboot with grub
>
> On 12.10.2014 08:03, Vipin Gahlaut wrote:
> > Hi,
> >
> > I have cloned latest coreboot and trying to build with grub2 as payload.
> > in make menuconfig I select grub2 instead of seabios. when I fire make
> > command it checkout latest grub and that fails to build. for 2 reasons.
> >
> > Due to some initialization errors that I managed to fix with below
> > changes
> > -struct grub_linux_initrd_context initrd_ctx = { 0, };
> > +struct grub_linux_initrd_context initrd_ctx = { 0,NULL,0 };
> >
>
> Sounds like you have an old gcc
> > grub size issue as below that I am unable to resolve and looking
> > for your help. I am building for QEMU and using QEMU version 2.1.2.
> >
> > E: Could not add
> > [payloads/external/GRUB2/grub2/build/default_payload.elf, 268862 bytes
> > (262 KB)@0x0]; too big?
> > E: Failed to add
> > 'payloads/external/GRUB2/grub2/build/default_payload.elf' into ROM image.
> >
>
> Increase ROM size.
> >
> >
> >
>
> On Sun, Oct 12, 2014 at 11:33 AM, Vipin Gahlaut <[e-mail]
> > wrote:
> Hi,
>
> I have cloned latest coreboot and trying to build with grub2 as
> payload. in make menuconfig I select grub2 instead of seabios. when
> I fire make command it checkout latest grub and that fails to build.
> for 2 reasons.
>
> 1. Due to some initialization errors that I managed to fix with
> below changes
> -  struct grub_linux_initrd_context initrd_ctx = { 0, };
> +  struct grub_linux_initrd_context initrd_ctx = { 0,NULL,0 };
>
> 2. grub size issue as below that I am unable to resolve and looking
> for your help. I am building for QEMU and using QEMU version 2.1.2.
>
> E: Could not add
> [payloads/external/GRUB2/grub2/build/default_payload.elf, 268862
> bytes (262 KB)@0x0]; too big?
> E: Failed to add
> 'payloads/external/GRUB2/grub2/build/default_payload.elf' into ROM
> image.

unable to build coreboot with grub

[Vladimir 'φ-coder/phcoder' Serbinenko]

On 12.10.2014 11:57, John Lewis wrote:
> Hi,
>
> It's in "Chipset Options" -> "Size of CBFS filesystem in ROM" - 0x200000
> or 0x400000 will work.

This is only for recent intel chipsets.
> Cheers,
>
> John.
>
> On 12/10/14 10:51, Vipin Gahlaut wrote:
> > Thanks Vladimir,
> >
> > Can you please let me know how to increase the ROM size?
> >
> > -----Original Message-----
> > From: Vladimir 'φ-coder/phcoder' Serbinenko [mailto:[e-mail]
> > ]
> > Sent: Sunday, October 12, 2014 3:02 PM
> > To: Vipin Gahlaut; coreboot
> > Subject: Re: [coreboot] unable to build coreboot with grub
> >
> > On 12.10.2014 08:03, Vipin Gahlaut wrote:
> > > Hi,
> > >
> > > I have cloned latest coreboot and trying to build with grub2 as
> >
> > payload.
> > > in make menuconfig I select grub2 instead of seabios. when I fire make
> > > command it checkout latest grub and that fails to build. for 2
> >
> > reasons.
> > >
> > > Due to some initialization errors that I managed to fix with below
> > > changes
> > > -struct grub_linux_initrd_context initrd_ctx = { 0, };
> > > +struct grub_linux_initrd_context initrd_ctx = { 0,NULL,0 };
> > >
> >
> > Sounds like you have an old gcc
> > > grub size issue as below that I am unable to resolve and looking
> > > for your help. I am building for QEMU and using QEMU version 2.1.2.
> > >
> > > E: Could not add
> > > [payloads/external/GRUB2/grub2/build/default_payload.elf, 268862 bytes
> > > (262 KB)@0x0]; too big?
> > > E: Failed to add
> > > 'payloads/external/GRUB2/grub2/build/default_payload.elf' into ROM
> >
> > image.
> > >
> >
> > Increase ROM size.
> > >
> > >
> > >
> >
> > On Sun, Oct 12, 2014 at 11:33 AM, Vipin Gahlaut <[e-mail]
> > > wrote:
> > Hi,
> >
> > I have cloned latest coreboot and trying to build with grub2 as
> > payload. in make menuconfig I select grub2 instead of seabios. when
> > I fire make command it checkout latest grub and that fails to build.
> > for 2 reasons.
> >
> > 1. Due to some initialization errors that I managed to fix with
> > below changes
> > -  struct grub_linux_initrd_context initrd_ctx = { 0, };
> > +  struct grub_linux_initrd_context initrd_ctx = { 0,NULL,0 };
> >
> > 2. grub size issue as below that I am unable to resolve and looking
> > for your help. I am building for QEMU and using QEMU version 2.1.2.
> >
> > E: Could not add
> > [payloads/external/GRUB2/grub2/build/default_payload.elf, 268862
> > bytes (262 KB)@0x0]; too big?
> > E: Failed to add
> > 'payloads/external/GRUB2/grub2/build/default_payload.elf' into ROM
> > image.

unable to build coreboot with grub

[John Lewis]

On 12/10/14 11:12, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> On 12.10.2014 11:57, John Lewis wrote:
> > Hi,
> >
> > It's in "Chipset Options" -> "Size of CBFS filesystem in ROM" - 0x200000
> > or 0x400000 will work.
>
> This is only for recent intel chipsets.

Oh dear, this is probably why I should just stalk the list, rather than 
pipe up occasionally. ;)
> > Cheers,
> >
> > John.
> >
> > On 12/10/14 10:51, Vipin Gahlaut wrote:
> > > Thanks Vladimir,
> > >
> > > Can you please let me know how to increase the ROM size?
> > >
> > > -----Original Message-----
> > > From: Vladimir 'φ-coder/phcoder' Serbinenko [mailto:[e-mail]
> > > ]
> > > Sent: Sunday, October 12, 2014 3:02 PM
> > > To: Vipin Gahlaut; coreboot
> > > Subject: Re: [coreboot] unable to build coreboot with grub
> > >
> > > On 12.10.2014 08:03, Vipin Gahlaut wrote:
> > > > Hi,
> > > >
> > > > I have cloned latest coreboot and trying to build with grub2 as
> > >
> > > payload.
> > > > in make menuconfig I select grub2 instead of seabios. when I fire make
> > > > command it checkout latest grub and that fails to build. for 2
> > >
> > > reasons.
> > > >
> > > > Due to some initialization errors that I managed to fix with below
> > > > changes
> > > > -struct grub_linux_initrd_context initrd_ctx = { 0, };
> > > > +struct grub_linux_initrd_context initrd_ctx = { 0,NULL,0 };
> > > >
> > >
> > > Sounds like you have an old gcc
> > > > grub size issue as below that I am unable to resolve and looking
> > > > for your help. I am building for QEMU and using QEMU version 2.1.2.
> > > >
> > > > E: Could not add
> > > > [payloads/external/GRUB2/grub2/build/default_payload.elf, 268862 bytes
> > > > (262 KB)@0x0]; too big?
> > > > E: Failed to add
> > > > 'payloads/external/GRUB2/grub2/build/default_payload.elf' into ROM
> > >
> > > image.
> > > >
> > >
> > > Increase ROM size.
> > > >
> > > >
> > > >
> > >
> > > On Sun, Oct 12, 2014 at 11:33 AM, Vipin Gahlaut <[e-mail]
> > > > wrote:
> > >  Hi,
> > >
> > >  I have cloned latest coreboot and trying to build with grub2 as
> > >  payload. in make menuconfig I select grub2 instead of seabios. when
> > >  I fire make command it checkout latest grub and that fails to build.
> > >  for 2 reasons.
> > >
> > >  1. Due to some initialization errors that I managed to fix with
> > >  below changes
> > >  -  struct grub_linux_initrd_context initrd_ctx = { 0, };
> > >  +  struct grub_linux_initrd_context initrd_ctx = { 0,NULL,0 };
> > >
> > >  2. grub size issue as below that I am unable to resolve and looking
> > >  for your help. I am building for QEMU and using QEMU version 2.1.2.
> > >
> > >  E: Could not add
> > >  [payloads/external/GRUB2/grub2/build/default_payload.elf, 268862
> > >  bytes (262 KB)@0x0]; too big?
> > >  E: Failed to add
> > >  'payloads/external/GRUB2/grub2/build/default_payload.elf' into ROM
> > >  image.

unable to build coreboot with grub

[Peter Stuge]

Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> > It's in "Chipset Options" -> "Size of CBFS filesystem in ROM" - 0x200000
> > or 0x400000 will work.
>
> This is only for recent intel chipsets.

Why is that option even user visible?

Why is it not at a very minimum behind CONFIG_EXPERT?

//Peter