[yocto] [poky] bug #8729 grub bootloader

Dimitris Tassopoulos dimtass at gmail.com
Wed Nov 7 01:18:55 PST 2018


Hi Anuj,

thanks for the reply. First I need to say that it was insightful from your
side to use virtual/grub-bootconf
and this made things much easier. I only had to add `BBCLASSEXTEND =
"native"` in the grub-efi in
order to get `grub-editconf` for the host and create environment files on
the fly.

I had a look in your recommendation and it works after some tweaking. The `
efi-bootdisk.wks.im` file
has an example of this case, as your links suggested. It seems though that
the environment variable
`${IMAGE_ROOTFS}` in the file is not translated correctly during the
bitbake build and it fails with an
error. For example in my case the error was:

Couldn't get bitbake variable from
/rnd/yocto/grub-dev/build/tmp/sysroots/qemux86/imgdata/${IMAGE_ROOTFS}/boot.env.

After I changed the `${ROOTFS}` in `--rootfs-dir=${IMAGE_ROOTFS}/boot` with
the absolute path
then it worked. For me it's nor an issue but it's good for you to know.
Without someone pointing this
out it would be very difficult to discover the above use-case as it's not
clearly documented.

Also, it would be nice when bitbake detects that both `loader=grub-efi` and
`grub-efi_%.bb` are used
to print a warning about this overlapping and suggest the use of
`--rootfs-dir` and `--exclude-path`.

I'll continue from this point now.

Thanks again,
Dimitris

On Wed, Nov 7, 2018 at 1:58 AM Mittal, Anuj <anuj.mittal at intel.com> wrote:

> Hi Dimitris
>
> On Tue, 2018-11-06 at 16:12 +0100, Dimitris Tassopoulos wrote:
> >
> > In this case the bootimg-efi.py script creates the extra partition, a
> > different grub.cfg and also
> > edits the /etc/fstab and mounts this partition over /boot and
> > therefore virtual/grub-bootconf
> > becomes unused.
> >
> > This raises the following questions:
> > - Why there are two different facilities to achieve the same thing?
> > - Why the second overrides the first one, instead of sharing the same
> > files?
> > - How to proceed from now on?
> >
>
> I think this needed --exclude-path in wks to be used to take effect.
> Please see:
>
>
>
> http://lists.openembedded.org/pipermail/openembedded-core/2018-February/147837.html
>
> and bug:
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=10073
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20181107/bf30f7d5/attachment.html>


More information about the yocto mailing list