with latest svn the problem is solved

solved, ip on dhcp server option was incorrect

Also I have this rEFInd hangup screen… there are a solution? hw Is a hp all-in-one the temporary solution Is to Press f9 at boot to start via pxe so if hard disk Is the First start option in BIOS list Windows starts up normally, but Is Crazy pressing f9 Every time when you have to do a multicast session of 20-30 PC…

@george1421 in this way don’t work i created 2 vendor classes, one PXEClient:Arch:00007 for uefi and onother PXEClient:Arch:00000 for legacy and in this way all works

lenovo thinkcentre failed to boot hard disk after fog pxe boot benu (3 seconds timeout before foot hard disk) if i move the sata hard disk boot in bios before, and network boot after, windows boots normally. If network boot is firts instead, windows don’t boot

someone know howto fix?

@george1421 i defined uefi policy… but the wiki don’t tell me howto define legacy policy… what are the string that i must insert for legacy boot?

@fabritrento the cause was a bad setting in the bios now ipxe.efi works thankyou very much

@george1421 i have a i5 hp pc that has efi bios.

the only image that i can run correctly is undionly.kpxe (bios). If I try to use one of *.efi images the bios hangs, none of available works.
There are a reason?
I want to use efi version and not the bios version because all pc on my network are efi

What tftp image is right to use?

I started configuring undionly.kpxe image on the dhcp server.

all works, but i think that is the legacy bios image. what to use with uefi images?

in a network with a mix of legacy and uefi bios howto configure both?

images available is:

10secdelay boot.txt i386-efi intel.kkpxe intel.pxe ipxe.iso ipxe.kpxe ipxe.lkrn ipxe.usb ncm–ecm–axge.efi realtek.kkpxe realtek.pxe snponly.efi undionly.kpxe
arm64-efi default.ipxe intel.efi intel.kpxe ipxe.efi ipxe.kkpxe ipxe.krn ipxe.pxe memdisk realtek.efi realtek.kpxe snp.efi undionly.kkpxe undionly.pxe

solved, ip on dhcp server option was incorrect

@george1421 using ipxe.efi don’t work. the problem is that the client don’t transfer the file via tftp, giving a timeout.
using a tftp windows client after disabling windows firewall the system transfers the file.

@fabritrento enable logging gives these lines:

Jun 27 12:12:44 joana in.tftpd[43610]: RRQ from 192.168.2.41 filename undionly.pxe
Jun 27 12:13:25 joana in.tftpd[43643]: RRQ from 192.168.2.41 filename undionly.pxe