From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: Naresh Bhat <nareshgbhat@gmail.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: With grub.cfg Linux Kernel boot hangs
Date: Wed, 06 Apr 2011 17:12:25 +0200 [thread overview]
Message-ID: <4D9C82D9.8040305@gmail.com> (raw)
In-Reply-To: <BANLkTimCtxO-8kU-ODxDo4hqX6=o+eYcxA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 675 bytes --]
> Now, My problem is that When I create a menu entry for the above
> manual commands I can see the following message on the screen and
> system will hangs...The menu entry I have created as below
>
Is it latest bzr?
Can you try with debug=relocator and compare the outputs?
> Now my questions are
> 1. Is there any size limitations for Kernel Image which is loaded from
> EFI shell ?
> 2. Is there any size limitations for ramdisk Image which is loaded
> from EFI shell ?
>
GRUB is limited only by memory map and allocations already done by other
subsystems. Linux itself might have further limits.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2011-04-06 15:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 7:38 With grub.cfg Linux Kernel boot hangs Naresh Bhat
2011-04-06 8:15 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-04-06 9:39 ` Naresh Bhat
2011-04-06 12:14 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-04-06 13:54 ` Naresh Bhat
2011-04-06 15:12 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-04-07 11:13 ` Naresh Bhat
2011-04-07 12:01 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-04-07 15:05 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-04-12 10:37 ` Naresh Bhat
2011-04-12 10:57 ` Naresh Bhat
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=4D9C82D9.8040305@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
--cc=nareshgbhat@gmail.com \
/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.