Subcategories

• FOG Problems

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

  J

  This is what i get to after changing the boot file. I have updated the kernel and still can not get past this. We have about 200 of these Yogas and when the bios gets updated we are no longer able to boot to fog. I have verified secure boot is disabled and the MAC pass through is disabled.

  fog error.png

• Hardware Compatibility

  Problems with specific computer models.
  692
  Topics
  8.2k
  Posts

  B

  Same thing here with this laptop. We’ve also tested the experimental kernel but same problem.

  Thanks 🙂

• Windows Problems

  Technical help related to a Windows Problem.
  991
  Topics
  8.1k
  Posts

  T

  I was unable to resolve this issue with pnputil using a cmd.exe script.

  I noticed that the problem was also present on another FOG installation managed by other system administrators.

  I assume (perhaps wrongly) that the problem is linked to an ANSI/UTF encoding issue. If someone using another language manages to run pnputil.exe in a cmd.exe script, report it here.

  I was finally able to resolve this driver deployment issue using powershell. I’m leaving a sample code (install of a driver named usbblstr.inf) in case it helps someone.

  New-Item -Path "c:\" -Name "drivers" -ItemType "directory" -Force Copy-Item -Path "usb-blaster" -Destination "C:\drivers" -Recurse Start-Process -FilePath "pnputil.exe" -ArgumentList "/add-driver C:\drivers\usb-blaster\usbblstr.inf /subdirs /install" -RedirectStandardOutput "$env:tmp\usb-blaster-install.txt" -RedirectStandardError "$env:tmp\usb-blaster-err.txt"

  Sincerely,

  Julien

• Linux Problems

  Technical help related to a Linux Problem.

  715
  Topics
  6.2k
  Posts

  J

  I am looking for a way to exit from a FOG task to a specific GRUB menu option on the client machine.
  My goal it to find a way to achieve a one time iPXE boot option on a legacy GRUB Linux machine by copying the iPXE kernel to the /boot folder on the client machine, then adding a grub menu entry for iPXE so that I have a grub menu.lst file similar to

  default 0 timeout 0 title BIOS iPXE Boot root (hd0,0) kernel /boot/ipxe.lkrn title openSUSE - Kernel 3.1.0-1.2 root (hd0,0) cedarview_gfx.modeset=0 kernel /boot/vmlinuz splash=silent quiet initrd /boot/initrd

  I have tested this and it works well , but I end up in a boot-loop and I can not see a method to automatically exit a FOG session that would allow me to move on to the next menu option as all EXIT options I have tried so far end up back at the GRUB menu with a default of iPXE

  Is there a way to use a custom GRUB_EXIT_TO_MENU_OPTION or maybe some better way to achieve this ?

  So far I have tried the following exit options
  GRUB - finds the local GRUB , but oots to the default iPXE option
  GRUB-FIRT-HDD -same as above , - I have the ipxe bootloader and menu option on the HDD
  REFIND-EFI - this machine is very legacy and did not manage to load REFIND neither from FOG, nor a rEFInd bootable USB for testing ( this USB was tested on more modern machines and did work)
  EXIT - Still ends up back at the same grub menu with iPXE as default

  I can see that there are other ways to booting to iPXE ( eg bootable USB , BIOS option etc), but this method of adding the files to the main HDD would allow me to do all this remotely, without the need for access to the machine, e.g. over ssh and the basic concept is working well. I just am not sure how to solve the boot loop EXIT issue

• 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.
  656
  Topics
  5.0k
  Posts

  G

  On ubuntu 22.04.5 LTS
  running version: 1.5.10.41

  I’ve been capturing and deploying all week as we upgrade PCs. I’m not sure why deploying to this box is causing a problem when I’ve pushed images to a dozen boxes just like this one. I can’t think of a single thing that’s changed.

  e792e228-d10c-4032-98a9-3d02e614dff3-20250214_131112.jpg

  I followed this, but my fog server seems to check out.
  https://forums.fogproject.org/topic/16585/bin-fog-upload-doesn-t-exist

  root@ubu-fog2:~/fogproject/bin# ls -la /images/dev
  total 20
  drwxrwxrwx 5 fogproject fogproject 4096 Feb 14 14:49 .
  drwxrwxr-x 30 fogproject fogproject 4096 Feb 14 14:49 …
  drwxrwxr-x 2 fogproject fogproject 4096 Mar 21 2019 080027fac68c
  drwxrwxr-x 2 fogproject fogproject 4096 Feb 2 2024 6805ca23db0b
  -rwxrwxr-x 1 fogproject fogproject 0 Feb 14 15:41 .mntcheck
  drwxrwxr-x 2 fogproject fogproject 4096 Mar 21 2019 postinitscripts

  root@ubu-fog2:~/fogproject/bin# showmount -e 127.0.0.1
  Export list for 127.0.0.1:
  /images/dev *
  /images *
  root@ubu-fog2:~/fogproject/bin#

  Not sure what happened. Any direction on how to resolve this would be great.