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 ?
Gabriel On 29 févr. 2012, at 16:43, Alex Davies wrote: > That replicates my problem exactly, but I can't remove the first step :( > > Thanks for confirming, does anyone have an idea of a fix? > > Is it possible to configure iPXE to show a menu, one option of which is to > load pxelinux from iPXE? > > Thanks, > > Alex > > Sent from a mobile device > > On Feb 29, 2012 3:39 PM, "Gabriel Barazer" <[email protected]> wrote: > Hi Alex, > > 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. > > We are also using recent Dell servers with the same PXE boot agent. > > Gabriel > > On 29 févr. 2012, at 16:34, Alex Davies wrote: > > > Hi, > > > > There was a message last summer (below) to this list discussing an > > error using undionly.kpxe with recent Broadcom cards, starting > > Broadcom NetXtreme Ethernet Boot Agent v6.0.11. I see exactly these > > symptoms with pretty much all of my recent-ish Dell servers. > > > > Does anybody have any suggestions on how best to fix / get around this? > > > > Thanks, > > > > Alex > > > > -- > > > > From: John Julien [mailto:john at julienfamily.com] > > Sent: Thursday, July 28, 2011 5:43 PM > > To: ipxe-devel at lists.ipxe.org > > Subject: UNDI Memory Error > > > > > > > > Hi, > > > > I've come across an issue using the UNDI driver of the Broadcom 5709C card. > > I've been using the UDNI driver with no problems until recently I started > > getting the message "Try to free Memory without Signature" Utilizing > > different hardware vendors and through many trial and error tests I believe > > I've narrowed the issue down to something that was introduced in the > > Broadcom NetXtreme Ethernet Boot Agent v6.0.11 . > > > > > > > > Here is a copy of my console with some extra debug output from iPXE. You > > can ignore the "Getting ready to load into memory" message. That's > > something I added to the source to try and track down the exact line of code > > the failure was occurring at which I found to be line 00097 of > > arch/i386/drivers/net/undirom.c <http://dox.ipxe.org/undirom_8c.html> > > <http://dox.ipxe.org/undirom_8c_source.html> [code] > > > > > > > > 00097 /* Call loader */ > > > > 00098 undi_loader_entry = undirom->loader_entry; > > > > 00099 __asm__ __volatile__ ( REAL_CODE ( "pushw %%ds\n\t" > > > > 00100 "pushw %%ax\n\t" > > > > 00101 "lcall > > *undi_loader_entry\n\t" > > > > 00102 "addw $4, %%sp\n\t" ) > > > > 00103 : "=a" ( exit ) > > > > 00104 : "a" ( __from_data16 ( &undi_loader ) > > ) > > > > 00105 : "ebx", "ecx", "edx", "esi", "edi", > > "ebp" ); > > > > > > > > > > > > Error Image: http://home.comcast.net/~john.julien/ipxe/ipxe_error.gif > > > > > > > > > > > > Does anyone have any idea what might be causing this or how I might narrow > > it down any further? > > > > > > > > Thanks, > > > > John > > _______________________________________________ > > ipxe-devel mailing list > > [email protected] > > https://lists.ipxe.org/mailman/listinfo/ipxe-devel >
_______________________________________________ ipxe-devel mailing list [email protected] https://lists.ipxe.org/mailman/listinfo/ipxe-devel
