1. Home
  2. Technical Help

Subcategories

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

    In the start of the week same of our PCs suddenly got an error. After the FOG start menu we got this error:

    Starting bootmgfw.efi Using load options '' Secure Boot validation failure loading bootmgfw.efi!

    Our PC support told us to update our BIOS because of new signatures (Starting directly on Windows without FOG in between gave us also a Invalid signature error). After the update we can boot into Windows, but now we have problems booting into FOG.
    It’s loading the NBP file and iPXE is starting, then we getting the following error

    iPXE 1.20.1+ Configuring (net0 xx:xx........) .......... No configuration methods succeeded (http://ipxe.org/040ee186) Configuring (net0 xx:xx........) .......... No configuration methods succeeded (http://ipxe.org/040ee186)

    After that I go into the PXE shell and try typing dhcp. This gives me an “OK” always after the 2nd try. So im again in the FOG starting menu and want to boot into Windows and I’m getting the following error:

    http://......... refind.conf ......... Connection times out (http://ipxe.org/4c0a6092) Could not boot: Connection timed out (http://ipxe.org/4c0a6092) Could not boot: Connection timed out (http://ipxe.org/4c0a6092)

    Our setup is:
    Your version of FOG is up to date.
    You’re running the latest stable version: 1.5.10
    Custom signed files with this tutorial: https://forums.fogproject.org/topic/15888/imaging-with-fog-and-secure-boot-poc
    Changed from ipxe.efi to snponly.efi didn’t helped.

    Someone knows what’s the problem here and how to solve it? Do I need to update the FOG server or just update the pxe file?

    Thanks in advance

  • 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
    G

    Hi Again guys

    I have some news about this problem.
    I found a work around.

    I change the file d1.fixed_size_partitions deleting the recovery Windows partition. This change generated and error when I made the deploy image in Client PC.
    But if I cancel the job in the CLI fog server and reset the client machine after fog show the error
    It boot ok.

    I’ll continue reading …
    Thanks

  • Technical help related to a Linux Problem.

    726 Topics
    6k Posts
    J

    Ok so I now have a second system with the EXACT same issue. I purchased a Dell Precision 7875 which has 2 on-board nics. I updated our dhcp server to issue an IP address for one of the two NICs. With the system connected to that interface I PXE booted the system. The first stage of the fog shows as it notices the system is not registered and asking whether I would like to register the system. Yet once I say do full registration that’s it it will not proceed further.

    So similar to the issue that I’ve raised prior with multiple NICs and @george1421 suggested I PXE booted the system again but went into DEBUG mode. Well as it appears the unused MAC address is now showing up on the interface that I had configured to connect to the network. Seeing that I did not assign an IP address to the second mac address the system would not proceed any further. The odd thing is that BOTH interfaces show up having the same mac address. It seems that there’s an issue with the FOS with newer Dell systems with multiple NICs.

    If I disable one of the two NICs in the BIOS, and do the re-imaging process everything works fine…

    Really looking for a fix for this…

    Cheers

    Jason Naughton

  • 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.
    683 Topics
    5k Posts
    raulR

    @Tom-Elliott Do the values in .fogsettings get applied only the first time installfog.sh is executed, or are they supposed to be applied on every subsequent run as well?
    In my case, updating .fogsettings after the initial installation doesn’t seem to change anything, so I want to confirm whether this is expected behavior or if I’m missing something.

110

Online

12.5k

Users

17.5k

Topics

156.3k

Posts