From: Peter Seiderer <ps.report@gmx.net>
To: "Walter, Stefan" <stefan.walter@iml.fraunhofer.de>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] Boot process stuck at "GRUB loading.." since 2021.02.1
Date: Tue, 19 Oct 2021 23:02:52 +0200 [thread overview]
Message-ID: <20211019230252.324bbb61@gmx.net> (raw)
In-Reply-To: <AM0P194MB0706FB2963323BD5D657815EB7BD9@AM0P194MB0706.EURP194.PROD.OUTLOOK.COM>
Hello Stefan,
On Tue, 19 Oct 2021 15:17:23 +0000, "Walter, Stefan" <stefan.walter@iml.fraunhofer.de> wrote:
> Hi Peter,
>
> > Can you try instead of your original
> >
> > /path/to/buildroot-sdk/host/bin/grub-mkimage \
> > --config=grub_early.cfg \
> > --directory=/path/to/buildroot-sdk/host/lib/grub/i386-pc \
> > -o ./genimage_input_tmp/grub_core.img \
> > --format=i386-pc \
> > --prefix==/boot/grub \
> > biosdisk part_msdos ext2 normal linux configfile
> >
> > the following one (makes the difference here for me with the qemu test):
> >
> > /path/to/buildroot-sdk/host/bin/grub-mkimage \
> > --config=grub_early.cfg \
> > --directory=/path/to/buildroot-sdk/build/grub2-2.04/build-i386-
> > pc/grub-core \
> > -o ./genimage_input_tmp/grub_core.img \
> > --format=i386-pc \
> > --prefix==/boot/grub \
> > biosdisk part_msdos ext2 normal linux configfile
> >
> > Note the --directory change from the '.../host/lib/grub/i386-pc' (installed)
> > directory to '.../build/grub2-2.04/build-i386-pc/grub-core' build directory (as
> > the original buildroot
> > grub2 install step uses to create images/grub.img...
>
> there is no directory build/grub2-2.04/build-i386-pc, but there is a build/grub2.204/grub-core, which I assume you meant.
Yes, your are right...
> I tried with that directory, and indeed, the resulting image boots.
Thanks for testing (and for providing your command lines from your build)...
The host-grub2 modules build can be fixed by the following patch:
--- a/boot/grub2/grub2.mk
+++ b/boot/grub2/grub2.mk
@@ -125,7 +125,9 @@ GRUB2_TUPLES-$(BR2_TARGET_GRUB2_ARM64_EFI) += arm64-efi
# use the cross compile variant to ensure grub2 builds
HOST_GRUB2_CONF_ENV = \
- CPP="$(HOSTCC) -E"
+ CPP="$(HOSTCC) -E" \
+ CFLAGS="$(HOST_CFLAGS) -Os" \
+ CPPFLAGS="$(HOST_CPPFLAGS) -Os"
GRUB2_CONF_ENV = \
CPP="$(TARGET_CC) -E" \
Regards,
Peter
>
> Thank you for your help so far! I'll reference this in the issue at https://bugs.busybox.net/show_bug.cgi?id=14281.
>
> Best regards,
> Stefan
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-10-19 21:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 20:36 [Buildroot] Boot process stuck at "GRUB loading.." since 2021.02.1 Walter, Stefan
2021-10-07 21:50 ` Peter Seiderer
2021-10-08 14:27 ` Walter, Stefan
2021-10-08 17:25 ` Peter Seiderer
2021-10-11 12:23 ` Walter, Stefan
2021-10-11 17:29 ` Walter, Stefan
2021-10-18 22:22 ` Peter Seiderer
2021-10-19 15:17 ` Walter, Stefan
2021-10-19 21:02 ` Peter Seiderer [this message]
2021-10-21 17:59 ` Yann E. MORIN
2021-10-22 9:48 ` Köry Maincent
2021-10-22 17:42 ` Peter Seiderer
2021-10-08 16:53 ` Alexander Dahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211019230252.324bbb61@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@buildroot.org \
--cc=stefan.walter@iml.fraunhofer.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox