Subcategories

• FOG Problems

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

  G

  @aurfalien said in Mellanox ConnectX 3 imaging issues.:

  So all good here.

  Did FOS Linux have the driver enabled for that 10GbE card (i.e. were you able to image with FOG once you got past the iPXE menu)?

  FWIW: For uefi mode snp.efi or snponly.efi should work if undionly.kpxe worked in bios mode. I’m saying it should because ConnectX3 is a somewhat older card (circa 2017/2018).

• Hardware Compatibility

  Problems with specific computer models.
  699
  Topics
  8.3k
  Posts

  D

  I would like to hopefully piggy back off this thread because I am getting the same error in the screenshot when trying to image or register the machine, but if I need to create a new thread I will.

  I have some Dell Pro 13 Plus with Intel Core Ultra 5 processor and get this same error. I have tried the current master branch 1.5.10 with kernel 5.15.93 and also tried master branch 1.5.10 with 6.12.25 kernel. I then tried the dev-branch 1.5.10.1667 with no luck and then did dev-branch with kernel 6.12.35 with no luck.

  Can anyone recommend some other things to try? I’m running out of ideas and time. Any ideas or help is greatly appreciated.

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

  S

  @Tom-Elliott I fixed it by directly removing the dirty flag using Linux. sudo ntfsfix -d /dev/nvme...

  We need to redo our golden image, so we will check at that time if we still get the same behavior.

  Thx for the help !