FOG Very Slow to Deploy Image - Lenovo Neo 50Q Gen 4

[george1421]

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

You are welcome to continue using the “OEM driver” kernel for now until I create a full upstream release.

What did you do here, did you fold in the realtek oem driver into the kernel build. I was looking at going this path for another open issue with a realtek 8125, where the oem driver solves a lot of the issues with the default universal drive 8169.

[rodluz]

@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

[george1421]

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

That is exactly what I did, I disabled the 8169 driver from the kernel config too.

Good going. That 8125 driver was originally in the linux kernel individually but then the driver was merged into the 8169 unified driver which has not kept up with the realtek hardware changes. I was getting lost trying to integrate a third party driver into the linux kernel. I could compile it as a module and add it to the init.xz but that is not a sustainable solution. If you have it integrated into the kernel for the 8169 (1GbE) and 8125 (2.5GbE) that should cover most of the common network adapters today from realtek (outside of the 10GbE stuff, but those haven’t hit the desktops yet).
Well done!

[Clebboii]

@george1421 @rodluz
Out of curiosity, when will this hit the production FOS image? Be handy to not need to purchase Dell Ethernet Adapters.

[rodluz]

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

[Clebboii]

@rodluz Absolutely, where can I find it?

[rodluz]

@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

[Clebboii]

Hi @rodluz,

Apologies for the late reply to this. Could you please provide me with the init.xz and bzImage for this experimental kernal?

[rodluz]

@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

[Clebboii]

Hi @rodluz

Just wanted to confirm that this update has worked. Now deploying my images in <5mins.

Thank you for your help.

[Quintin Giesbrecht]

Well, I have to admit, I opened this issue a while ago, and then didn’t really have time to play with it. I only have a handful of these machines, and while it’s a pain when I have to reimage one, I didn’t have time to spend a lot of time trying to figure this out. Well, today I had to reimage another one of them, and so just out of curiosity checked this thread again, and wouldn’t you know it, it seemed like the issue might be resolved…I updated the kernel, started imaging, and it is going in 5 minutes again!

Thanks so much for an amazing product and community!

Q