1. Home
  2. Technical Help

Subcategories

  • Technical help directly related to FOG.
    9k Topics
    85k Posts
    J

    Hello!
    I’m trying to capture a Windows 11 base image from an XCP-ng VM. The VM will boot to the FOG menu, and I can select the desired option (Full host registration), but after loading bzImage and init.xz, the VM hangs on

    EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Measured initrd data into PCR 9

    I’ve tried a list of different kernel versions:

    5.15.93 5.15.98 6.1.22 6.1.89 6.6.49 6.6.69 6.12.25 6.12.35 The experimental kernel listed here: https://github.com/FOGProject/fos/issues/108

    None have allowed the VM to get any further. What else should I be trying?

    Other devices are able to image successfully. We deploy laptops to staff and students, and all are imaging as expected.

    System info:
    FOG server is running AlmaLinux 9.5, in a VM that was migrated from ESXi to XCP-ng.
    FOG version is 1.5.10.15
    XCP-ng hosts are Dell PowerEdge R630. 2x Intel Xeon E5-2660v3, 128GB RAM
    Windows 11 VM has 2 CPUs, 4GB RAM, 64GB disk

    Thanks for your time!

    Screenshot 2026-03-17 092817.png

  • Problems with specific computer models.
    710 Topics
    8k Posts
    M

    @dimoura

    Hello!

    Do you have Secure Boot enabled?

    I worked with this Dell Machine about 6 months ago and don’t have it with me now.

    So here it goes.

    Ensure secure boot is disabled. You will need to re-enable it for Windows 11 to work., You need to ensure your SATA mode setting is set to “AHCI”. - If you have “RAID” selected (which was the default from the Dell Machines I tried) it will not work. If you have legacy IPv4 PXE booting that would work best, newer computers no longer have a legacy PXE boot, but use UFEI IPv4 PXE booting. Check if that is enabled.

    Otherwise, check what bzImage files you are using. The bzImage files have the linux kernel drivers which I think I used the latest stable ones I could find. These are placed in /var./www/html/fog/service/ipxe

    There are 4 files in there which need to be there
    bzImage
    bzImage32
    init.zx
    init_32.zx

    Or others depending on what CPU architecture your machines use. These are available on the following URL
    https://github.com/FOGProject/fos/releases

    I found that some work better than others as the FOG project is maintaining their FOS releases and adding computers. It is possible that one you are using simply does not have the drivers for the PC you are using. I would back up these files before updating these to ensure your older machines can PXE when updating your FOS (fog OS).

    Matt

  • Technical help related to a Windows Problem.
    1k Topics
    8k Posts
    K

    Hi everyone,

    I’m struggling with a specific PXE booting issue on a Dell Pro Tower Plus QBT1250 equipped with an Intel® Ethernet Connection (19) I219-LM (Windows 11).

    The Problem:

    When I shut down the PC from the BIOS/UEFI menu (or via a hard power-off), I can wake it up via WOL and it successfully enters the PXE boot sequence.

    However, when I shut down the PC from Windows 11, WOL still works (the PC turns on), but it skips PXE completely and boots straight back into Windows.

    What I’ve already tried:

    Windows Fast Startup: Disabled in Control Panel.

    BIOS Settings: “Deep Sleep Control” is Disabled. “UEFI Network Stack” is Enabled. PXE is first in the boot order.

    NIC Driver Settings (Intel PROSet):

    Disabled “Ultra Low Power Mode” (ULP).

    Disabled “Energy Efficient Ethernet” (EEE).

    Disabled “ARP Offload” and “NS Offload”.

    Set “Wait for Link” to “Enabled”.

    Unchecked “Allow the computer to turn off this device to save power” in Power Management.

    Registry: Tried PlatformAoAcOverride = 0 and PnPCapabilities = 24.

    The Observation:
    It seems that Windows 11 leaves the I219-LM in a “D3” low-power state that doesn’t fully reset the PHY layer during a WOL trigger, causing the UEFI Network Stack to ignore the NIC during the boot process. Only a “cold” boot or a reboot (sometimes) allows PXE to initialize.

    Has anyone encountered this with the newer I219-LM (v19) revisions? Is there a specific Intel driver version or a hidden “Shutdown Wake” registry key that forces the NIC to a clean state for PXE after a Windows shutdown?

    Any help would be greatly appreciated!

    Regards, Krzysztof

  • Technical help related to a Linux Problem.

    727 Topics
    6k Posts
    H

    Hello,

    I’ve ran into a problem. When upgrading from Debian 12 to Debian 13 I no longer can get to the webpage for fog. I get a 503 service unavailable. After seeing that I decided to re-run the installer to see if that would help but then I get the following dependency conflicts and was wondering if anyone has ran into this yet with Debian 13 Trixie.

    The following information may help to resolve the situation:

    The following packages have unmet dependencies:
    systemd-sysv : Conflicts: initscripts but 3.14-4 is to be installed
    Conflicts: insserv but 1.26.0-1 is to be installed
    Conflicts: startpar but 0.66-1 is to be installed
    Conflicts: sysv-rc but 3.14-4 is to be installed
    Conflicts: sysvinit-core but 3.14-4 is to be installed
    sysvinit-core : Conflicts: systemd-sysv but 257.9-1~deb13u1 is to be installed
    Recommends: orphan-sysvinit-scripts but it is not going to be installed
    E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
    E: The following information from --solver 3.0 may provide additional context:
    Unable to satisfy dependencies. Reached two conflicting decisions:

    sysvinit-core:amd64 is not selected for install because: systemd-sysv:amd64 is selected for install systemd-sysv:amd64 is available in versions 257.9-1~deb13u1, 257.8-1~deb13u2
    [selected systemd-sysv:amd64=257.9-1~deb13u1 for install] sysvinit-core:amd64 Conflicts systemd-sysv
    [selected systemd-sysv:amd64=257.9-1~deb13u1]
    For context, additional choices that could not be installed: In systemd-sysv:amd64 is available in versions 257.9-1~deb13u1, 257.8-1~deb13u2: systemd-sysv:amd64=257.8-1~deb13u2 is not selected for install sysvinit-core:amd64 is selected for install because: sysv-rc-conf:amd64=0.99-10 is selected for install sysv-rc-conf:amd64 Depends sysvinit-core

  • Technical help related to a Mac Problem.

    80 Topics
    942 Posts
    B

    Hello everyone,

    As I work at a secondary school, I was able to get hold of some Catalina iMacs (iMac 14.3).
    I already use FOG to deploy Windows and Linux images on PCs.

    I would like to deploy a LinuxMint image on these iMacs.

    However, I am unable to boot into PXE on them with FOG, and I do not know what is wrong.

    I modified my DHCP server as follows:

    ## FOG class "UEFI-32-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006"; filename "i386-efi/ipxe.efi"; } class "UEFI-32-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002"; filename "i386-efi/ipxe.efi"; } class "UEFI-64-1" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007"; filename "ipxe.efi"; } class "UEFI-64-2" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008"; filename "ipxe.efi"; } class "UEFI-64-3" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009"; filename "ipxe.efi"; } class "Apple-Intel-Netboot" { match if substring (option vendor-class-identifier, 0, 14) = "AAPLBSDPC/i386"; option dhcp-parameter-request-list 1,3,17,43,60; if (option dhcp-message-type = 8) { option vendor-class-identifier "AAPLBSDPC"; if (substring(option vendor-encapsulated-options, 0, 3) = 01:01:01) { # BSDP List option vendor-encapsulated-options 01:01:01:04:02:80:00:07:04:81:00:05:2a:09:0D:81:00:05:2a:08:69:50:58:45:2d:46:4f:47; } elsif (substring(option vendor-encapsulated-options, 0, 3) = 01:01:02) { #BSDP Select option vendor-encapsulated-options 01:01:02:08:04:81:00:05:2a:82:0a:4e:65:74:42:6f:6f:74:30:30:31; # filename "i386-efi/ipxe.efi"; filename "snp.efi"; } } } class "Legacy" { match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000"; filename "undionly.kkpxe"; } ### END FOG

    I tested ipxe.efi in 64-bit and 32-bit, as well as snp.efi, but it still doesn’t work. I get some kind of spinning planet when I try to boot.

    I admit I don’t fully understand the documentation page: https://wiki.fogproject.org/wiki/index.php/FOG_on_a_MAC

    Thanks in advance!

  • General Developer questions relating to FOG.
    684 Topics
    5k Posts
    AUTH IT CenterA

    @astrugatch we have firewalld but you can make the adjustments… some ports have been changed from the initial setup due to network restrictions.

    - name: FOG_Services short: FOG Server network rules description: >- For FOG Server to handle boot, image and various tasks on workstations sources: - SUBNET_IPS allow_icmp: - echo-request - echo-reply services: - ftp - http - mountd - nfs - rpc-bind - tftp ports: - { port: 20048, proto: tcp } # nfs - { port: 20048, proto: udp } # nfs - { port: "35350-36350", proto: udp } # tftp - { port: "49512-65532", proto: udp } # multicast

168

Online

12.6k

Users

17.5k

Topics

156.3k

Posts