All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15191] pc_x86_64_efi_defconfig doesn't run on real hardware
Date: Wed, 03 May 2023 22:26:40 +0000	[thread overview]
Message-ID: <bug-15191-163-dfQkqD2O8b@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15191-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=15191

Sam Bristow <s.bristow@rocketlab.co.nz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Sam Bristow <s.bristow@rocketlab.co.nz> ---
Sorry for the delay in replying. I tested this on a couple of different
machines, an Elkhart Lake Atom board and a random other intel box from around
the office.

I think the issue was that I wasn't getting a framebuffer to display anything
after grub.

Now that the EFI framebuffer is enabled by default the pc_x86_64 config works
out of the box.

(https://git.busybox.net/buildroot/commit/?id=7a4e8355e3751f620ef91239a1c61a9c1c41d5ca)

-- 
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

      parent reply	other threads:[~2023-05-03 22:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20  3:36 [Buildroot] [Bug 15191] New: pc_x86_64_efi_defconfig doesn't run on real hardware bugzilla
2023-01-28 21:10 ` [Buildroot] [Bug 15191] " bugzilla
2023-05-03 22:26 ` bugzilla [this message]

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-dfQkqD2O8b@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 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.