@Ryxn @george1421

No issues getting into the iPXE menu typically, the issue only appears to occur once you begin to deploy an image. Occasionally it will give this error while loading the iPXE menu: BzImage… (Connecting) and then loads my standard iPXE menu but with red text and a black background, any function chosen fails beyond this point. I’ve only ever seen this occur on these machines.

I’ve tried kernels from 6.1.22 up to 6.12.25 for testing purposes, the issue remains the same. I think you’re definitely correct with this being an issue with the network adapter not having it’s specific firmware available on the kernels.

The NIC shown in device manager is ‘Intel 82579LM Gigabit Network Connection’ - Hardware ID: PCI\VEN_8086&DEV_1502&SUBSYS_00008006&REV_04

I’ve ran both the commands suggested above while in the debugger and I received a ‘no such file or directory’ error for grep -i -e firm /var/log/syslog but grep -i -e firm /var/log/messages gave me the following output:

fogclient kern.info kernel: Spectre V2 : Enabling Restricted Speculation for firmware calls

I’ve managed to reproduce the issue while loading into the debugger, but when viewing /messages there is no errors apart from the one above.

I hope this helps, if you require any further information please let me know. TIA.

Hi all,

Firstly, thank you all for the huge amount of work you’ve put into this project it’s seriously impressive.

I’ve been deploying Windows using FOG Project for a few years now, but I’ve encountered an error that I haven’t seen before and it’s driving me insane.

FOG Version: 1.5.10.1639
Kernel Version: 6.1.22
Init Version: 2024.02.1
FOG Server OS: Debian 12
Storage Node OS: Debian 12

I use DNSMasq for the boot files, I’ve attached the config below (IP’s removed, but it’s configured to my server)

#Don’t function as a DNS server:
port=0

#Log lots of extra information about DHCP transactions
log-dhcp

#Set the root director for files available via FTP.
tftp-root=/tftproot

#The boot filename, server name, server ip address
dhcp-boot=undionly.kpxe,...**

#Disable re-use of the DHCP servername and filename fields as extra
#Option space. That’s to avoid confusing some old or broken DHCP clients.
dhcp-no-override

#inspect the vendor class string and match the text to set the tag
dhcp-vendorclass=BIOS,PXEClient:Arch:00000
dhcp-vendorclass=UEFI32,PXEClient:Arch:00006
dhcp-vendorclass=UEFI,PXEClient:Arch:00007
dhcp-vendorclass=UEFI64,PXEClient:Arch:00009

#Set the boot file name based on the matching tag from the vendor class (above)
dhcp-boot=net:UEFI32,i386-efi/ipxe.efi,...**
dhcp-boot=net:UEFI,ipxe.efi/ipxe.efi,...**
dhcp-boot=net:UEFI64,ipxe.efi,...**
dhcp-boot=net:BIOS,undionly.kpxe,...**
#PXE Menu. The first part is the text displayed to the user. The second is the timeout, in seconds.
pxe-prompt=“Booting FOG Client”, 1

#The Known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,

Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI

This option is first and will be the default if there is no input from the user.

pxe-service=X86PC, “Boot to FOG”, undionly.kpxe
pxe-service=X86-64_EFI, “Boot to FOG UEFI”, ipxe.efi
pxe-service=BC_EFI, “Boot to FOG UEFI PXE-BC”, ipxe.efi

dhcp-range=...**,proxy

The machine that I’m deploying Windows to is a Varipos 815s - the interface is labelled as: ‘IBA GE Slot 00C8 v1395’- I’ve having mixed success with these machines on exactly the same bios version, from the exact same ports. Some of them complete normally and the others display this error:

“No network interfaces found, your kernel is most probably missing the correct driver! Please check your network setup and try again”

It appears that one the kernel & init are loaded the interface just completely stops, along with the negotiation lights on the port. Does anyone have any suggestions to resolve this issue or point me in the right direction? TIA.