Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15964] New: Please add an option to use Grub 2.12, or update Grub to 2.12
Date: Fri, 01 Mar 2024 14:16:35 +0000	[thread overview]
Message-ID: <bug-15964-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 15964
           Summary: Please add an option to use Grub 2.12, or update Grub
                    to 2.12
           Product: buildroot
           Version: 2023.11.1
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Outdated package
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: ian_ormshaw@waters.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

Created attachment 9724
  --> https://bugs.busybox.net/attachment.cgi?id=9724&action=edit
Config.in

Due to linitations in Grub 2.06 large rootfs files fail to load due to an out
of memory error.  This error nolonger occurs in Grub 2.12 due to the changes in
memory allocation in version 2.12.  I have tested grub 2.12 on x86_64 via an
external package, see attached files.  There is an issue I have not resolved in
booting a system containing a particulal Ethernet card.  This has been raied
upstream.

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

             reply	other threads:[~2024-03-01 14:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01 14:16 bugzilla [this message]
2024-03-01 14:17 ` [Buildroot] [Bug 15964] Please add an option to use Grub 2.12, or update Grub to 2.12 bugzilla
2024-03-01 14:17 ` bugzilla
2024-03-01 14:21 ` bugzilla
2024-03-01 16:09 ` 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-15964-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