@trent_potter Yes you figured it out. Sysprep is a Windows utility, it has nothing to do with FOG. It is always recommended to sysprep before capturing an image.

@JCS-RVK Okay so I don’t see why this kernel wouldn’t work for you with those settings. Only difference I can think of may be the initrd version that is being loaded. I know that @BPSTravis is using the latest released version so it wouldn’t hurt to update yours too.

I also see that you are running an older version of FOG. You could upgrade to the latest stable release and that will also download the latest initrd.

You could also download it manually if you don’t want to update FOG:

On your FOG server, run this command to download the latest initrd
wget https://github.com/FOGProject/fos/releases/download/20260306/init.xz

Move it to the correct location like this:
sudo mv init.xz /var/www/fog/service/ipxe/

Then you need to change the permissions and ownership of that file:
sudo chmod 644 /var/www/fog/service/ipxe/init.xz

Red Had based server: sudo chown fogproject:apache /var/www/fog/service/ipxe/init.xz

Debian based server: sudo chown fogproject:www-data /var/www/fog/service/ipxe/init.xz

@JCS-RVK Hi I have a kernel that should work for XCP-ng. If you don’t mind giving it a try and let me know if it works for you please.
You will need to download and set it up manually but here are the instructions.

On your FOG server, run this command to download the test kernel
wget https://github.com/rluzuriaga/fos/releases/download/EXPERIMENTAL_XCP_1/bzImage
That will download it to whatever directory you are currently on.

Rename the file and move it to the correct location like this:
sudo mv bzImage /var/www/fog/service/ipxe/bzImage_XCP

Then you need to change the permissions and ownership of that file:
sudo chmod 644 /var/www/fog/service/ipxe/bzImage_XCP

Red Had based server: sudo chown fogproject:apache /var/www/fog/service/ipxe/bzImage_XCP

Debian based server: sudo chown fogproject:www-data /var/www/fog/service/ipxe/bzImage_XCP

Then add bzImage_XCP to the Host Kernel line in the XCP-ng host on the FOG web.
Also, remove all the host kernel arguments.

@BLT I don’t necessarily have a timeline for the final release but I did just release an experimental kernel with a newer nic driver. It may work for you if you want to give it a try.

@BLT Hi I am working on an updated kernel that should support newer hardware like the Framework Desktop.

@jas777 Hi sorry for the delay. I believe I have the solution for this issue.
I haven’t been able fully test these changes on physical hardware, so I pushed them to another branch. Please clone the repository and change the branch like this before installing:

git clone https://github.com/fogproject/fogproject.git
cd fogproject
git switch ipxe-bios-test

Let me know if it works out for you.

@jas777 It looks like you are running an old version of iPXE. The newest version, as of 10 minutes ago when I built it, is 1.21.1+ (g21b5b).
I may be wrong, since I don’t use my own custom certificate, but you probably need to rebuild your iPXE with the new certificate.

@heix75 Did you update from 1.5.10.1754 to 1.5.10.1763 or from an older version?

@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)