Re: Kernel options not passing in EFI image?

[Avi Deitcher]

OK, will do it right now.

Interesting note: why does mkrescue have --prefix='()/boot/grub' as an
option to mkimage? I get that rather than loading all of the modules into
the grub binary, it puts them on the iso9660 filesystem and then accesses
them that way, but what does '()' signify? That isn't any one known disk
like (memdisk) or (cd0) or (hd0) etc.

On Tue, May 24, 2016 at 10:40 AM, Andrei Borzenkov <address@hidden>
wrote:

> On Tue, May 24, 2016 at 10:12 AM, Avi Deitcher <address@hidden> wrote:
> > Confirm that grub-mkrescue *does* pass the cmdline options along. Which
> > almost definitely means my mkimage build is slightly (but critically)
> > different than what mkrescue does.
> >
> > I ran mkrescue -v, the mkimage line was:
> >
> > grub-mkimage --directory '/usr/lib/grub/x86_64-efi' --prefix
> '()/boot/grub'
> > --output 'somefile.efi' --format 'x86_64-efi' --compression 'auto'
> --config
> > '/tmp/grub.9g6zmZ' 'part_msdos' 'fat' 'iso9660'
> >
> > Much simpler command line, yet it works?
> >
>
> mkerscue makes *full* grub available in ISO, so everything that it
> needs at boot time is autoloaded from image. Image itself only needs
> just enough to access ISO after initial boot.
>
> It would be interesting to find out what is missing in your case. You
> could start with booting rescue into CLI, issuing the same "linux" and
> "initrd" commands and comparing the list of modules (lsmod). Use "set
> pager=1" as module list is likely longer than normal screen.
>



-- 
Avi Deitcher
address@hidden
Follow me http://twitter.com/avideitcher
Read me http://blog.atomicinc.com