HP ProBook 470 G4

[george1421]

@sudburr said in HP ProBook 470 G4:

You have a contradiction here.

Lets take a step back. If the laptop is in uefi mode, can you register it?

Or do you get a no such device error?

Or does it image fine but on reboot you get a no such device when exiting from the fog iPXE menu?

[sudburr]

It IS an odd one.

1. In UEFI mode
   a. Perform Full Host Registration and Inventory (init.xz… then returns to menu)
   b. Quick Registration and Inventory (init.xz… then returns to menu)
   c. Deploy Image ( see error above )
   d. Join Multicast Session (same as Deploy Image)
   e. Client System Information (init.xz… then returns to menu)

2. In Legacy mode
   … waiting on other stuff right now… will edit this ina few minutes.

[george1421]

@sudburr well lets see what happens here.

Schedule a deploy on this specific computer again in uefi mode.

Don’t pxe boot the computer, but key in the following into a browser: http://10.12.40.14/fog/service/ipxe/boot.php?mac=<mac_addr_of_probook>

Post the results here.

[sudburr]

Results

#!ipxe
set fog-ip 10.12.40.14
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 web=10.12.40.14/fog/ consoleblank=0 rootfstype=ext4 mac=48:ba:4e:51:d9:e2 ftp=10.12.40.14 storage=10.12.40.14:/images/ storageip=10.12.40.14 osid=9 irqpoll hostname=48ba4e51d9e2 chkdsk=0 img=Win_10x64_C_20170314_UEFI imgType=n imgPartitionType=all imgid=77 imgFormat=0 PIGZ_COMP=-3 type=down
imgfetch init_32.xz
boot

Then I:

1. Created a host entry for the client computer
2. Switched client back to UEFI
3. Scheduled a deploy from FOG to client computer
4. Client computer picked up task but then fails again with same error after init.xz

[george1421]

@sudburr Hmm well that ipxe boot menu looks OK. Its still not clear why its getting the boot device failure. Have you checked to see if you have the latest firmware on that device?

[sudburr]

Firmware is latest yes. 1.06

[Sebastian Roth]

@sudburr Possibly secure boot is on??

And by the way, … which iPXE is used here??

We have seen an issue with a device from ASUS, see here: https://forums.fogproject.org/topic/9361/could-not-boot-no-such-device (here the older ipxe7156 binary helped - though you can use those binaries in 1.4.4 we’ve tossed those out in the current working branch as the surface issue was resolved in the latest iPXE version some weeks ago. So you can also try the latest iPXE binary from the github repo)

[sudburr]

No. Secure boot is not on.

ipxe7156.efi works. ugh.

[sudburr]

Good news everyone!

ipxe.efi (1b67a) works.

[Tom Elliott]

So we can solve this, or 1b67a is very old ipxe file?

[sudburr]

ipxe.efi (1b67a) is the latest from the github repo linked above.

[george1421]

@tom-elliott Just looking at rom-o-matic 1b67a is the latest release. I’m not in a place right now to see what boot version is in 1.4.4. I can check later tonight. But I would suspect that 1.5.0RC9 will have the fixed version of ipxpe where/when/since ipxe7156.efi was removed from fog.