Hello It sounds like there's something going wrong in pcnet32_probe(). Please build a gPXE image with debugging for the pcnet32 driver and serial console support enabled. To enable the serial console, edit 'src/config/console.h' and remove the '//' in front of '//#define CONSOLE_SERIAL', thus making the line '#define CONSOLE_SERIAL'. Then build gPXE with the following line:
make bin/pcnet32.dsk DEBUG=pcnet32 (adjust 'bin/pcnet32.dsk' according to your needs). In virtualbox you can configure a serial port that redirects the output to a file. Please let us know the contents of said file. This should give us an idea where the driver gets stuck. -- Thanks for reporting Thomas On Wed, Jul 28, 2010 at 12:22 PM, Gilles Martin <gilles.mar...@psi.ch> wrote: > Hi, > > Now that I have recover my gpxe script thanks to Josh, I can test the > latest version of GPXE... > > My test environment is like that: > > * Virtualbox 3.2.6 with ethernet adapter PCNET-Fast III (Am79C973) > * First PXE boot to a classical PXE server > * Then load a GPXE lkrn image made at the Rom-o-matic website. > > This is working well with GPXE-1.0.0 with all drivers or only PCNET32 > driver. > > This is not working with GPXE-1.0.1: > > With all drivers it get stuck just after "GPXE initializing devices..." > With only PCNET32, it doesn't detect the interface with "ifopen net0". > > > Thanks for your help. > > Gilles > > _______________________________________________ > gPXE mailing list > gPXE@etherboot.org > http://etherboot.org/mailman/listinfo/gpxe > _______________________________________________ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
