(as my last message was sent off list, I really need to pay attention to the headers)
The error code is 0x4c10603 and I am loading gPXE via syslinux on a flash drive (for reasons unknown the .usb image isn't liked by the bios) I tried both the single image and the multiple image with the same results and at the moment I can't capture the output from the serial. Thanks > On Wed, Apr 14, 2010 at 3:29 PM, <[email protected]> wrote: >> ---------------------------- Original Message >> ---------------------------- >> Subject: Re: [gPXE] Fails to get an address under gpxe, gets one under >> pxe >> From: [email protected] >> Date: Wed, April 14, 2010 9:14 am >> To: "Thomas Miletich" <[email protected]> >> -------------------------------------------------------------------------- >> >> Hello, >> >> I tried the old driver (0.9.7) and the same results, fails to get an >> address. There is another nic in the machine that gpxe recognizes but >> UNDI >> is broken on it (normal pxe won't work) and same results for that one. > > Hi > thanks for testing. > Can you please specify the error code printed with the timeout > message? I wonder if it's a dhcp timeout or a link-up timeout. > Please also tell us the way you are loading gPXE(i.e. gpxe.dsk, > eepro100.iso, etc). If you are using a multi-driver image(like > gpxe.<type>), please try a single-driver image, like eepro100.dsk. > > If you can capture the output from a serial console, please enable > gPXE's serial console in config/console.h and build gPXE with > debugging options from the eepro100 driver: > > make bin/eepro100.dsk DEBUG=eepro100 > > You can put the output at http://etherboot.pastebin.com > > Thanks > Thomas > >> Thanks >> >> -Trevor Adams >> > > _______________________________________________ gPXE mailing list [email protected] http://etherboot.org/mailman/listinfo/gpxe
