[ipxe-devel] ipxe.lkrn chainloaded from pxelinux 4.03 does not work anymore

Gene Cumm gene.cumm at gmail.com
Mon Nov 11 10:58:17 UTC 2013

On Mon, Nov 11, 2013 at 2:18 AM, Anton D. Kachalov <mouse at yandex-team.ru> wrote:
> I have the same problem on pxelinux 4.x while 3.86 works. Looks like
> something has been changed in pxelinux that is incompatible with iPXE (at
> least UNDI-version).
> http://www.syslinux.org/wiki/index.php/Common_Problems#PXE_Calls_in_4.00-4.03

Not quite.  Thomas is loading a "Linux kernel"-like file.  He's not
affected by this bug.

As I noted in that Wiki section, you're only affected by that bug when
you use a PXE call that effectively unloads PXELINUX.  pxechain.com is
an example.  It calls the PXE API to restart with a new file.  Using
sanboot.c32 would also do so (assuming iPXE/gPXE is underneath to
catch that call).


> 11.11.2013, 00:30, "Robin Smidsrød" <robin at smidsrod.no>:
> On 08.11.2013 21:27, Thomas Mieslinger wrote:
>  I have an older ipxe.lkrn which identifies itself as version "9361". It
>  just works when loaded from pxelinux 4.03.
>  I now compiled a new one with the last commit
>  "c3d1e7869731c8cccb041ce05ee0ebbb3dc375d5". When it is chain loaded from
>  pxelinux 4.03 a short message "Initializing Devices ..." is displayed
>  and then Server (Dell PowerEdge R320) resets.
>  Can you give me a hint how I reset my local git to "9361".
> git checkout 9361 (hopefully that is enough of the commit id)
>  Which Debug options should I set when I compile the current ipxe src to
>  debug the "Initializing Devices ..."?
> You should really try to do a git bisect to figure out which is the
> commit that broke your build. Details on how to do that is on
> http://ipxe.org/howto/bisect
> Also, to figure out which driver you use, you need to run "ifstat" and
> take note of the driver name mentioned.
> -- Robin

More information about the ipxe-devel mailing list