Subcategories

  • Technical help directly related to FOG.
    9k Topics
    86k Posts
    Tom ElliottT

    @Matthiman Your issue appears similar to an issue that’s being described here:
    https://forums.fogproject.org/topic/18213/version-1-6-0-beta-3187-ipxe-2-0-0-x-problems

    Though they seem to indicate changing to an older bootfile (snponly.efi/ipxe.efi whatever) worked so it’s not a kernel/init issue that’s happening causing this to occur.

    This may be what’s happening with everyone in this thread as well, but the first image that I see from Fog_Newb looks more like what I’d expect where there’s not enough ram available to load.

  • Problems with specific computer models.
    713 Topics
    8k Posts
    Tom ElliottT

    @rpycroft That’s the confirmation I needed, thank you. 1.2 to 6.5 GB/min is
    the fix working. The change is merged now, so it’ll be in the next kernel
    release rather than something you have to keep hand-installing.

    Two corrections from my end.

    First, tx checksumming: ko was never broken. That line is about jumbo frames –
    it’s the driver saying this chip can’t do TX checksum offload if you enable
    jumbo, and at a normal 1500 MTU it never applies. It’s printed based on the
    chip model alone, so you’ll still see it on the new kernel. Don’t let it worry
    you when you spot it again. Your ethtool output was very likely the same before
    the swap; there was nothing to fix there.

    Second, I got two details wrong in the setpci commands I posted. My apologies.
    The write should be masked so it only touches the two ASPM bits – as I wrote
    it, it would have cleared the whole Link Control register, including the common
    clock configuration, which you don’t want to disturb on a live link. And the
    order was backwards: the spec wants L1 switched off at the NIC before the root
    port, not the other way round.

    Reading the current state (this part was fine):

    setpci -s 02:00.0 CAP_EXP+10.w setpci -s 00:1c.5 CAP_EXP+10.w

    Only the last hex digit matters:

    0 4 8 C -> ASPM off 1 5 9 D -> L0s 2 6 A E -> L1 3 7 B F -> L0s + L1

    And clearing it, NIC first, masked to the ASPM bits:

    setpci -s 02:00.0 CAP_EXP+10.w=0000:0003 setpci -s 00:1c.5 CAP_EXP+10.w=0000:0003

    If you did already run the originals, nothing you’ve reported suggests any harm
    came of it, and a reboot clears the lot either way.

    No pressure on this next bit at all – the fix is confirmed and merged, and
    this doesn’t gate anything. But if you ever have one of those 3070s spare, the
    read-only pair above run once under UEFI and once under legacy would tell us
    why the two differ. My theory is the Dell firmware enables L1 on the UEFI
    path and leaves it off under CSM, which would explain everything you saw, but
    that’s still me inferring rather than knowing. Genuinely optional – if it’s
    easy, great, and if not, don’t spend your time on it.

    Thanks again for testing this so quickly.

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

    @Tom-Elliott

    I pulled latest dev-branch version 1.5.10.1856, re-run installer and snapins are working again.

    Thank you very much for help.

  • Technical help related to a Linux Problem.

    730 Topics
    6k Posts
    C

    @Numa09
    I had the same problem with a TP-Link switch. The model was a TL-SG2428P, and the FOG client would get stuck at:

    “Running post init scripts…”

    There were no error messages on the server, and the server firewall was disabled.

    After seeing your comment, I disabled the DoS protection feature on the switch, and FOG started working normally.

    Thank you, man!

  • Technical help related to a Mac Problem.

    81 Topics
    943 Posts
    Bristow 0B

    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.
    686 Topics
    5k Posts
    Bristow 0B

    @Tom-Elliott

    I’ve updated my FOG to the stable release and also updated my script with the following three lines, and everything’s fine – the database has been backed up successfully, it’s perfect!

    fogApiToken="XYZ=" fogUsrToken="ZYF" curl -ik -X GET "http://$fogServerAddress/fog/system/export" -H "fog-api-token: $fogApiToken" -H "fog-user-token: $fogUsrToken" -o $backupDir/mysql/fog.sql 2>>$backupDir/logs/error.log 1>>$backupDir/logs/progress.log 2>&1

    Thanks again for all your hard work on the FOG project!

97

Online

12.7k

Users

17.6k

Topics

156.9k

Posts