Thanks. A blank prefix parameter fixed the problem. > On the contrary. Now we use the same defaults on all platforms which > simplifies maintaining and packaging. To get old behaviour add > -p "" > to grub-mkimage line
What about this request? Is this feasible? >> I have one more feature request :- >> >> Is it possible to specify which config file should be read by grub >> instead of a hard-coded grub.cfg ? For example :- If I have a <EFI >> SYSTEM PARTITION>/efi/grub2/ folder with grub1.efi grub2.efi grub3.efi >> (each having different set of modules with normal and other basic >> modules included) etc., and I have grub.cfg grub5.cfg grub4.cfg, I >> want grub1.efi to use grub.cfg, grub2.efi to use grub5.cfg and >> grub3.efi to use grub4.cfg (the config file name can be user choice). >> One efi app should not load any other cfg file even if many cfg files >> are present in the prefix folder. >> >> I noticed an option of embedding a config file in grub-mkimage . >> Instead of embedding, I just want the generated image to load a >> different config file with a filename of my choice which can be >> specified as a parameter in grub-mkimage. Is this possible? This can >> also be an option for core.img of grub2 BIOS, but this option is more >> useful for UEFI where multiple grub efi apps can be created. >> >> Finally, just a matter of interest, what non-Apple UEFI (2.x spec, not >> 1.1 spec) systems do you guys use primarily for developing grub2 UEFI? >> Any Intel Motherboard or some UEFI based laptop (HP Elitebook or Sony >> Vaio) or USB based Tianocore EDK or EDK2 DUET (the firmware I use)? >> The only place where the config file name is hardcoded to be "grub.cfg" is (grub2-source)/normal/main.c config = grub_xasprintf ("%s/grub.cfg", prefix); (line 519) Can this be made as a grub-mkimage option instead of hardcoding or even embedding a config file in the generated image. Although it is possible to replace the filename in the mentioned line and compiled, I need something that can be defined while creating the grub2 boot image or the efi app. Regards _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel