From: David Park <djpark121@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] pc defconfig image does not boot
Date: Mon, 27 Jul 2020 13:10:33 -0700 [thread overview]
Message-ID: <CACef8roF4nq5eu+-jFpxPN01By+sNLtEOmMKNrnVP0nVJ7K_mA@mail.gmail.com> (raw)
In-Reply-To: <871rkxwemd.fsf@dell.be.48ers.dk>
I do not see any build errors whatsoever. I tried increasing the image size
to 1024m but still the same issue.
My machine is a Core i7-4770 with 8GB of RAM. I also tried another machine
even more capable but seeing the same result.
--
On Mon, Jul 27, 2020 at 1:23 AM Peter Korsgaard <peter@korsgaard.com> wrote:
> >>>>> "David" == David Park <djpark121@gmail.com> writes:
>
> > Hi,
> > I created a PC disk.img from the pc_x86_64_efi_defconfig config file
> > following exactly the instructions outlined in board/pc/readme.txt.
>
> > make pc_x86_64_efi_defconfig
>
> > Running this disk.img in qemu boots fine with no issues, but when I
> write
> > the image to a pendrive using the listed commands:
>
> > dd if=output/images/disk.img of=/dev/sdc; sync
>
> > And then insert it into my PC, it doesn't boot all the way. I only see
> the
> > GRUB menu with the Buildroot image listed, but when GRUB tries to run
> this
> > image, I only see "Booting Buildroot", and then nothing else.
>
> If it boots with qemu, then the image is probably fine.
>
> What are the specs of the PC that you are trying to boot it on?
>
> --
> Bye, Peter Korsgaard
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200727/e1e9e487/attachment.html>
next prev parent reply other threads:[~2020-07-27 20:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 5:21 [Buildroot] pc defconfig image does not boot David Park
2020-07-27 6:09 ` Tudor Holton
2020-07-27 8:23 ` Peter Korsgaard
2020-07-27 20:10 ` David Park [this message]
2020-07-27 23:51 ` Tudor Holton
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=CACef8roF4nq5eu+-jFpxPN01By+sNLtEOmMKNrnVP0nVJ7K_mA@mail.gmail.com \
--to=djpark121@gmail.com \
--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.