Lenovo E15 Gen2 won't PXE boot (bzImage)

[george1421]

@sebastian-roth said in Lenovo E15 Gen2 won't PXE boot (bzImage):

booting into FOS Linux

You must have caught my post just after I posted it. After I hit the submit button I realized that the target computer didn’t ipxe boot directly so I changed my story. I think still getting the PCAP is what we need to see if its actually sending out the dhcp discovery bits.

[x23piracy]

@george1421 we have a supernet at work 172.19.100.0/22 (100.0/24, 101.0/24, 102.0/24 & 103.024) the two fog servers are reachable under the following ip addresses (172.19.102.17 (fog), 172.19.102.18 (fog-image) storage node. All other clients do well with current ipxe.efi (fog 1.5.0).

when i change back from snponly.efi to ipxe.efi all my other devices work well as before.

When i deploy the E15 devices with their dock it works fine, the dock nic seems to be propperly detected, the bad thing is if the device goes into windows it doesnt know the docks nic driver the first time but the internal nic is working, so we put the network cable after deployment into internal nic so fog client can do his job (rename, ad-join etc.) another solution (workaround) would be to deploy the device with both nics connected to the network.

Best Regards X23

[george1421]

@x23piracy Do you have a usb boot stick into FOS Linux? This would bypass the ipxe.efi boot loader completely. When booting via USB, does fos linux work correctly for imaging? What is the hardware id that it sees with lspci -nn | grep -i net?

Does this lenovo e15 have the latest firmware installed?

[Sebastian Roth]

@x23piracy said in Lenovo E15 Gen2 won't PXE boot (bzImage):

All other clients do well with current ipxe.efi (fog 1.5.0).

You are still on FOG 1.5.0? Ok, then you can really try out the latest iPXE binaries manually and see if it works. Download ipxe.efi from https://github.com/FOGProject/fogproject/tree/1.5.9/packages/tftp, rename the original you have in /tftpboot/ on your FOG server and put the new one in place. See if the Lenovo E15 can get an IP with that.

[x23piracy]

@sebastian-roth yes i am still on 1.5.0, i tried to update to the latest but update repository problems kicked my ass.

Best Regards X23

[x23piracy]

@george1421 hi george i am currently not on site (home office) i can try this when i am back in the office.

Best Regards X23

[Nate Baker]

For anyone else coming across this thread, we had the same problem. The iPXE from the latest version of FOG (1.5.9) did not work, but building the latest iPXE binaries using the instructions on this post worked fine:

https://forums.fogproject.org/post/141618

After that, the Linux kernel we were using also worked fine.

[x23piracy]

@nate-baker said in Lenovo E15 Gen2 won't PXE boot (bzImage):

For anyone else coming across this thread, we had the same problem. The iPXE from the latest version of FOG (1.5.9) did not work, but building the latest iPXE binaries using the instructions on this post worked fine:

https://forums.fogproject.org/post/141618

After that, the Linux kernel we were using also worked fine.

Hi @Nate-Baker can you share the kernel please?

Best Regards X23

[george1421]

@x23piracy said in Lenovo E15 Gen2 won't PXE boot (bzImage):

Hi @Nate-Baker can you share the kernel please?

What Nate is referring to is rebuilding ipxe and using those new ipxe boot code. The link he referred to tells you how to do this on your FOG server assuming you used the git method to install FOG.

Not really connected to ipxe, but make sure you are running 5.10.x version of FOS Linux kernels to have the latest hardware support.

[x23piracy]

@george1421 just a moment ago i successfully compiled my own ipxe.efi binary and it works fine https://forums.fogproject.org/post/141618

[terrigan]

You need to disable the Intel VT-d Directed I/O setting and it will pxe boot. I couldn’t get Win10 to boot without disabling the Intel VMD controller as well. (Sorry for the necropost)

[terrigan]

In the BIOS on the configuration tab, disable Intel VMD Controller and disable Secure Boot on the security tab. This is the only way i’ve gotten this to image.