patient pxe people, after months of usage -- pretty much as described here http://etherboot.org/wiki/httpboot -- we were recently pushed out of our comfort zone (read as "gpxe times out at dhcp net0 on new hardware HP ProLiant BL460c G6 Server) and have thus been pests on IRC.
to sum up our new points of confusion: 1) if we're chaining, as described here, http://etherboot.org/wiki/pxechaining, and not burning gPXE ROMs for NICs, are we always using the UNDI driver ? 2) we're building an embedded gpxe script into our image much like what is available in syslinux gpxe sources. make -C src bin/undionly.kkpxe NO_WERROR=1 EMBEDDED_IMAGE=../ pxelinux.gpxe,../../core/pxelinux.0 where pxelinux.gpxe is our #!gpxe script and core/pxelinux.0 is the syslinux image kkpxe is good as we'd like to have iSCSI keep-san 1 for some installs that don't provide native support in the OS the question here is are we undionly or is it trying to use native drivers when the result of this build is served to the PXEBOOT client. thank you for your help and patience. d. _______________________________________________ gPXE mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe
