<div dir="ltr">Hi,<div><br></div><div>I was wondering if any of you guys ran into/worked around this problem.</div><div><br></div><div>Following my previous query about UEFI image execution,</div><div>I enabled snponly.efi image execution, partly from Jarrod's patch and partly my own.</div>
<div><br></div><div>My addition there was:</div><div>If you try to run 2 efi images 1 after the other, the second image wont execute because protocol installation will fail on the device handle as protocols are already installed. So I added a check before installation in efi_image_exec in efi_file_install and efi_download_install. And similarly to uninstall only when it was installed for that image.</div>
<div><br></div><div>To simulate this easily, you can just try autoboot from the shell as the first command and then after you have reached the shell AGAIN!, chain your normal efi image.</div><div><br></div><div>However I ran into a wierd issue, after the autoboot, when i try to load an efi image, the cwuri is changed to the one from previous autoboot.</div>
<div><br></div><div class="gmail_extra"><br clear="all"><div>Thanks and Regards,<br>Niket Kandya,<br>Graduate Student CS,<br>Columbia University, NY</div>
<br><br><div class="gmail_quote">On Wed, Aug 7, 2013 at 5:36 PM, Jarrod Johnson <span dir="ltr"><<a href="mailto:jarrod.b.johnson@gmail.com" target="_blank">jarrod.b.johnson@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><div><div>If trying to use snponly.eif, the following two patches will help:<br><a href="https://git.ipxe.org/vendor/xcat/ipxe.git/commitdiff/73d1ff05b058a2507fda0119825715fa2253d722" target="_blank">https://git.ipxe.org/vendor/xcat/ipxe.git/commitdiff/73d1ff05b058a2507fda0119825715fa2253d722</a><br>
</div>and<br><a href="https://git.ipxe.org/vendor/xcat/ipxe.git/commitdiff/f411dcea1ce12ddcdfafa3fa2a89566a16f86bce" target="_blank">https://git.ipxe.org/vendor/xcat/ipxe.git/commitdiff/f411dcea1ce12ddcdfafa3fa2a89566a16f86bce</a><br>
<br>
</div>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.<br><br></div>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.<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote"><div>On Mon, Jul 29, 2013 at 5:20 PM, Niket Kandya <span dir="ltr"><<a href="mailto:niketkandya@gmail.com" target="_blank">niketkandya@gmail.com</a>></span> wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><span style="background-color:rgb(0,0,0)"><br></span></div><div><span><font color="#000000"><span style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px">Hi,</span><br style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px">
<br style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px"><span style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px">I was trying to chain boot an efi image.</span><br style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px">
<span style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px">My setup is all like traditional PXE with snponly.efi as the PXE file.</span><br style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px">
<br style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px"><span style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px">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 ??</span><br style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px">
<br style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px"><span style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px">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.</span><br style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px">
<br style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px"><span style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px">Any suggestions??</span><br style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px">
<br style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px"><span style="font-family:Verdana,Arial,sans-serif;font-size:13px;line-height:18px">Regards</span><br></font></span></div><br clear="all"><div>
Thanks and Regards,<br>Niket Kandya,<br></div>
</div>
<br></div></div><div>_______________________________________________<br>
ipxe-devel mailing list<br>
<a href="mailto:ipxe-devel@lists.ipxe.org" target="_blank">ipxe-devel@lists.ipxe.org</a><br>
<a href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a><br>
<br></div></blockquote></div><br></div>
</blockquote></div><br></div></div>