No boot UEFI IPV4 (HP elitebook 840)
I am new to the FOG, I have a problem with a UEFI computer (HP elitebook 840), but in Legacy it works very well.
I would like to know how to boot in UEFI and understand how to do it if it’s possible?
it is to predict the next machine that works only uefi, I do not understand the setting of FOG UEFI too complicated for me :(
in which FOG menu I need to make the setting or which line of code for the terminal
- MAJ FOG in 18.104.22.168.
- DHCP is the FOG that manages it.
- management FOG (WEBMIN)
- on the bootfilename I unionly.kpxe (only works in legacy and not in UEFI and what is it ?)
- custom FOG setting …
Thank you for all help :(
sry for my english.
The setting of FOG 22.214.171.124:
on the HP elitebook 840 laptop, I received a message and can not go further?
@Beber55 Ok, permission error was missleading, nevermind.
You need to edit the file:
Now make the change, save (ctrl+o), exit (ctrl+x) and then run the other commands to restart and read log file as suggested earlier.
I do not understand about two command?
I tried… :
@george1421 There were two commands…
the result :
-rw-r–r-- 1 root root 133 oct. 23 2017 /etc/default/tftpd-hpa
@Beber55 Please run the following commands and post output here:
whoami ls -al /etc/default/tftpd-hpa
george1421 how can I thank you for the help you give me ?
With /etc/default/tftpd-hpa , I have the message (permission not granted), I use sudo -i to log in as an administrator ?
sorry for my lack of knowledge.
@Beber55 I’d suggest enabling verbose logging for TFTP in your FOG server. For that edit
TFTP_OPTIONS="-s -v". Then restart:
systemctl restart tftpd-hpaand keep an eye on the logs:
tail -f /var/log/messages /var/log/daemon.log | grep "tftp"while you boot up the client.
Yes the file can be downloaded from the FOG server, photo to have confirmation?
The update of the BIOS does not change anything, I have the same problem.
thank you george1421.
@Beber55 sorry for the delay I have meetings here all day.
From a windows computer, install the tftp client feature. Connect the windows computer to the isolated imaging network. Then from windows command prompt key in:
tftp 10.10.10.10 GET ipxe.efi .This will test if the ipxe.efi file can be downloaded from the FOG server to the target computer. In this case we only want to test if it downloads.
If that works then we will need to do a bit more debugging.
One last idea, make sure the firmware (BIOS) is updated to the latest on the target computer (hp elitebook 840). That will make sure any fixes are on that hardware before we go to the next step with testing.
Thank you very much for the explanations :)
Yes the FOG server is isolated and it manages DHCP.
No I did not manually modify the DHCP configuration files, just some IP following a
So normally the FOG need to know where to start IPXE.EFI or undionly.kpxe automatically?
The secure boot (secureBoot) is disabled,
I have the same problem.
So do I understand that the fog server is on an isolated imaging network and the FOG server is configured as the DHCP server for that isolated network?
If the FOG server is managing DHCP then it will send the right boot file name based on the pxe booting computer unless you adjusted the dhcp server configuration files by hand.
For BIOS (legacy) the boot file is undionly.kpxe for sure. For UEFI computers the boot file is ipxe.efi. It looks from your boot screen picture that its unable to load ipxe.efi. You can not mix these boot files. A uefi boot file (ipxe.efi) will not start on a bios (legacy mode) computer. The same the other way to.
With UEFI computers, make sure that secure boot is disabled in the firmware (BIOS) setup pages.