@gchartrandCRL I’m glad that worked! You should be able to keep using snp.efi with your previous machines.

@meie1kyl The fix for this issue was done in August 2023 and released in init version 20231208. My guess is that you haven’t updated your FOG install since 2023, or else the init should have “auto” updated.
I recommend that you update your FOG server to the latest stable version since there have been many fixes and security updates since 2023.

@meie1kyl I may be wrong but I have a feeling you are running an old version of the inits. Can you run these commands:

source /usr/share/fog/lib/funcs.sh
echo $initversion

@CanadienITGuy @gchartrandCRL I had to switch from using ipxe.efi to snp.efi for all my newer HP machines. Please try changing that in your DHCP scope options.

@Kureebow I’ve had this happen to me before. These are the two cases that I’ve seen:

1 - I captured an image in UEFI and the computer that I was deploying it to was in Legacy mode. I also had the inverse of this, where I captured in Legacy and was trying to deploy to UEFI.
2 (the most common for me) - Some sort of RAID or volume management device is enabled in the UEFI. I only use HP so I don’t know what it would be called on Dell, but on HP there is an option that I have to disable “Configure Storage Controller for VMD”.

@jacaman Does this happen with every HP computer or just one in specific? Does this happen with any other brand/model of computer? Have you tried deploying that same image to another computer? Have you tried replacing any component of the HP computer: HDD/SSD/NVMe, RAM, network adapter (dongle instead of embedded port)?

@Tom-Elliott Just thinking out loud here… Like you said, the UI interaction would probably be best as a plugin. For the FOS side, I would think that this could be done as a post init script modifying the fog.auto.reg, right?

@sloeckle You can use an older kernel for now, but I’ll work on a fix for this issue. I don’t have access to the hardware needed to reproduce this issue. Are you willing to help us test some kernels?

@DanCan Hi This is currently a known issue on some motherboards. Honestly not sure what is causing this to happen. I am working on a fix to this issue just haven’t had too much time lately.

@mrowand I consider Rocky (and other RHEL derivatives) a bit of an advanced distro. SELinux and the firewall are on by default and that makes things a bit more complicated.
In the FOG installer there is a check if SELinux is enabled and it’s recommended and the default option is to set it to permissive. There is also a check if the firewall is enabled but by default we don’t disable it, this means that you then have to go and modify the firewall rules for everything to work correctly.

I just re-created the VM and installed FOG, this time I didn’t set SELinux to permissive and didn’t disable the firewall and I am having some issues like you. This is not something that we need to/will “fix” since there are checks and recommend to set SELinux to permissive and disable the firewall.

If you have everything working now, we can set this post as resolved.

@collegestjoseph Can you try out this testing kernel and let us know if it works? https://github.com/rluzuriaga/fos/releases/tag/EXP_20250927

@mrowand I just created a Rocky 9.6 VM and installed FOG stable and didn’t have any issues. The install skipped php-json since it didn’t find that package. I didn’t need to install anything else manually.

Can you post an image of the error that you are getting?

Few things to check:
Is this a new Rocky Linux server? (I ask because if you are reusing a Linux install, it may have had some settings that could give you this issue)
Are you behind a proxy?
Is the Rocky install pulling the packages from the BaseOS/AppStream of the install ISO or from the web? (I ask this because this happened to me once)

@rurap Not sure what that patch would have been, but our last kernel release includes the Realtek R8168 driver. This kernel has fixed that same issue for other users.

@Afif I have seen this happen before due to a bad RAM module. Please run a memtest on the NUC.

@Clebboii It is now a general release (not in experimental phase). You can update to the latest kernel and init from the FOG settings pages or using this link: https://github.com/FOGProject/fos/releases/tag/20250715

@punch07 Everything there seems right to me.
Did you disable secure boot on the VM? Is the VM set to UEFI? ipxe.efi requires UEFI so make sure that the VM is changed from BIOS to UEFI.

@Clebboii I just noticed an error in how FOG displays the experimental kernel/init releases. For now, please get it from here: https://github.com/FOGProject/fos/releases/tag/EXP_20250630

@Eazis I created an experimental kernel that includes the drivers to fix this issue. Would you be willing to test it and let us know how it goes?

@Clebboii @olivier-bonnici I created an experimental kernel that includes the drivers to fix this issue. Would you be willing to test it and let us know how it goes?

@george1421 That is exactly what I did, I disabled the 8169 driver from the kernel config too.
I think I know what other issue you are talking about. The release that I posted earlier only has the 8168 driver.

I just uploaded a kernel with 8125, 8126, and 8168 drivers, if you want to try it out for that issue.
https://github.com/rluzuriaga/fos/releases/tag/EXPERIMENTAL_REALTEK_DRIVERS