I am using a modified version of gPXE that allows >256 characters to be passed to the kernel command line. gPXE needs to pass a very long string of arguments to the kernel command line. I am chain-loading gPXE from PXE. DHCP is configured to look for the gpxe.bus-id in the dhcpd.conf file to break out of the infinite loop.
The new Qlogic NICs are coming with gPXE. This poses a problem because it doesn't load the custom gPXE (w/Kernel CmdLine patch) because DHCP sees that the gpxe.bus-id is already defined so it doesn't hand-out the custom gPXE like it does for NICs that PXE boot. Is there a known solution for loading a custom (patched) gPXE from gPXE (native) without falling into an infinite loop? Can an attribute be set to tell dhcp to always offer the custom bootloader unless the attribute defined in the custom gPXE version is present? Thanks, Steve _______________________________________________ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
