Trouble booting into iPXE from new HP Probook 440 G11
-
Hi there,
We are purchasing some HP ProBook 440 G11 laptops. I'm trying to network boot using iPXE and I'm having trouble. On the laptop, the process stops at "iPXE Initialising devices..." Here's a screenshot:
On the server, when I check the logs viewer in the TFTPD64_gui.exe, I see the following:
Connection received from 10.14.2.19 on port 1897 [31/03 11:37:06.603]
Read request for file <proxy/efi64/pxeboot.0>. Mode octet [31/03 11:37:06.603]
OACK: <tsize=1020416,blksize=1468,> [31/03 11:37:06.604]
Using local port 58007 [31/03 11:37:06.604]
Peer returns ERROR <User aborted the transfer> -> aborting transfer [31/03 11:37:06.604]
Connection received from 10.14.2.19 on port 1898 [31/03 11:37:06.604]
Read request for file <proxy/efi64/pxeboot.0>. Mode octet [31/03 11:37:06.604]
OACK: <blksize=1468,> [31/03 11:37:06.604]
Using local port 58008 [31/03 11:37:06.604]
<proxy\efi64\pxeboot.0>: sent 696 blks, 1020416 bytes in 0 s. 0 blk resent [31/03 11:37:06.747]
Connection received from 10.14.2.19 on port 1899 [31/03 11:37:06.763]
Read request for file <proxy\efi64\autoexec.ipxe>. Mode octet [31/03 11:37:06.763]
File <proxy\efi64\autoexec.ipxe> : error 2 in system call CreateFile The system cannot find the file specified. [31/03 11:37:06.763]Everything works on all of our other devices. Also, I tried updating the Kernel in the boot menu to the newest version available, "6.13.4x64-updated".
Any ideas on what I can do? Thank you!
-
can you try using the ipxe snp only or snp file
-
@theopenem_admin Sure, I just tried both of those options in the "PXE settings" menu. I got the same result.
-
I could try building the latest version of iPXE but it may take a few days
-
@theopenem_admin Sure, that sounds good. We are in no rush. I did have a similar problem a few years back and a new iPXE build did solve my problem back then. Thank you so much!
-
@theopenem_admin Good morning! Any luck on the ipxe build? Thanks!
-
Sorry my dev vm died and I lost a lot of my build scripts. Getting everything setup again, hopefully in the next day or 2.
-
@theopenem_admin Oh no, I'm sorry to hear that.
-
Here is the latest version, i see you are using the proxy.
http://files.theopenem.com/ipxe.efiPlace it in
Program Files\tftpboot\static\ipxe\proxy\ipxe_efi_64Then in admin settings->pxe /boot menu ->pxe settings, change your ipxe 64 bootloader to something other than ipxe_efi, save it, and then change it back to allow the new file to copy to the correct folder.
-
@theopenem_admin
Thanks! I just tried it out. Looks like we're making some progress. Unfortunately, now I'm getting this timeout error after pulling down the default.ipxe file. I'll keep poking around.
-
Looks like the tftp server is empty for some reason. I'll double check some things
-
@theopenem_admin
Thanks! I poked around on this end and wasn't able to get anywhere. -
@theopenem_admin Good morning! Any luck adding that TFTP path to the ipxe image? Thanks!
-
I haven't been able to see the issue. Is the new version not working on the older machines either?
-
@theopenem_admin Yea, unfortunately. I just tried an older device that worked before again and it times out trying to download the default.ipxe file.
-
@theopenem_admin I copied the old ipxe file back and updated the pxe settings. I get this error when I do that, I don't know if it would be relevant.
"Updated Settings Successfully, But Could Not Copy PXE Binaries On One Or More Com Servers. Check The Logs For More Info"
The old file works on my old device again.
-
I can't seem to replicate this, the latest version seems to be working for me. Are you using the proxy dhcp service, how are your dhcp options setup?
-
Also, can you send me your original ipxe file that is working for the old models.
-
ipxe.zip @theopenem_admin We are using the DHCP proxy. Here is a screenshot of the options in the server.
Also, I attached my original ipxe file that works.Thanks for the help!
-
@theopenem_admin Also, we have two other DHCP policies set up for 32-bit and BIOS respectively in the DHCP server. But, we really don't use them these days.
