PXE boot fails on a WIN10 based Lenovo (USB Ethernet) - FOG TRUNK

[arnaudrigole]

Hello Fog Community,

I encounter a problem today , trying to upload an image from a Lenovo Yoga 460, with a USB Ethernet (lenovo official, needed to boot on PXE)

It launch the process, get an IP, then “Download the NBP file”, and finish with “Download NBP succeeded”. But, after that, the computer don’t load the ipxe menu and reboots.

I expect a kernel problem, i saw on fog 1.2 that some of these has “USB” in kernel name, and some else no. But in fog trunk, no “USB” in description.

0_1464083901946_IMG_0583.PNG

Thank you for your help!!!

Arnaud

[george1421]

@arnaudrigole Thank you for providing the picture, that tells me something important and then I’ll read between the lines to fill in the rest.

You have a Lenovo and you had to use a supported usb ethernet adapter to boot. And I also see the word NBP, that kind of tells me you are booting the yoga in uefi mode. If this is the case you are sending a bios iPXE boot file to this client, which will of course cause the yoga to fail to boot. The proper uefi boot kernel is ipxe.efi. Change your dhcp option 67 to ipxe.efi and this yoga should boot into the fog menu.

Also make sure that the secure boot is off, that will be the next error you could run into.

[housekeeping] moving this thread to the hardware section since its not a windows issue (not there yet) [/houskeeping]

[arnaudrigole]

Great! i created another dhcp strategy which have ipxe.efi for option 67, it works.

Thanks you george, i mark this thread as solved.

[george1421]

@arnaudrigole If your dhcp server is a windows 2012 server you can add a filter to send the uefi boot file to uefi device and the bios boot file to bios devices automatically. That way you don’t need to manage two different scopes. Unfortunately this filter is not available for windows 2008 dhcp server.

[Wayne Workman]

@george1421 said in [SOLVED] PXE boot fails on a WIN10 based Lenovo (USB Ethernet) - FOG TRUNK:

@arnaudrigole If your dhcp server is a windows 2012 server you can add a filter to send the uefi boot file to uefi device and the bios boot file to bios devices automatically. That way you don’t need to manage two different scopes. Unfortunately this filter is not available for windows 2008 dhcp server.

Here’s our article on this process: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

[fry_p]

@Wayne-Workman @george1421 We are going to move toward getting more UEFI devices (Surface Pro 4’s) but still have many BIOS devices as well. We happen to have DHCP on 2012. It’s a pain switching option 67 back and forth, I will try this in the morning. Thanks again, super valuable info!

[george1421]

@fry_p Then follow the link that Wayne posted. That will help greatly with Windows 2012 dhcp server. It DOES WORK well managing the option 67 parameter for you.

[arnaudrigole]

@george1421
Great to know it. Also, my DHCP server is a 2008 one…

[arnaudrigole]

@fry_p said in PXE boot fails on a WIN10 based Lenovo (USB Ethernet) - FOG TRUNK:

@Wayne-Workman @george1421 We are going to move toward getting more UEFI devices (Surface Pro 4’s) but still have many BIOS devices as well. We happen to have DHCP on 2012. It’s a pain switching option 67 back and forth, I will try this in the morning. Thanks again, super valuable info!

Maybe you could try DHCP strategies to assign uefi ipxe to uefi devices, and undionly.kpxe to bios devices via clients mac@ddress

[Wayne Workman]

@arnaudrigole That’s one way, albeit incredibly labor intensive.

Since you have a 2008 server, maybe you give a shot at setting a vendor class filter in it? There are some screenshots in the below article from 2008 to help you along your way, but I’ve not been successful yet. That’s not to say it can’t be done, it’s just saying it hasn’t been done yet. I was working on a community member’s production 2008 DHCP server and messed with it for a while but no luck. I’m not entirely sure his environment was even setup correctly…

If you are successful, we will be wanting screen-shots and steps for the Wiki.