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

[george1421]

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

A friend of mine have added the correct driver into the bzimage file

Can you explain this in a bit more detail? Lets see if we can help everyone do better, please.

[olivier.bonnici]

@Clebboii Here the link
https://1fichier.com/?la6xpv8145lvfano9t98

[olivier.bonnici]

@george1421 I tell me i recompile the kernel using https://kernel.org/ and the fog procedure.
Link to the modified bzimage
https://1fichier.com/?la6xpv8145lvfano9t98

[Clebboii]

@olivier-bonnici That link does not work for me. Can you please provide it another way (Google Drive open link or GIT etc.)?

[olivier.bonnici]

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

(Google Drive open link or GIT et

https://drive.google.com/file/d/1LCmvgmUa8YvbG1fE95Yn_lDBhFXLs8At/view?usp=sharing

[rodluz]

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

@rodluz Unfortunately still no better:

@olivier-bonnici I cannot test with link below as you have not allowed me access.

[olivier.bonnici]

@Clebboii Acces granted.

[Clebboii]

@olivier-bonnici This kernel works:

Can you please describe what has changed so that @rodluz can make changes for next release?

[rodluz]

@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

[rodluz]

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

@rodluz Success!

As we know the pre-release kernel did not work:

However the experimental OEM driver did work:

Let me know if you need any further tests

[rodluz]

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

[olivier.bonnici]

@george1421
Here the command.

sudo apt install git build-essential flex bison libelf-dev
git clone https://github.com/FOGProject/fos
cd fos
./build.sh --kernel-only --arch x64
wget https://www.kernel.org/pub/linux/kernel/v6.x/linux-6.14.9.tar.gz
tar xzf linux-6.14.9.tar.gz
cd linux-6.14.9/
git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
git clone https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
make mrproper
wget -O .config https://github.com/FOGProject/fos/raw/master/configs/kernelx64.config
apt install build-essential fakeroot dpkg-dev perl libssl-dev bc gnupg dirmngr libncurses-dev libelf-dev flex bison lsb-release rsync dwarves
make menuconfig
make -j $(nproc) bzImage
cp arch/x86/boot/bzImage /home/ckern-linux/Bureau/bzImageReg6149

[george1421]

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

tar xzf linux-6.14.9.tar.gz

Ah that explains the difference. You didn’t just rebuild the kernel you jump to the next version. The FOG developers typically only use long term supported kernel. Currently the latest long term kernel is 6.12.x, you used a development kernel 6.14.x which is not EOL (just means fixes and updates will not happen in this branch).

It looks like whatever was causing the slowness was resolved in 6,14.x and later versions of the linux kernel. Thank you for the clarification.

[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!