<div dir="ltr">Ok, don't know if someone could clarify, but it *looks* like it requires that a candidate device be put into efi_pci_devices list, but I don't see the relevant function being called when running as snponly, meaning no 'pci' devices are listed at all, nothing is considered to be snp, etc etc...<br>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 10, 2013 at 1:33 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">So prior to the commit, snponly latched onto the device as provided from loaded image. The switch to last_opened_snpdev() seems to not be working.....<br>
</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, Apr 10, 2013 at 1:21 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">This was working for me, but broke as of <br>fc87adb commit... If I back that one out, chain loading efi images from snponly.efi works again...<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
<div><div>
On Tue, Apr 9, 2013 at 11:42 AM, James A. Peltier <span dir="ltr"><<a href="mailto:jpeltier@sfu.ca" target="_blank">jpeltier@sfu.ca</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div>
<div><div style="font-size:12pt;font-family:times new roman,new york,times,serif"><hr><div><div><blockquote style="padding-left:5px;font-size:12pt;font-style:normal;margin-left:5px;font-family:Helvetica,Arial,sans-serif;text-decoration:none;font-weight:normal;border-left:2px solid rgb(16,16,255)">
<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2013/4/6 Michael Brown <span dir="ltr"><<a href="mailto:mbrown@fensystems.co.uk" target="_blank">mbrown@fensystems.co.uk</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
This will give you an iPXE EFI ROM; you'll see it show up as "EFI Network" in the EFI boot device selection screen, and it should thereafter look and feel similar to normal iPXE.<br>
<br>
There is no such thing as a non-EFI (aka BIOS or "legacy") ROM which is capable of loading an EFI image. Such a thing simply does not and can not exist.<br>
<span><font color="#888888"><br>
Michael<br>
</font></span></blockquote></div><br></div><div class="gmail_extra">I didn't know this. Up to know I've been using a modified version of ipxe that gives me a shell after initilizing the devices (just a modified main() function), so that I can load and boot any image over a network. I've always had all image types enabled in general.h and never had an issues when starting ipxe. Right now my system just reboots regardless of the not supported IMAGE_EFI. From my point of view this is a regression, because befor this commit ipxe started without glitches regardless if an image is supported or not. So even if the image is not supported then ipxe should gracefully continue initilization and not reboot the mashine....<br>
<br><br></div><div class="gmail_extra">From the shell I can point to and download any efi image over the network, but why it cannot boot the system?<br></div><div class="gmail_extra"><br>Joshua
</div></div></blockquote><br></div></div>I have iPXE working with both legacy BIOS and EFI machines right now, except that I can't get it to chainload to an EFI bootloader such as CentOS's BOOTX64.efi. I always end up with "Could not boot: No such device", although considering this is my first time trying to do this I'm probably not doing it right. I'm just trying with<br>
<br> chain <a href="http://mirror.its.sfu.ca/mirror/CentOS/6/os/x86_64/EFI/BOOT/BOOTX64.efi" target="_blank">http://mirror.its.sfu.ca/mirror/CentOS/6/os/x86_64/EFI/BOOT/BOOTX64.efi</a><br><br>which is probably not right. Any ideas?<span><font color="#888888"><br>
-- <br><div><span name="x"></span>James A. Peltier<br>Manager, IT Services - Research Computing Group<br>Simon Fraser University - Burnaby Campus<br>Phone : <a href="tel:778-782-6573" value="+17787826573" target="_blank">778-782-6573</a><br>
Fax : <a href="tel:778-782-3045" value="+17787823045" target="_blank">778-782-3045</a><br>E-Mail : <a href="mailto:jpeltier@sfu.ca" target="_blank">jpeltier@sfu.ca</a><br>Website : <a href="http://www.sfu.ca/itservices" target="_blank">http://www.sfu.ca/itservices</a><br>
<br>“A successful person is one who can lay a solid foundation from the bricks others have thrown at them.” -David Brinkley via Luke Shaw<span name="x"></span><br></div></font></span></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></div></blockquote></div><br></div>