@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

@Clebboii Thank you so much for testing this! I now have a better idea of what needs to be done for future releases.
You are welcome to continue using the “OEM driver” kernel for now until I create a full upstream release.

@Clebboii Sorry to double up on the requests… After you try the commands from my last reply, can you please try this kernel? https://github.com/rluzuriaga/fos/releases/tag/EXPERIMENTAL_OEM_Driver

Can you also try the ethtool command with this kernel please?

@Clebboii Thanks for testing! Using the kernel I linked previously, can you run the following command and post the output please?
ethtool interface
interface would be your ethernet interface like eth0 or ens1. You can get it using the command ip a s

@olivier-bonnici @Clebboii Sorry for the delay. Would either of you be willing to test another kernel? If so, please download it from here: https://github.com/rluzuriaga/fos/releases/tag/EXP_20250617

@Clebboii Sorry for the delay on this.
Others are having the same issue and George has something good to try. Please try this out and let us know.

@george1421 said in FOG Very Slow to Deploy Image - Lenovo Neo 50Q Gen 4:

@olivier-bonnici If you have time to test, I have an idea what maybe causing this. I just saw a video on hacking a chromebox (seemingly unrelated), and they had a similar issue with downloads being unnaturally slow but uploads were OK.

It came down to the energy efficient ethernet built into the realtek nic.

What I want you to do this this:

1. schedule another deployment to this hardware, before you hit the schedule task button tick the debug checkbox then schedule the task.
2. PXE boot the target computer, it should go right into imaging, well it should drop you to a linux command prompt after several screens of text.
3. At the linux command prompt, we need to find the name of the ethernet adapter device. Issue the following command ip a s . Look in the list for the network device that has an IP address. Write down that name for the next stel.
4. Use the linux tool ethtool to disable ‘eee’ on the network adapter, in this case the ethernet adapter name is eno0 yours might be different, fix accordingly ethtool --set-eee eno0 eee off
5. On success of setting green ethernet to off lets start the imaging process. Key in fog and press enter. This will place you in single step mode. You will need to press enter at each breakpoint in the code but you will be able to see the partclone screen to see if the speed has improved.

I don’t know specifically if this is your issue but its worth a shot. If it does work we can do a few things to make this a forever change, but first we need to find out if it works or not.

@Clebboii I just checked through the commits between kernels 5.15.34 and 5.15.98. I didn’t see any changes that would cause this issue.

I have a theory of what it could be, so can you try this kernel I added to my forked repo. Let us know if the networking issue still persists.

@John-L-Clark Can you try updating to the latest dev-branch of FOG? This is mainly to update iPXE to the latest version.
After updating, please try the experimental releases of the kernel 6.12.25 and initrd 2025.02.0

@Itay1787 I just pushed a change to the dev-branch. Please try installing it again from there and let me know how it goes.