Categories

  • 12k Topics
    114k 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

  • Get the latest news on what's happening.
    184 Topics
    825 Posts
    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    2k Topics
    19k Posts
    Cire3C

    @youzersef Ok, see how long it takes me to get back on a project…lol

    I did some more looking, and found yes, the GUI will re-write the dhcp config file. However I did some more reading and I guess services.inc determines what is written by the GUI.

    Sorry, not a CLI guy, and I love the quick and easy edits, viewing issues that the GUI provides. Like Fog ! However my servers are headless…lol

    Anyway, looking that route now, and will update if I find how Negate wants services edited so when it reboots, DHCP will remain.

    Determined 🙂

    Any thank you everyone here . This place has always been great for information !

  • Report bugs, request features, or get the latest progress.
    2k Topics
    21k Posts
    M

    Okay - So what killled this installation was the fact a 1.5.9 csv load was imported into my 1.5.10.1698 FOG - this killed a bunch of features and I eded up having to reinstall.

141

Online

12.6k

Users

17.5k

Topics

156.3k

Posts