(2012-03-15 02:12)jpwise Wrote:  How often is the undionly.kpxe on boot.ipxe.org updated?

Is it done on a regular basis as the source is updated, or manually at set intervals? If it's done automatically I'd like to schedule once a week cron downloads to update the local pxeboot server without the need to manually recompile it.

(2012-03-29 23:29)jpwise Wrote:  Afternoon, I set up an auto update on a weekly basis, which just updated at 3am this morning (approx 8 hours ago) and looks like the current undionly.kpxe that's on the site may be buggy.

Our implementation is tftp for the undionly.kpxe, followed by http loading the menu.ipxe file, finally chaining vesamenu.c32 to a menu file.
With the latest undionly.kpxe it gets as far as downloading the vesamenu.c32 file, reports ok, and then just hangs. If i revert to the previous undionly.kpxe file it runs fine.

I've just re-downloaded the current file as you indicated it was an hourly build, but the latest is no change. Filesize also appears to have dropped from 62373 to 61419kb.

(2012-03-30 08:34)mcb30 Wrote:  COMBOOT image support is no longer enabled by default, since we now have the ability to implement native iPXE menus:

http://git.ipxe.org/ipxe.git/commitdiff/cf0953a
http://ipxe.org/cmd/choose

Michael

(2012-04-01 11:20)jpwise Wrote:  

(2012-03-30 08:34)mcb30 Wrote:  COMBOOT image support is no longer enabled by default, since we now have the ability to implement native iPXE menus:

http://git.ipxe.org/ipxe.git/commitdiff/cf0953a
http://ipxe.org/cmd/choose

Ah, that would definitely explain it. Our system is built around the comboot vesamenus, so we'll move back to compiles.

Is there a recommended method to re-enable it during config/compilation, or is it a case of editing the pcbios.h file to re-add the define?