Re: Kernel options not passing in EFI image?

[Andrei Borzenkov]

On Tue, May 24, 2016 at 10:56 AM, Avi Deitcher <address@hidden> wrote:
> Cool! I love that. That really could have saved me a lot of headache.
>
> Can you do that for root as well?

Not sure I understand the question. During initialization GRUB sets
$root to boot device as reported by firmware and it stays this way
unless there is embedded config that changes it. Original boot path is
still available as $cmdpath (on EFI this also includes path to
directory where image was loaded from).

Note that internally GRUB translates EFI reference to ESP on ISO to
whole ISO, so your $root should be set to "cd0" in your example.

> E.g. if I want to boot using a linux
> kernel that is on the iso9660 partition of the disk from which this EFI fat
> was booted, how would I do that?
>
> On Tue, May 24, 2016 at 10:54 AM, Andrei Borzenkov <address@hidden>
> wrote:
>>
>> On Tue, May 24, 2016 at 10:52 AM, Avi Deitcher <address@hidden> wrote:
>> > So if I boot off of a CD, where there is both the (cd0) iso9660
>> > partition
>> > and the (cd0,msdos2) or whatever where the EFI fat32 image is, then ()
>> > gets
>> > translated into (cd0) ?
>> >
>>
>> Correct.
>>
>> > On Tue, May 24, 2016 at 10:46 AM, Andrei Borzenkov <address@hidden>
>> > wrote:
>> >>
>> >> On Tue, May 24, 2016 at 10:43 AM, Avi Deitcher <address@hidden>
>> >> wrote:
>> >> > what does '()' signify?
>> >>
>> >> The (whole) device grub was booted from (as long as this information
>> >> is provided by firmware; it is for BIOS and EFI). '()' is replaced
>> >> during initialization by actual device name referring to boot device.
>> >
>> >
>> >
>> >
>> > --
>> > Avi Deitcher
>> > address@hidden
>> > Follow me http://twitter.com/avideitcher
>> > Read me http://blog.atomicinc.com
>
>
>
>
> --
> Avi Deitcher
> address@hidden
> Follow me http://twitter.com/avideitcher
> Read me http://blog.atomicinc.com