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