If trying to use snponly.eif, the following two patches will help: https://git.ipxe.org/vendor/xcat/ipxe.git/commitdiff/73d1ff05b058a2507fda0119825715fa2253d722 and https://git.ipxe.org/vendor/xcat/ipxe.git/commitdiff/f411dcea1ce12ddcdfafa3fa2a89566a16f86bce
I still have been meaning to make snponly.efi work from non chian booted scenarios (e.g. local vfat) but snponly.efi works fine with these two patches. Perhaps one day Michael will have spare time to double check my work, make sure I did it right, probably fudge it a tad, and merge it. In the meantime it's been working swimmingly for me. On Mon, Jul 29, 2013 at 5:20 PM, Niket Kandya <[email protected]> wrote: > > Hi, > > I was trying to chain boot an efi image. > My setup is all like traditional PXE with snponly.efi as the PXE file. > > While chainloading an EFI file, I always fail at last_opened_snpdev() as > it internally tries to find a PCI SNP device which it does not find. Is the > problem here itself ?? > > Or what I understood that this can be the case as this is a software > interface with no PCI address. To fix that I tried installing the protocols > onto a new handle (initially NULL) and then loading the image, however the > image never finds any files to read. So I tried doing this on the > efi_image_handle itself. And this failed again with none of these protocols > even being found on the device handle of the new image. I also tried using > any efi_pci_device, but none is found. > > Any suggestions?? > > Regards > > Thanks and Regards, > Niket Kandya, > > _______________________________________________ > ipxe-devel mailing list > [email protected] > https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel > >
_______________________________________________ ipxe-devel mailing list [email protected] https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
