<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>You are trying to create an ISO image that supports both BIOS and UEFI boot modes, similar to how a CentOS 7 ISO image is able to boot both. This is not possible given how iPXE currently creates it's ISO images. As far as I am aware, the ISOs to not contain relocatable code that can allow for a unified entry point for both platforms. Perhaps I am wrong in this, but I don't see any way to do it currently.</div><div><br></div><span id="zwchr" data-marker="__DIVIDER__">----- On 29 Jan, 2017, at 01:18, Dean Westhead <dean@westhead.net> wrote:<br></span><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>Hi Oliver,<br></div><br><div>Thanks for that info.<br></div><br><div> have already done that part and the BIOS ISO and the EFI ISO works fine and boots and detects what system it is on etc.<br></div><br><div>The problem I have is the part that in that forum that states :<br></div><br><div>"But as far as the iPXE Binary goes, you need to go up one level to the DHCP server"<br></div><br><div>The problem I have is that in our server environment, we dont use DHCP ... everything has a static IP.<br></div><br><div>That is not a problem with iPXE .... I have an embeded script that when the ISO is booted it opens a console and asks the user for the IP, subnet mask, gateway and DNS server. It then uses this<br></div><div>info to open the NIC, connect to the network and chain the menus etc from our central build server.<br></div><br><div>This all works fine if I boot either the BIOS ISO or the EFI ISO and the servers build fine depending on which environment they are booted into.<br></div><br><div>What I am now trying to do is not have two different ISO's .... one for BIOS and one for EFI.<br></div><br><div>I would like to boot one ISO and that ISO will detect and run either the BIOS boot sequence or the EFI sequence. I basically need an ISO that will boot and do the function of the DHCP server by loading the correct iPXE binary for either <br></div><div>BIOS or EFI.<br></div><br><div>This may not be possible but so far I have not found anything that iPXE couldnt do !<br></div><br><div>Thanks.<br></div><br><div>Dean.<br></div><br><br><br><hr id="zwchr"><div><b>From: </b>"Oliver Rath" <oliver@greenunit.de><br><b>To: </b>"ipxe-devel" <ipxe-devel@lists.ipxe.org><br><b>Sent: </b>Sunday, 29 January, 2017 07:12:51<br><b>Subject: </b>[ipxe-devel] Addendum [was Re: Dual BIOS and EFI boot ISO]<br></div><br><div><p>Hi Dean,</p><p>you can also use the <acronym title="Dynamic Host Configuration
Protocol">DHCP</acronym> Client Architecture option (code 93) will indicate the client architecture as specified by <a href="http://tools.ietf.org/html/rfc4578" class="urlextern" title="http://tools.ietf.org/html/rfc4578" target="_blank">RFC 4578</a>, see the NOTES here: <a class="moz-txt-link-freetext" href="http://www.ipxe.org/cfg/platform" target="_blank">http://www.ipxe.org/cfg/platform</a><br></p><p>Hth,</p><p>Oliver<br></p><br><div class="moz-cite-prefix">On 28.01.2017 20:32, Dean Westhead wrote:<br></div><blockquote cite="mid:982611455.43044545.1485631976964.JavaMail.zimbra@westhead.net"><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000;"><div>Hi,</div><br><div>I am able to create an iPXE BIOS bootable iso and a iPXE EFI bootable ISO ... is there a way to create one ISO that will boot on both environments and detect which one needs booting ?</div><br><div>I know that the major linux distributions do this with their build media but is this possible with the iPXE ?</div><br><div>Thanks.</div><br><div>Dean.</div><br></div><br><fieldset class="mimeAttachmentHeader"></fieldset><br><pre>_______________________________________________
ipxe-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ipxe-devel@lists.ipxe.org" target="_blank">ipxe-devel@lists.ipxe.org</a>
<a class="moz-txt-link-freetext" href="https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel" target="_blank">https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</a>
</pre></blockquote><br> <br>_______________________________________________<br>ipxe-devel mailing list<br>ipxe-devel@lists.ipxe.org<br>https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel</div></div><br></div></div><br>_______________________________________________<br>ipxe-devel mailing list<br>ipxe-devel@lists.ipxe.org<br>https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel<br></blockquote></div><br><div data-marker="__SIG_POST__">-- <br></div><div>James A. Peltier<br>IT Services - Research Computing Group<br>Simon Fraser University - Burnaby Campus<br>Phone : 604-365-6432<br>Fax : 778-782-3045<br>E-Mail : jpeltier@sfu.ca<br>Website : http://www.sfu.ca/itservices<br>Twitter : @sfu_rcg<br>Powering Engagement Through Technology</div></div></body></html>