Neurognostic

If you can test it, I'd appreciate it. It works! I tested with both GNU-EFI and Tianocore EDK2 libraries. I created a manual boot stanza with no options parameters and the system booted exactly as expected. /proc/cmdline only contains the kernel parameters that were embeded in the image. Only thing I can think of that would make this behave even better, from a user-experience perspective, is what I said in the comment about extracting the .cmdline vma-section in the stub binary. But if the overhead...

If you can test it, I'd appreciate it. It works! I tested wirh both GNU-EFI and Tianocore EDK2 libraries. I created a manual boot stanza with no options parameters and the system booted exactly as expected. /proc/cmdline only contains the kernel parameters that were embeded in the image. Only thing I can think of that would make this behave even better, from a user-experience perspective, is what I said in the comment about extracting the .cmdline vma-section in the stub binary. But if the overhead...

If you can test it, I'd appreciate it. It works! I tested both GNU-EFI and with Tianocore EDK2 libraries. I created a manual boot stanza with no options parameters and the system booted exactly as expected. /proc/cmdline only contains the kernel parameters that were embeded in the image. Only thing I can think of that would make this behave even better, from a user-experience perspective, is what I said in the comment about extracting the .cmdline vma-section in the stub binary. But if the overhead...

If you can test it, I'd appreciate it. It works! I tested both GNU-EFI and with Tianocore EDK2 libraries. I created a manual boot stanza with no options parameters and the system booted exactly as expected. /proc/cmdline only contains the kernel parameters that were embeded in the image. Only thing I can think of that would make this behave even better, from a user-experience perspective, is what I said in the comment about extracting the .cmdline vma-section in the stub binary. But if the overhead...

It occured to me that the defult kernel parameters could be extracted from the EFISTUB by checking the .cmdline vma section. This could allow easier editing of the kernel parameters from within rEFInd at boot time. Otherwise, with no kernel parameters defined, when editing a boot option the user would need to type the entire parameter list in addition to any they are appending.

The question, really, is: Should an EFI program that launches another program necessarily include the follow-on program's filename as a first command-line parameter? Something of note worthy is that the EFI program's name is not included as a parameter when the firmware's boot manager launches the program directly; atleast that is the case with the EFISTUB Linux kernel. What do you mean by "GPY?" I mean the GPT GUID Partition Code is correctly configured for my system. The GUID partition code for...

EDIT: Never mind

The question, really, is: Should an EFI program that launches another program necessarily include the follow-on program's filename as a first command-line parameter? Something of note worthy is that the EFI program's name is not included as a parameter when the firmware's boot manager launches the program directly; atleast with the EFISTUB Linux kernel. What do you mean by "GPY?" I mean the GPT GUID Partition Code is correctly configured for my system. The GUID partition code for the partition my...