@Seb-B Thanks for clarifying. As well great that you tried the suggested debugging steps in the iPXE forums. There is a new suggestion on using an embedded iPXE script. Hopefully we’ll see more useful information this way. :-)
We are over some tests at last. As you suggested I did the following:
used a total dumb “link” between the pc and the network (hub): no change, still no boot properly
I used undionly.kkpxe and ipxe.pxe one by one. unfortunatelly no change.
Still no change, that means this hardware has somehow problems. Any other suggestion maybe? The problem is that we will surely get such hw, so it would be good to have a workaround somehow. Ah, one more thing. ipxe.pxe file gave a little difference. It said during boot that it boots from SAN device. Does it changes a thing?
@george1421, no we are using the legacy mode, i didn’t knew that the uefi mode worked in Fog :)
OK thanks for clearing that up.
Yes, uefi (working well) and nvme disks were added in an early 1.2.0 trunk release of FOG. With FOG 1.3.x both are fully supported and work very well. UEFI (EFI) is here to stay so its either support or die. Many new systems are coming uefi only (i.e. MS Surface Pro)