From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15191] New: pc_x86_64_efi_defconfig doesn't run on real hardware
Date: Tue, 20 Dec 2022 03:36:36 +0000 [thread overview]
Message-ID: <bug-15191-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15191
Bug ID: 15191
Summary: pc_x86_64_efi_defconfig doesn't run on real hardware
Product: buildroot
Version: 2022.08.1
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: s.bristow@rocketlab.co.nz
CC: buildroot@uclibc.org
Target Milestone: ---
I have been trying to get a Buildroot image to run on an x86_64 machine but I'm
not having much luck. The generated image boots fine on QEMU but if I try to
run it on real hardware, I just get a blank screen after the GRUB menu.
I have tested running on a couple of different machines with the same result
and have confirmed that I can boot a standard Linux distro on the target
hardware successfully.
# Steps to reproduce
git describe:
2022.08.1-38-b44e2cf19a
make clean && make distclean
make pc_x86_64_efi_defconfig
make -j(nproc)
# Running in QEMU (works)
qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -drive
format=raw,file=output/images/disk.img -m 4096M
# Running on Hardware (doesn't work)
* Flash image to USB stick
* Boot from USB stick
* UEFI works
* GRUB menu displayed
* Select boot option
* Blank screen, no further progress
--
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:[~2022-12-20 3:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 3:36 bugzilla [this message]
2023-01-28 21:10 ` [Buildroot] [Bug 15191] pc_x86_64_efi_defconfig doesn't run on real hardware bugzilla
2023-05-03 22:26 ` 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-15191-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