Stuck at EFI stub: Loaded intrd

[Rattenjunge]

Describe the bug
Using a MSI 650 Gaming plus wifi using its onboard network adapter. (newest bios, secure boot disabled, windows 11 fast boot disabled and power management for pcie disabled)
PXE works fine until I do one of 4 tasks.
Capture, host registration, deploying image or showing system information.
It works the first time, probably a second time, but after I do one of the tasks above often enough, it will be stuck at
EFI stub: Loaded intrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Measured initrd data into PCR 9

If this happens, PXE is not available in bios anymore and Windows 11 will not have an Ethernet adapter.
I have to flush cmos or cut power, shutdown PSU and wait. After a while the Ethernet adapter is working again.

But when it works, I can register the host, capture and deploy images without a problem.

To Reproduce
Steps to reproduce the behavior:

1. Load into ipxe.efi
2. Open System Information
3. repeat until stuck

Expected behavior
Not stuck.

Screenshots

Software (please complete the following information):

• FOG version 1.5.10.1673
• FOS kernel bzImage Version: 6.12.35, bzImage32 Version: 6.12.35, arm_Image Version: 6.12.35
• OS: Ubuntu 24.04.3 LTS

I hope this is here correct, if not please close or move to issues.

[sura008]

I’m also experiencing the “stuck” issue. On other systems, everything works fine, but I’m encountering problems specifically with the following hardware:

Processor: Intel® Core™ Ultra 7 265  
Motherboard/Base: Dell Pro Max Micro FCM2250 CTO BASE  
Motherboard/Base: Dell Pro Max Slim (FCS1250) CTO Base  
FOG Version: 1.5.10  
OS: Ubuntu 20.04.6 LTS

Any help or suggestions would be greatly appreciated. Thanks!

[mastacontrola]

Have you tried a newer/updated kernel? You should be able to update the kernel using the FOG Configuration Page -> Kernel Update and find the latest one. 1.5.10 is from years ago now and the kernel is likely very old. Now I'm not saying updating the kernel will definitely fix the problem, just that I vaguely recall and believe this is fixed in the latest version of the kernels? If it's not, at least we know it's still not fixed, and we are actively tryign to figure out how to address this. More information would be better though.

Thank you

[Rattenjunge]

"FOS kernel bzImage Version: 6.12.35, bzImage32 Version: 6.12.35, arm_Image Version: 6.12.35"
I used the most recent kernels FOG is providing on the web UI

[rluzuriaga]

I'm moving this issue to the FOS repo since it is since it is an issue with the kernel.

[rluzuriaga]

I'm working on an updated kernel/initrd release that will hopefully fix this issue.

[college-stjoseph]

Hi every one.

I’ve got the same problem with Dell Pro 16 PC16250. Only with deployment.

The PXE boot stuck at : EFI Stub: Loaded initrd from Linux_EFI_InitRD_Media_Guid device path

I’ve allready had this message with other models : Dell Latitude 3550 and Dell Optiplex 3080 SFF, but boot keep going and the deployment start.

But not with Dell Pro 16 PC16250

My server (debian 12.12) is up to date.
Fog is also up to date 1.5.10.1698
The kernel too : bzImage and init.xz version : 6.12.35 (july 2025 and september 2025)

I tried to change the DHCP (Debian too) file with snponly.efi : stuck too

I’ve tried older kernels : 6.1.89, 6.6.9, 6.6.49 : stuck too

In the BIOS, Secure boot and TPM are disabled

I’ve tried to add kernel arguments : acpi=off noapic nolapic pci=nomsi nomodeset intel_iommu=off iommu=off

But no success

PS : Thanks for all the job

[rluzuriaga]

@Rattenjunge @sura008 @college-stjoseph I have created a new test kernel https://github.com/rluzuriaga/fos/releases/tag/EXP_20250926
Can you try it out and let me know if it works please?

[Rattenjunge]

@rluzuriaga
I tested the new bzimage.
The error is still there, but it took me a while to get there. Just repeating opening "system information" didn't get me stuck this time. I had to boot into windows twice until I'm stuck again. After that, the ethernetadapter is again not available.

[rluzuriaga]

@Rattenjunge Interesting. I just reread the original issue and I'm starting to think this may be a weird Hibernate/fast boot issue. I am not ruling out that this can't be fixed by some kernel changes though.
Can you disable hibernate on Windows and fast boot from the UEFI menu, then try the previous kernel please?
If you still have the same problem, please try this new kernel https://github.com/rluzuriaga/fos/releases/tag/EXP_20250927

[Rattenjunge]

@rluzuriaga forgot to write it, but hibernate/Fastboot was disabled. I will try your new kernel as soon as I'm back at the office. :)

[college-stjoseph]

It seems that I have a solution.
Could the ipxe.efi file be the problem ?
In the Dell Pro 16, I have disabled the WLAN (Connection > WLAN), the PC find the network perfectly and deploy perfectly too.
After deployment, enabled the WLAN and all is OK

I remind my configuration :
Debian 12 (upto date)
FOG : 1.5.10.1698
Kernel : 6.12.35

Before FOG update I was able to deploy Dell Pro 16 (very slowly, but I had it).

And since my update and problem, I try many things with kernels and inits, but nothing with the ipxe files.

[Rattenjunge]

@rluzuriaga
I tried your new bzImage.
This time the result was different. I after a few restarts and "checking system info"s I realized, that I did not have any internet adapter anymore in windows, but pxe was still available in bios and I could still boot into ipxe + still could read the system informations. The weird part is, after windows was telling me that I did not have any internet adapter, pxe showed up with an empy mac adress. Picture billow.

Hope this helps figuring out the issue.

[rluzuriaga]

@college-stjoseph @Rattenjunge what boot file are you using? ipxe.efi, snp.efi, snponly.efi, etc?
On my newer HP devices I had to move away from ipxe.efi and use snp.efi since I was having weird issues with iPXE similar to these.
Please try using snp.efi or snponly.efi if you aren't already doing so.

[Rattenjunge]

I will try snp.efi. I'm using ipxe.efi currently.