Subcategories

• FOG Problems

  Technical help directly related to FOG.
  9k Topics

  86k Posts

  K

  @Tom-Elliott
  Scheduled Power Management Task is not working
  a03ab1c4-b08b-4125-9907-0453e57feffa-grafik.png

  Maybe it’s a Windows bug; I’ve often had to shut down not just once, but two or three times with 24H2 LTS.

  But none of the 36 + 25 student computers are shutting down.

• Hardware Compatibility

  Problems with specific computer models.
  713 Topics

  8k Posts

  R

  @Tom-Elliott

  Thanks so much for your help with this. Happy to feed back any info I can so please do let me know if there’s anything else you need me to test. Will be on annual leave for a couple of weeks after this and have no access to the systems but I think this confirms your suspicion. Please see results below from a Dell OptiPlex 3070:

  Addresses on this machine:

  NIC: 01:00.0 (Realtek RTL8168h)
  Root port: 00:1c.0

  UEFI mode:

  setpci -s 01:00.0 CAP_EXP+10.w = 0142 (last digit 2 = L1 enabled)
  setpci -s 00:1c.0 CAP_EXP+10.w = 0c42 (last digit 2 = L1 enabled)

  Legacy/CSM mode:

  setpci -s 01:00.0 CAP_EXP+10.w = 0040 (last digit 0 = ASPM off)
  setpci -s 00:1c.0 CAP_EXP+10.w = 0c40 (last digit 0 = ASPM off)

  Dell’s UEFI firmware enables L1 on both the NIC and root port. The Legacy/CSM path leaves both off. The only difference between the two readings is those two ASPM bits. Everything else in the register is identical.

  Thanks for the nudge to run these. Anything else needs testing please do let me know. We love using FOG and it’s invaluable in our set of schools that we work in at least so please do keep up the great work!

• Windows Problems

  Technical help related to a Windows Problem.
  1k Topics

  8k Posts

  V

  What version of FOG are you running?

• Linux Problems

  Technical help related to a Linux Problem.
  730 Topics

  6k Posts

  M

  @JasonNaughton

  Hi, I noticed that this was unresolved after so long. Wonder if you have solved it?
  I recently stumbled across the man page for dhcpcd.conf. In there is a denyinterfaces (pattern) should solve the issue for you. It tells dhcpd to ignore the nic interfaces listed in pattern. Just was wondering if you found the fix otherwise hope this helps.

• Mac Problems

  Technical help related to a Mac Problem.
  81 Topics

  943 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 Problems

  General Developer questions relating to FOG.
  688 Topics

  5k Posts

  A

  @JJ-Fullmer said in PXE does not load in EFI mode.:

  actually reading the claude output looks like you’re actually pointing to secureboot/ipxe.efi for option 67. Switch that to either secureboot/snponly-shimx64.efi or secureboot/ipxe-shimx64.efi and that may do the trick

  I’ve tried everything, absolutely everything from the tftpboot folder.

  @JJ-Fullmer said in PXE does not load in EFI mode.:

  That reframes the problem — you’re not stuck at “PXE won’t start,” you’re stuck at “NBP won’t load or won’t run.”

  Yes, that’s right.
  Since the computers that only work in legacy mode have no issues at all — they work flawlessly. I’ve been using them for several years now.

  @JJ-Fullmer said in PXE does not load in EFI mode.:

  Please re-run on the FOG server (192.168.65.35) with:

  Yes, I’ll continue conducting experiments nearby and test the team.

  @JJ-Fullmer said in PXE does not load in EFI mode.:

  Settings → Advanced → Integrated Peripherals

  LAN Option ROM: Enabled
  Network Stack (may be its own menu entry depending on BIOS revision): Ipv4 PXE Support: Enabled, Ipv6 PXE Support: Disabled

  Thanks to this parameter, I managed to get everything done.
  I’m very grateful for the help, but in the future, once things calm down a bit, I’ll continue to figure out why nothing works in EFI.

  @JJ-Fullmer said in PXE does not load in EFI mode.:

  also, silly question, but is this a problem just with this motherboard? Other devices pxe boot fine?

  The problem is with the EFI mode. It doesn’t matter which board.
  Legacy works without any issues.
  I just couldn’t find out how to switch the network card to Legacy mode on this motherboard.

  @JJ-Fullmer said in PXE does not load in EFI mode.:

  echoing the question if what version you’re on?

  version fog 1.5.10.2253

  @Tom-Elliott said in PXE does not load in EFI mode.:

  That said, what version of FOG are you running? You said a customized FOGProject, what exactly do you mean?

  I apologize, translation difficulties. Fog is entirely native, the version is indicated above.
  version fog 1.5.10.2253

  I personally don’t want anything from the developers.
  Excuse me.
  I’ve been using fog for about 3–5 years now.
  I ran into a problem where I couldn’t switch the network card on the motherboard to legacy mode.
  And the EFI mode hasn’t worked for me since a couple of years ago, and it still doesn’t work after the fog update.
  For now, I’ve managed to get by by doing what was suggested here — switching the network card to legacy mode.