PXE boot issue with HP Probook 450 G8 (Realtek Nic)
-
@george1421 Yeah, quite possibly!
@RobertD Thanks heaps for posting this information here!
-
@george1421 I stared at this and thought… this seems like it would break FOG. and I didn’t try it.
-
@rankinc said in PXE boot issue with HP Probook 450 G8 (Realtek Nic):
this seems like it would break FOG
Well without the actual hardware in front of the developers, they have to rely on fog admins to try different things with their harware until they find a working path. So well done!!
-
@george1421 I could be missing another setting, but my fix is copying refind.efi to refind_x64.efi. the original refind_x64.efi, v12 and v13 did not work even after DMA disable.
-
@rankinc The developers shipped 0.11.0 for a long time with FOG. Sometimes when the newer ones fail we would recommend testing 0.11.0 to see if that masked the issue. But really we need to find out why the newer ones are failing so FOG can stay current with iPXE
-
@rankinc FWIW the only thing we did was, disabled secure boot, disabled DMA protection, changed the UEFI boot order to nic first (I also disabled all the other options) and it started working.
We were facing the exact same problem in the screenshots above. We are using ipxe.efi
EDIT: My machine also hangs at “rEFind - Initializing” after the image has been deployed, but we are just going back into the BIOS and setting the HDD as the first boot device after the image has been pushed. I don’t know where to begin troubleshooting this part of the process. Legacy BIOS was so much easier…
-
@robertd said in PXE boot issue with HP Probook 450 G8 (Realtek Nic):
My machine also hangs at “rEFind - Initializing” after the image has been deployed, but we are just going back into the BIOS and setting the HDD as the first boot device after the image has been pushed. I don’t know where to begin troubleshooting this part of the process. Legacy BIOS was so much easier…
I can only give you a perspective from a Dell shop. In our case we do not boot through the fog server, but instead I require the IT techs to sit in front of the computer and press the F12 button during booting to get into the firmware boot manager, then select network boot. The default boot order is hard drive, so once imaging is done it boots back to the local hard drive. So personally I have not seen refind hanging, because we never really get there since we don’t boot through the fog menu. I’m not saying its a right or wrong way, just a different way.
-
@george1421 Understood.
For us it’s just extra steps we try to eliminate. We are a pretty large school district with over 65K students and 10K employees and a lot of machines. We have more then once had to re-image an entire campus because a virus outbreak and being able to push an image to a school and just telling them to reboot has saved us a lot of time in the past. Thankfully this hasn’t been an issue in a long time. Maybe times are changing and UEFI is going to force our hand…
-
Hello,
I have the exact same problem “no configuration method succeeded” with a Lenovo Laptop 20VE series
this is a realtek 8168 nic.I tried to change the ipxe.efi to snponly.efi and it is working fine.
Since I don’t know what are the differences between ipxe.efi and snponly.efi. I’m going to stay on snponly.efi.
I didn’t try realtek.efi since this snponly is working for me.
Thank you for your help
-
Yeah, switching to a different iPXE binary can help in some cases too.
Though I want to bring up what I have posted two weeks ago as well: https://forums.fogproject.org/post/141320 (compiling the latest version of iPXE)
-
Chiming in here… I’ve been stumped for some time after I too purchased a handful of new G8 HP Laptops.
Fortunately I found this thread, and I am glad to say that snponly.efi worked for me!
I figured posting might keeps this thread alive and relevant for others.
-
@ayy_nelson said in PXE boot issue with HP Probook 450 G8 (Realtek Nic):
I too purchased a handful of new G8 HP Laptops.
Some things we found with this new generation of systems with this realtek network adapter. Update your FOS Linux kernel to 5.15.x series (we just discovered this) and also update your iPXE version using this method. https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe
Right now we only have anecdotal evidence that it fixes what changed in this generation of hardware.
