All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: "not a valid root device" error in UEFI chainloader command
Date: Wed, 18 Jan 2012 13:38:36 +0100	[thread overview]
Message-ID: <4F16BD4C.1050402@gmail.com> (raw)
In-Reply-To: <CAMPnHXy+PatnWdi9SnQX6D_dtMML3Rorx_WJ3y04XPvtywDnCQ@mail.gmail.com>

On 18.01.2012 03:54, Keshav P R wrote:
> Hi,
>       I tried to manually chainload UEFI shell from grub2 terminal in
> x86_64 firmware. I get
>
>> insmod part_gpt
>> insmod fat
>> chainloader (hd0,gpt1)/shellx64.efi
> error: not a valid root device
Setting "root" isn't just for convenience inside GRUB, with some loader 
(multiboot, chainloader, bsd) it's actually passed to the payload as its 
root. If you forget to set it, it obviously won't work
> If I use
>
>> set pager=1
>> set debug=all
>> chainloader (hd0,gpt1)/shellx64.efi
> [long rows of text - but no visible error]
>> boot
> [shell launched]
>
> However a menuentry like
>
> menuentry "UEFI Shell" {
> 	search --fs-uuid --no-floppy --set=root ${_uefi_sys_fs_uuid}
> 	chainloader (${root})/shellx64.efi
> }
>
> works. I can reproduce this error everytime I try to manually
> chainload from grub2 terminal, but does not occur even once when
> loaded via menuentry. Thanks in advance.
>
> Regards.
>
> Keshav
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko



  reply	other threads:[~2012-01-18 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18  2:54 "not a valid root device" error in UEFI chainloader command Keshav P R
2012-01-18 12:38 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-01-18 13:02   ` Keshav P R

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=4F16BD4C.1050402@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.