Subcategories

• FOG Problems

  Technical help directly related to FOG.
  9.1k
  Topics
  84.8k
  Posts

  G

  @Ryxn I checked and that nic has been in the linux kernel for several years.

  And secondly when you checked for missing firmware the kernel wasn’t complaining about missing something.

  Its a good thing you were able to get the error while in debug mode. Because that was going to be the next quest for you. To get the system when its behaving badly.

  So when you get it into debug mode and its complaining about no nic lets do the following.

  ip a s should show if the network interface has an ip address, I’m going to suspect no because it complained about it earlier in the boot process.

  lspci -k -nn | more Look through this list until you find the entry. The number in the square brackets will be what you posted earlier. [8086&1502]. See if the nic is visible to the kernel. AND if it is it should mention what kernel driver its using. I’ll give you a for example using my laptop.

  0000:00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection ( 13) I219-V [8086:15fc] (rev 20) Subsystem: Dell Ethernet Connection (13) I219-V [1028:0a22] Kernel driver in use: e1000e Kernel modules: e1000e

  lastly if everything looks good, kernel sees the nic, there is a kernel driver assigned. Lets see if time fixes your problem.

  When you ran the ip a s command it listed all of the network interfaces and if it has IP addresses. You will need to know the interface name for your network adapter. It may be something like eno1 or ens192, or something else. Get that device name.

  Now run this command /sbin/udhcpc -i $iface --now replacing the whole word $iface with the device name listed from the ip command. This will tell the network adapter to again poll for an IP address from your dhcp server. If it picks up an IP address this time, then time does solve your problem and you will need to look into your network configuration and make sure that port-fast or fast-stp is enabled on your network port.

• Hardware Compatibility

  Problems with specific computer models.
  699
  Topics
  8.3k
  Posts

  G

  @Donutsrule5

  OK lets see if we can boot from a usb drive. This tutorial will instruct you on how to build a usb boot image. https://forums.fogproject.org/post/69606 the google drive link below will take you to step 7 in the thread.

  https://drive.google.com/file/d/1psCrPVzBTvlakLkCMvhdoScAEZp1CKE6/view?usp=drive_link

  Once you build the usb boot drive, take the kernel and init.xz from your current version of fog and replace the ones on the flash drive with the ones in from the FOG server. The files are in /var/www/html/fog/service/ipxe directory.

  Once you have the usb drive ready, pxe boot into the grub menu on the flash drive, then go into debug mode. After several pages of text you need to clear with the enter key you will be dropped at a fos linux command prompt. If you can get that far then fos linux is OK and the problem is probably with ipxe or the handoff between the two.

  If you want to image with the flash drive, schedule the task in the fog server BEFORE you usb boot and select option 1 from the menu. If you get it out of sequence you will get an error that says something about Null. Basically its saying you don’t have a task scheduled on the fog server so there is nothing to do. Lets see if we can get it to boot this way.

• Windows Problems

  Technical help related to a Windows Problem.
  1.0k
  Topics
  8.2k
  Posts

  S

  @Almeida BitLocker is enabled in your master ? If yes, you should disable it. Enable it only on the final computer.

  We do have the BCD issue when enabling BitLocker on 24h2 image, we are running the same commands, but you are missing one.

  You need to set device partition=C: for the recover from hibernate entry too. The annoying part is that its ID is dynamic.

• Linux Problems

  Technical help related to a Linux Problem.

  719
  Topics
  6.2k
  Posts

  M

  Sorry for diging up this post.
  Just for us the solution was a missing package : gcc-aarch64-linux-gnu

• Mac Problems

  Technical help related to a Mac Problem.

  79
  Topics
  941
  Posts

  M

  @george1421 Hi,

  Thanks for your reply. Its strange. I am working with (almost exclusively) early 2012 hardware. My older Imacs 2009-2011 afaict pxe boot fine image with FOG w/o issue. The problem comes along when, I try to image our macbooks. They display different levels of progress before they flat out hang. I had one mbpx,y I’m almost sure it was a 3rd gen intel just can’t find it right now. I may be being processed to go out the door to our clients.

  Yes the 2019 verison of ipxe was executed from a boot of clonezill 3.1.x the version I would attempt to boot from ventory stick or from an imaged usb stick would display an error regarding not having efi capability and/or hang or return to the ventoy menu. If I just let them be long enough the MBP would just restart.

  So I did attempted to roll my own and ran into the same problem with the oobox downloadable iso/zip file. Hang… I am researching w/o much success with how clonezilla compiled their ipxe menu entry or how to just plain add efi capability to ipxe.iso/zip and burn it to a usb stick. I just am not knowledable enough to formulate a good question or find what I am looking for (cause I don’t know:))

  So thanks again for your reply. I have a large donations of older MBP’s coming just before the holidays and I would lik to be able to make it rain.

  Regards,

• General Problems

  General Developer questions relating to FOG.
  669
  Topics
  5.0k
  Posts

  F

  Hey there,
  we are using our Fog Server since a long time.

  Now with Windows 11 24H2 we experiencing some strange issue.

  after getting the image to the computer our postdownloadscripts start working, mounting the ntfs partition where windows resides and copying the drivers to a specific location.

  We have noticed, that with a new golden master (with audit mode) the mount of the ntfs partition isnt working anymore the right way. We noticed that as we are checking some specific files in the windows folder as it is x86 or x64 architecture. In debug mode we had trouble to manually mount the partition with the ntfs-3g drivers. So we cannot check or copy anymore the drivers into the partition.

  Bitlocker is disabled in the golden master as with oobe it cannot seal with it activated. So this cannot be the problem.
  Maybe Windows did something to the NTFS Partitions in their new Windows 11 ISO ?

  I also checked if the new filesystem (reFS) is active but we have a classic NTFS partition.

  Anyone has the same problems ? Or does anyone have a solution for it ? New NTFS-3G drivers for the PXE or something like that ?

  Florian