No configuration methods succeeded
-
No configuration methods succeeded
i am trying to create a fog image of a lenovo thinkbook 15-G2 laptop
its set to legacy and that fails to get dhcp
when i use the EFI -PXE i am getting the error no configuration methods succeeded
now the setup works on all my other computers we deploy from our fog server its just this one that is not working i thought maybe it has a different configuration file needed for pxe boot but i am unable to find anything on here .thanks
-
@kbell So both UEFI and Legacy work on other machine? Secure boot off?
-
@kbell said in No configuration methods succeeded:
legacy and that fails to get dhcp
when i use the EFI -PXE i am getting the error no configuration methods succeededThese are really two different issues in my mind depending on where the error is happening.
The bios doesn’t get dhcp, I would think that is a dhcp server or possibly spanning tree issue if the other systems would not work too.
If the error “no configuration methods succeeded” is in iPXE *“.e. you see the ipxe banner, but then it fails to configure” Then dhcp and pxe booting is OK, just iPXE can’t for some reason pick up a dhcp IP address.
So I would start with, what device is your dhcp server?
Second question is your fog server, dhcp server, and pxe booting computer all on the same subnet? If so we might grab a pcap of the pxe booting for this system.
Something that comes to mind is for typical dhcp servers they have the pxe booting information in the dhcp header (bootp protocol) as well as in dhcp option 66 and 67 (dhcp protocol). Its up to the firmware vendor to decide which boot method to look at. I have seen random pxe booting issues because the dhcp server vendor doesn’t follow the exact RFC for pxe booting.
-
@tesparza yes works on all the other computers excep the lenovo thinkbook
yes secure boot is disabled in bios
-
@kbell Some bios have UEFI network stacking option, is it enabled?
-
@george1421 both the errors are happening to the lenovo thinkbook
depending which boot i use
if i use legacy boot i get the failed dhcp
if i use the other boot i get the configuration error message -
@kbell Which version of FOG do you use??
If it’s not the latest dev-branch version then you might try using those: https://github.com/FOGProject/fogproject/tree/dev-branch/packages/tftp
If it does work I suggest you upgrade to dev-branch as it has many fixes included.
-
You are not running the most current version of FOG!
You are currently running version: 1.5.9.98
I’m a little confused i thought version 1.5.9.98 is a higher version then 1.5.9Latest stable version is 1.5.9
Latest dev-branch version is 1.5.9.111
Latest alpha-branch version is 1.6.0-alpha.1133but i see the dev version is higher then what we are running on
what should we be running on -
@kbell Sorry for the confusion. It just means you are not running the latest official release. In fact you are ahead of that using dev-branch already.
While 1.5.9.98 is definitely newer than 1.5.9 it still has the same old iPXE binaries. So I suggest you update to dev-branch 1.5.9.111 to use the newer iPXE binaries we uploaded on 17th of July this year.
-
@kbell I only see that problem when i use incorrect ipxe file, uefi/legacy independent. the pxe file must match with nic drivers, and firmware type, (.efi for efi systems), (.pxe, .kpxe, .kkpxe for legacy systems), and not all ipxe files have all nic drivers, some realtek cards not works with undionly.kkpxe and you need to use realtek.kpxe, same on uefi i have nics that require snp.efi instead of ipxe.efi.
