Just to follow this up in case anybody else finds this thread, after some internal work to allow us to remove the legacy system, we have done exactly as you suggest and had iPXE working well in testing for several weeks now.<div>
<br></div><div>Thanks!</div><div><br></div><div>-Alex<br><div><br></div><div><br><div class="gmail_quote">On Wed, Feb 29, 2012 at 5:03 PM, Gabriel Barazer <span dir="ltr"><<a href="mailto:gabriel@oxeva.fr">gabriel@oxeva.fr</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">I think you can chainload anything from iPXE, including pxelinux or the COM32 menu system from syslinux. have you tried loading the vesamenu.c32 directly from ipxe ?<span class="HOEnZb"><font color="#888888"><div>
<br></div></font></span><div><span class="HOEnZb"><font color="#888888">Gabriel</font></span><div><div class="h5"><br><div><br><div><div>On 29 févr. 2012, at 16:43, Alex Davies wrote:</div><br><blockquote type="cite"><p>
That replicates my problem exactly, but I can't remove the first step :(</p>
<p>Thanks for confirming, does anyone have an idea of a fix?</p><p>Is it possible to configure iPXE to show a menu, one option of which is to load pxelinux from iPXE?</p><p>Thanks,</p><p>Alex</p><p>Sent from a mobile device</p>
<div class="gmail_quote">On Feb 29, 2012 3:39 PM, "Gabriel Barazer" <<a href="mailto:gabriel@oxeva.fr" target="_blank">gabriel@oxeva.fr</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Alex,<br>
<br>
We were seeing the exact same problem in our setup which was to boot pxelinux from the original PXE stack, then chain load iPXE from the PXElinux stack. We managed to solve the problem by removing the PXElinux step and directly booting to iPXE.<br>
<br>
We are also using recent Dell servers with the same PXE boot agent.<br>
<br>
Gabriel<br>
<br>
On 29 févr. 2012, at 16:34, Alex Davies wrote:<br>
<br>
> Hi,<br>
><br>
> There was a message last summer (below) to this list discussing an<br>
> error using undionly.kpxe with recent Broadcom cards, starting<br>
> Broadcom NetXtreme Ethernet Boot Agent v6.0.11. I see exactly these<br>
> symptoms with pretty much all of my recent-ish Dell servers.<br>
><br>
> Does anybody have any suggestions on how best to fix / get around this?<br>
><br>
> Thanks,<br>
><br>
> Alex<br>
><br>
> --<br>
><br>
> From: John Julien [mailto:<a href="mailto:john" target="_blank">john</a> at <a href="http://julienfamily.com/" target="_blank">julienfamily.com</a>]<br>
> Sent: Thursday, July 28, 2011 5:43 PM<br>
> To: ipxe-devel at <a href="http://lists.ipxe.org/" target="_blank">lists.ipxe.org</a><br>
> Subject: UNDI Memory Error<br>
><br>
><br>
><br>
> Hi,<br>
><br>
> I've come across an issue using the UNDI driver of the Broadcom 5709C card.<br>
> I've been using the UDNI driver with no problems until recently I started<br>
> getting the message "Try to free Memory without Signature" Utilizing<br>
> different hardware vendors and through many trial and error tests I believe<br>
> I've narrowed the issue down to something that was introduced in the<br>
> Broadcom NetXtreme Ethernet Boot Agent v6.0.11 .<br>
><br>
><br>
><br>
> Here is a copy of my console with some extra debug output from iPXE. You<br>
> can ignore the "Getting ready to load into memory" message. That's<br>
> something I added to the source to try and track down the exact line of code<br>
> the failure was occurring at which I found to be line 00097 of<br>
> arch/i386/drivers/net/undirom.c <<a href="http://dox.ipxe.org/undirom_8c.html" target="_blank">http://dox.ipxe.org/undirom_8c.html</a>><br>
> <<a href="http://dox.ipxe.org/undirom_8c_source.html" target="_blank">http://dox.ipxe.org/undirom_8c_source.html</a>> [code]<br>
><br>
><br>
><br>
> 00097 /* Call loader */<br>
><br>
> 00098 undi_loader_entry = undirom->loader_entry;<br>
><br>
> 00099 __asm__ __volatile__ ( REAL_CODE ( "pushw %%ds\n\t"<br>
><br>
> 00100 "pushw %%ax\n\t"<br>
><br>
> 00101 "lcall<br>
> *undi_loader_entry\n\t"<br>
><br>
> 00102 "addw $4, %%sp\n\t" )<br>
><br>
> 00103 : "=a" ( exit )<br>
><br>
> 00104 : "a" ( __from_data16 ( &undi_loader )<br>
> )<br>
><br>
> 00105 : "ebx", "ecx", "edx", "esi", "edi",<br>
> "ebp" );<br>
><br>
><br>
><br>
><br>
><br>
> Error Image: <a href="http://home.comcast.net/~john.julien/ipxe/ipxe_error.gif" target="_blank">http://home.comcast.net/~john.julien/ipxe/ipxe_error.gif</a><br>
><br>
><br>
><br>
><br>
><br>
> Does anyone have any idea what might be causing this or how I might narrow<br>
> it down any further?<br>
><br>
><br>
><br>
> Thanks,<br>
><br>
> John<br>
> _______________________________________________<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/ipxe-devel" target="_blank">https://lists.ipxe.org/mailman/listinfo/ipxe-devel</a><br>
<br>
</blockquote></div>
</blockquote></div><br></div></div></div></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Alex Davies<br><br><span style="font-size:x-small">This email and any files transmitted with it are confidential and<br>
intended solely for the use of the individual or entity to whom they<br>are addressed. If you have received this email in error please notify<br>the sender immediately by e-mail and delete this e-mail permanently.</span><br>
</div></div>