From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11866] New: iniramfs file system fails to boot using Grub on EFI x86_64
Date: Fri, 10 May 2019 21:55:51 +0000 [thread overview]
Message-ID: <bug-11866-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11866
Bug ID: 11866
Summary: iniramfs file system fails to boot using Grub on EFI
x86_64
Product: buildroot
Version: 2019.02.2
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: pmorici at dev295.com
CC: buildroot at uclibc.org
Target Milestone: ---
I'm not 100% sure this is a bug and not my own oversight but I'm unable to
successfully boot the kernel produced by buildroot when the initramfs
filesystem option is selected using Grub on an x86_64 EFI system
To isolate to the bare minimum number of changes I started with
pc_x86_64_efi_defconfig, changed the file system selection from ext2 to
initramfs and modified the post image script to account for the differences.
The result is that after Grub I see only a frozen cursor in the upper left of
an otherwise blank screen.
The config and modified post script needed to reproduce are attached.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-05-10 21:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 21:55 bugzilla at busybox.net [this message]
2019-05-10 22:00 ` [Buildroot] [Bug 11866] iniramfs file system fails to boot using Grub on EFI x86_64 bugzilla at busybox.net
2019-05-11 15:50 ` bugzilla at busybox.net
2019-05-13 13:11 ` bugzilla at busybox.net
2020-03-05 8:02 ` bugzilla at busybox.net
2020-04-24 6:33 ` bugzilla at busybox.net
2020-04-25 1:55 ` bugzilla at busybox.net
2020-04-25 7:40 ` bugzilla at busybox.net
2020-04-25 12:10 ` bugzilla at busybox.net
2020-04-27 5:27 ` bugzilla at busybox.net
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-11866-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.