From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14281] New: Boot process stuck at "GRUB loading.." since 2021.02.1
Date: Mon, 18 Oct 2021 12:08:58 +0000 [thread overview]
Message-ID: <bug-14281-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14281
Bug ID: 14281
Summary: Boot process stuck at "GRUB loading.." since 2021.02.1
Product: buildroot
Version: 2021.02.5
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: stefan.walter@iml.fraunhofer.de
CC: buildroot@uclibc.org
Target Milestone: ---
The following used to work until including Buildroot 2021.02, i.e. the
resulting image used to boot normally. Ever since Buildroot 2021.02.1, the
resulting image does not boot any more - the boot process either gets stuck
right after displaying "GRUB loading..", or it reboots at that point, leading
to an infinite boot loop. More specifically, this problem exists since the
following commit:
e840f2d469 boot/grub2: Backport 2021/03/02 securify fixes
Here's what I'm doing:
1. Run Buildroot to create a root partition image (my_defconfig attached).
2. Create a GRUB image like this (grub_early.cfg attached):
/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
3. Create a home partition image like this:
MKE2FS_CONFIG=/path/to/buildroot-sdk/host/etc/mke2fs.conf
/path/to/buildroot-sdk/host/sbin/mke2fs -d home_partition_prep/home -j -L home
-t ext3 -U random -b 4096 ./genimage_input_tmp/home.ext3 25M
4. Create a disk image like this (genimage.cfg attached):
/path/to/buildroot-sdk/host/bin/genimage --loglevel=1 --config=genimage.cfg
--inputpath=./genimage_input_tmp --outputpath=images
--rootpath=home_partition_prep --tmppath=./genimage_tmp
--tune2fs=/path/to/buildroot-sdk/host/usr/sbin/tune2fs
--e2fsck=/path/to/buildroot-sdk/host/usr/sbin/e2fsck
(Note that I had also previously raised this issue on the Buildroot mailing
list - see
http://lists.busybox.net/pipermail/buildroot/2021-October/625323.html.)
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2021-10-18 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 12:08 bugzilla [this message]
2021-10-18 12:12 ` [Buildroot] [Bug 14281] Boot process stuck at "GRUB loading.." since 2021.02.1 bugzilla
2021-10-18 12:12 ` bugzilla
2021-10-18 12:12 ` bugzilla
2021-10-18 18:47 ` bugzilla
2021-10-19 15:31 ` bugzilla
2021-10-20 13:04 ` bugzilla
2021-10-20 13:05 ` bugzilla
2024-06-15 15:00 ` bugzilla
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=bug-14281-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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