• Hi,

    I have an issue booting my MIIX 510 I start network booting with F12 and it show the following message:

    0_1499415792241_MIIX 510 Booting Issue.png

    So it says that is booting correctly but after that it starts to scan for IPv6 and then starts computer from hard drive instead of the network image.

    I will add that to start network booting I’m using an USB Ethernet dongle, Thinkpad USB 3.0 Ethernet Adapter (4X90E51405), it seems to work fine cause I’m getting an ip address, finding the network boot server and downloading the image with success.

    I will really appreciate your support, thanks!

  • Hey, I have good news, after disabling secure boot it works ok, and after cloning you can re-enable it without any problem.

    Thanks for your help Quazz and George!

  • Moderator

    @David_Alvarez That’s great to hear. The secure boot being on is always a pain and you do have to turn it off for imaging to work correctly.

    Thank you for providing feedback on this issue. Hopefully it will help others that come to this thread.

  • Hey, I have good news, after disabling secure boot it works ok, and after cloning you can re-enable it without any problem.

    Thanks for your help Quazz and George!

  • Thanks for your answers, I looked for all efi files in my hd but I didn’t found any other than sponly.efi. Following Quazz advice I rerun FOG installer updating it to 1.4.4, after that I get some .efi files, one of them ipxe.efi. But when I try to I get the same as the image attached to my first post. The computer gets ip address, it says it succeeded to download the ipxe.efi file, but after that it starts to check ipv6, and after that it boots from HD instead of the FOG boot image.

  • Moderator

    @David_Alvarez pfSense will work for auto file name delivery. I use it in my test lab.

    One issue I see is that your uefi boot file name is wrong. It should be ipxe.efi.

    your pxe boot files should be in (on the fog server) /tftpboot. This command should show you all of the efi files in that directory ls -la /tftpboot/*.efi

    If you don’t have a complete build, then as Quazz said rerun the installer. BUT those file should be there or the installer should fail (when you first installed them).

  • Moderator

    @David_Alvarez Rerun the FOG installer.

  • Thanks Quazz and George,

    According to your replys I founded this article:


    I have a problem here cause I have a Windows 2008 Server as DHCP, and according to this article I can’t configure it to work as DHCP for FOG.

    I have a pfsense for testing purposes, I configured it as DHCP according to the following article:


    I configured too in UEFI 32 & 64 bits the ixpe.exi file you are mentioning but it still fails.

    Then I checked the folder TFTP from FOG installation and the problem is that ixpe.efi isn’t there, Snponly.efi is the only .efi file there, I tried to load it but then it shows a TFTP error when I boot.

    Where can I get this ixpe.efi file?

  • Moderator

    Quazz is right. Your pxe booting device is in uefi mode, but you are sending a bios (legacy mode) boot kernel to it (undionly.kpxe). A uefi system needs a uefi boot kernel like ipxe.efi.

    If you have a mix if uefi and bios pxe booting clients and you have a windows 2012 or newer dhcp server there is a configuration change you can make to have the dhcp server automatically send the right file name based on the pxe booting client.

  • Moderator

    It’s because it downloads a BIOS PXE file, when it needs an EFI PXE file.

    Did you configure a DHCP server to serve this file?

    The file it needs is ixpe.efi (or any other one ending in .efi)