[ipxe-devel] Image Load is gone?

Michael Brown mbrown at fensystems.co.uk
Mon Mar 25 22:42:32 UTC 2013

On Monday 25 Mar 2013 22:25:03 Duane Voth wrote:
> The snponly.efi binary runs fine so long as I only imgexec EFI
> applications.  I only get this error when I try to imgexec the ramdisk.efi
> driver found in the efi-toolkit tree on sourceforge.  (
> http://efi-toolkit.svn.sourceforge.net/viewvc/efi-toolkit/trunk/efi-toolkit
> /binaries/em64t/ramdisk.efi?view=log)

That's really surprising; the error number you mention 
(http://ipxe.org/2c04803b) is generated _before_ any code is reached that 
might plausibly care about the difference between loading an EFI driver and 
loading an EFI application.

[To clarify the situation for interested readers: this issue should have 
absolutely nothing to do with the ongoing issue of iPXE-being-a-driver versus 
iPXE-being-an-application.  What we're talking about here is instead the 
ability of iPXE to _load_ a driver, versus the ability of iPXE to load an 

> No rush on getting snponly stable for this specific use, but perhaps you
> have a last-stable-rev number for this functionality?

At the moment, I have no idea how your error is arising in the first place.  
Could you post the exact steps you are taking to reproduce both (a) a working 
imgexec and (b) a failed imgexec?



More information about the ipxe-devel mailing list