HP Elitebook 840 G8

[mcgeezacks]

Hello!

I’m having issues deploying an image to a new group of laptops, the HP Elitebook 840 G8. I’m currently on FOG version 1.5.9 and kernel versions 5.10.50. It’s worth noting the deployment works fine on older machines but doesn’t like these new laptops.

I’m able to network boot into FOG and select “Deploy Image”. From there it asks for the username and password, when I hit enter, the screen flashes but nothing happens. I hit enter again, it starts loading bzimage and init then ends up on an unexpected screen with several options: 1) Reboot 2) Network Information 3) Partition Information…

Any help would be much appreciated! Thanks guys

[george1421]

@mcgeezacks Would you provide a clear screen shot of this error. I can’t place where in the pxe booting process this screen is coming from.

An additional thought is to see if we can download the latest iPXE build images (newer than what is in 1.5.9) to see if that solves the issue.

Also make sure the firmware is up to date on these new HP computers. Where it sounds like its failing is at the transfer of the FOS Linux kernel (bzImage) to the target computer.

Lastly see if snponly.efi works better if you are currently using ipxe.efi for the UEFI boot loader.

[Sebastian Roth]

@mcgeezacks said in HP Elitebook 840 G8:

I’m able to network boot into FOG and select “Deploy Image”. From there it asks for the username and password, when I hit enter, the screen flashes but nothing happens. I hit enter again, it starts loading bzimage and init then ends up on an unexpected screen with several options: 1) Reboot 2) Network Information 3) Partition Information…

This sounds like you boot into the “Client System Information (Compatibility)” part of the FOS inits. Probably something goes wrong with the password entry for “Deploy Image” and then it comes back and goes to the sysinfo when hitting enter once again.

First I suggest you update to the latest iPXE binaries to see if those are still doing the same. Either by updating to dev-branch, manually loading the latest binaries from github or compiling the very latest iPXE binaries using the script provided in fogproject/utils/FOGiPXE/buildipxe.sh.

The other thing you can try is to register the new 840 G8 devices and schedule deploy tasks for them.

[george1421]

@sebastian-roth Similar here here. Cross linking posts: https://forums.fogproject.org/topic/15779/deploy-image-menu-not-coming-up

[mcgeezacks]

Thanks for the responses everyone.

I can confirm the firmware on the laptop is up to date. I’ve updated to the latest iPXE binaries by using the script provided at fogproject/utils/FOGiPXE/buildipxe.sh.

Still no luck here.

@george1421 I’m trying to see if snponly.efi will work but I’m struggling to find any information on how to swap the UEFI boot loader. Any tips? Also, thanks for linking the other post.

[george1421]

@mcgeezacks said in HP Elitebook 840 G8:

I’m trying to see if snponly.efi will work but I’m struggling to find any information on how to swap the UEFI boot loader. Any tips? Also, thanks for linking the other post.

In this case this setting is supplied by your DHCP server for this network.

What device is your dhcp server?

[Dungody]

Hello
Exactly What i said. On every Probook and elitebook G8

problem-i-can-t-restore-image-on-hp-probook

Sincerly.

[Sebastian Roth]

@Dungody As you mentioned in the other topic it’s not a general problem with FOG - “quick registration work , deploy by selecting host on web interface work”

So it’s actually an issue in the iPXE code or HP firmware. We are happy to help you guys find the right people to talk to but it’s not something we can fix. All we can do is provide the latest version of iPXE - which we do if you use the mentioned fogproject/utils/FOGiPXE/buildipxe.sh script.

@mcgeezacks @Dungody please get in contact with the developers of iPXE to see if they can work this out: https://ipxe.org/contact

[Dungody]

@sebastian-roth Ok Thank you , i understand !

[Sebastian Roth]

@Dungody Please keep us posted on your findings. As soon as there is a fix in iPXE we cann add the to the dev-branch version.

Also feel free to ask here if you need help with providing the information the iPXE developers will definitely ask you for.