From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: GRUB2 for UEFI crashes at startup when we got 8 gigabyte of memory
Date: Wed, 21 Apr 2010 11:40:10 +0200 [thread overview]
Message-ID: <4BCEC7FA.3050003@gmail.com> (raw)
In-Reply-To: <p2uca0f59981004210212z9e2cc07cx3ea1c9c64f49d9cf@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
Bean wrote:
> On Wed, Apr 21, 2010 at 3:53 PM, <gburanov@gmail.com> wrote:
>
>> In Febryary I was testing GRUB for UEFI and noticed that it was simply crashing.
>>
>> See topic
>> http://lists.gnu.org/archive/html/grub-devel/2010-02/msg00000.html
>>
>> At that time I blamed incorrect UEFI implementation on that computer (cause it worked fine on another one), but now I noticed that when I took off one memory stick, everything is working fine on that special computer!!!!
>>
>> So, it seems that GRUB2 is crashing on computers with 8 gb of memory (or more?)
>>
>> Is it known bug? Are there workarounds?
>>
>
> Hi,
>
> You could try BURG and see if it has the same problem, binary package
> for EFI is available for download at:
>
>
As I already told you before the bugs which are reported for GRUB2 must
be fixed in GRUB2, not in any kind of fork. Moreover any discussion of
BURG is off-topic here. And advertisement of it is not unlike spam.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next prev parent reply other threads:[~2010-04-21 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 7:53 GRUB2 for UEFI crashes at startup when we got 8 gigabyte of memory gburanov
2010-04-21 8:31 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-21 12:06 ` gburanov
2010-04-21 18:58 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-21 8:34 ` Seth Goldberg
2010-04-21 9:12 ` Bean
2010-04-21 9:40 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-01-04 12:59 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4BCEC7FA.3050003@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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.