Error with UEFI

[MaximeGuidez]

Hello,

We bought new computers from HP in Generation 8 and it seems that the Legacy option is no longer possible …

I tried to change the Filename to “ipxe.efi” otherwise I had nothing at all and I end up with an error message that I do not understand.

>>Start PXE over IPv4.
Station IP address is 192.168.1.206

Server IP address is 192.168.0.200
NBP filename is ipxe.efi
NBP filesize is 1044256 Bytes
Downloading NBP file...

NBP file downloaded successfully.
iPXE initialising devices... ok



iPXE 1.20.1+ (g4bd0) -- Open Source Network Boot Firmware -- http://ipxe.org
Features : DNS FTP HTTP HTTPS iSCSI NFS TFTP SRP VLAN AoE EFI Menu
Waiting for link-up on net0..... ok
Configuring (net0 xx:xx:xx:xx:xx:xx)................. No configuration methos succeeded (http://ipxe.org/040ee186)
Configuring (net0 xx:xx:xx:xx:xx:xx)................. No configuration methos succeeded (http://ipxe.org/040ee186)
DHCP failed, hit 's' for the iPXE shell; reboot in 10 seconds

Can anyone tell me how to fix this error?

For information, my Fog is installed on an Ubuntu server and the DHCP server is managed by UniFi

(in Legacy mode I never had any problems)

Thank you

[Yeet]

@maximeguidez I ran into this issue in the past, and if I remember right switching the bootfile to snp.efi was what fixed the issue. I’ve stopped using ipxe.efi altogether, since snp.efi seems to cover all of the devices I end up imaging.

If that doesn’t work, I’d recommend updating the kernel version.

[george1421]

@yeet said in Error with UEFI:

Just two points to clarify here.

I’ve stopped using ipxe.efi altogether, since snp.efi seems to cover all of the devices I end up imaging.

snponly.efi for uefi is roughly equivalent to what undionly.kpxe is to bios. Both of these ipxe boot loaders use the network adapter’s built in firmware driver. For bios, the undi firmware interface is very mature and stable. For uefi the snp firmware interface has been historically very flaky until the last few years where it has matured a bit and become more stable. For both the undi and snp firmware drivers, its up to the nic manufacturer to make sure the firmware driver conforms to the strict standards. This doesn’t always happen.

Now ipxe.kpxe is to bios what ipxe.efi is to uefi. In the case of these boot loaders these are more like a linux kernel than not. These boot loaders have one of every known driver installed. The complete network and disk drivers are part of this boot loader kernel. The benefits are that ipxe has a very stable and known network and disk controller communication. The down side is that its sometimes difficult to keep up with emerging hardware. That is where undi and snp firmware drivers have helped since they are created by the hardware manufacturer when the new hardware is released. If the developers find that many people are having success with the snponly.efi drivers, they may change their default recommendations.

If that doesn’t work, I’d recommend updating the kernel version.

Don’t confuse the ipxe menu and the boot loader from the FOS Linux kernel. They are two different systems that work together. iPXE gets you to the FOG menu on the target computer. Once you select a menu item and bzImage is loaded then its FOS linux in charge. If you are having network issues and don’t get to the FOG iPXE menu then its a ipxe boot loader issue, if you get to the menu but when you select a menu item then see a network issue then its FOS Linux with the problem. I said all of that to say, if iPXE will not initalize then updating your {FOS Linux} kernel will not help you.