Is this within QEmu? If so, there was once a "double-slash problem" with QEmu's built-in TFTP service, which might be affecting you. Please see:
http://etherboot.org/wiki/qemu#quick_start If that does not apply to your scenario, have you checked your TFTP service logs to ensure that the TFTP request for 'pxelinux.0' is being received? - Shao Miller -----Original Message----- From: gpxe-boun...@etherboot.org [mailto:gpxe-boun...@etherboot.org] On Behalf Of Axel Zöllich Sent: Tuesday, July 19, 2011 06:49 To: gpxe@etherboot.org Subject: [gPXE] Could not boot from filename "pxelinux.0" Hi, gPXE 1.0.1 worked well for severall weeks. But now I've got a problem. After a succesfull dhcp request the boot process comes to a halt with: Could not boot from filename "pxelinux.0": Not supported (0x3c126003) No more network devices. _______________________________________________ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe _______________________________________________ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe
