Posts made by rodluz

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

@jflash Great! Did you use the default kernel from FOG after the update, or did you use the kernel from my repo?

@Tycho Okay so I see two things that could be the problem.

1. Is your Hyper-V network adapter on the same subnet as the FOG server? I’m guessing yes as I only see one scope in your DHCP.
2. In the FOG document that you uploaded, is see this line: All router, DNS, and DHCP setting: No, n in the installation steps.

I recommend that some of those settings are actually set to yes. Like this:

Make sure that the IP for your DHCP and DNS servers are set correctly in those first two prompts.

---

If it still doesn’t work, then please include an image/video of the failure.

@pilipp_edv I had a very similar issue to this a while back but it was with an HP laptop. It turned out to be a hardware defect. I was able to get the motherboard replaced under warranty, so maybe you can too for this laptop.

@jflash I was just rereading through the full post and noticed a couple things.

I’m using FOG version 1.5.9. TFTP Server settings:

This is a really old version of FOG. I would recommend upgrading to the latest stable release.

---

From the last picture, your iPXE version should be updated too. @Tom-Elliott Can correct me if I’m wrong, but the iPXE version will update when you update FOG.

@jflash Thank you for the video. I don’t see anything that jumps out at me that is wrong.
I created another kernel on my repo to try. https://github.com/rluzuriaga/fos/releases/tag/EXP_20250430

If that doesn’t work, maybe you could try disabling Securlty -> Memory Protection -> Execution Prevention.

If the memory protection setting doesn’t fix it, could you post the output of lspci -nn by booting into a linux environment on that computer? (Sorry I forgot the flags last time I asked)

@ingemedia We just released new experimental kernel/initrd. I included the r8126 drivers. I don’t have any devices to test with so would you be willing to test it and let me know?

@jflash We just released a new experimental kernel/init. Can you update both the kernel and initrd, they are versions 6.12.25 & 2025.02.0. Try those and let me know if it still kernel panics.

@robertkwild I don’t think so. A couple years ago, I imaged a Windows 11 Home machine without any license key and used the SetupComplete.cmd script without any issue.
It won’t run it if using an OEM key, though.

@robertkwild This isn’t a FOG issue at all but I would look into running your sysprep scripts in the SetupComplete.cmd file. I’ve never had any issues with admin privileges when running powershell scripts from it.

https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-a-custom-script-to-windows-setup?view=windows-11

@Jim-Holcomb Can you provide more information.

Can you image any other computer using that same Ethernet connection?
If so: Is this new Dell trying to PXE boot at all? Does it get to the >>Start PXE over IPv4. screen?
If so: What iPXE version are you using? What bootfile are you using in your DHCP setting?

@jflash Can you make sure that you are using the Linux kernel version 6.6.69 and Initrd 2024.02.9 for FOG.
If you are using those versions and it still kernel panics, please boot into a linux live image, then in the terminal enter lspci and post that output on here.

@ingemedia I will be working on a 6.12.x kernel soon and I will make sure to include the r8126 config.

@Erika I don’t want to release this in the official repo since this is just a testing kernel, so here is the link to the kernel on my forked repo. https://github.com/rluzuriaga/fos/releases/tag/EXP_20250110

You’ll have to manually install it since it isn’t on the official repo. This is how if you’ve never done it before.

1. SSH into your FOG server
2. cd /var/www/fog/service/ipxe
3. mv bzImage bzImage_original #Not necessary but recommended so you can revert if there are any issues
4. wget https://github.com/rluzuriaga/fos/releases/download/EXP_20250110/bzImage
5. chmod 644 bzImage
6. chown fogproject:www-data bzImage # For Debian based servers
   chown fogproject:apache bzImage # For RHEL based servers

@Erika I would like to try the newer 6.12 kernel to see if this issue would get resolved. I will have a kernel for you to try later today.

@jeje3346 Oh yes the other thing I forgot in my previous reply is that you need to have the FOG client installed on the computer so that the name change can happen.

If you are wanting to install the FOG client on your golden image, make sure that you disable the FOGService in the windows services. You can use this link for reference of how to do this correctly with sysprep. https://wiki.fogproject.org/wiki/index.php/FOG_Client#FOG_Client_with_Sysprep

@jeje3346 I have seen this issue when sysprep domains the computer through the unattend file. Once the computer is domained, FOG is not able to change the computer name. If this is the case, I would recommend you domain the computer through the active directory options in FOG or through a snapin instead of the unattend file.

I would also recommend you upgrade your FOG install to the latest stable release 1.5.10.1629 since there have been a lot of improvements done since version 1.5.9.