Just figured this has been added already thanks to @Piotr86PL’s pull request in August (which I had obviously forgotten about, nevermind).

@JJ-Fullmer It’s good you bring this point up. We get posts in the forums every now and then but it’s very hard to estimate how often this really happens in the wild as we have no numbers of rEFInd working properly.

Adding more options is a good idea either way as it doesn’t hurt us and might help people.

Personally having used grub2 to PXE boot I will get onto that and see what’s the best way to add this to FOG.

@redbob said in Task taking too long time to begin after FOG Menu:

r8169

120 seconds sounds like a timeout (wait) for the initialization of the card.

@rosscaramell The type of disk you’re using doesn’t cause accounts to be randomly made in Windows. This isn’t related to FOG in the slightest.

@Tom-Elliott said in Could not boot:

ing your storage node IP to

I had the same problem starting from 1.4.0-RC-2 . Added another storage node with the fog-server ip and some fantasy user/password -> works

Hi,
try setting this parameter in /var/www/html/fog/service/ipxe/refind.conf:

# Delay for the specified number of seconds before scanning disks. # This can help some users who find that some of their disks # (usually external or optical discs) aren't detected initially, # but are detected after pressing Esc. # The default is 0. # scan_delay 5

and, if you need, this:

# Timeout in seconds for the main menu screen. Setting the timeout to 0 # disables automatic booting (i.e., no timeout). Setting it to -1 causes # an immediate boot to the default OS *UNLESS* a keypress is in the buffer # when rEFInd launches, in which case that keypress is interpreted as a # shortcut key. If no matching shortcut is found, rEFInd displays its # menu with no timeout. # timeout 5

@sebastian-roth

Hi sorry, I couldn’t answer any sooner.
“Nevertheless we ought to try out using the SNP binary (debug enabled - DEBUG=snp:3,nii:3 to start with). So find 01_snp.efi here. Just give it a try and post pictures or video. Make sure when you take those to place the camera or phone on a stack of books in front of the screen so we have a good picture.”

Here you go, not much to say from my side but here goes: video

Thanks!

Have you checked what the settings are under SATA Operation in the BIOS/UEFI? I noticed on some of our machines if SATA operation is set to ATA on the image and then the machine was set to AHCI or SCSI that it would not image properly. The image installs correctly and it starts to boot but it does not function at all until you change the setting in the BIOS/UEFI.

Cheers!

Joe

You are trying to boot the I.S.O. over the network.

The way I recommend you do this for pxe access in your company is to extract the content of the iso to a folder of your choosing then give proper access to the folder for the fog server using the exports file.

examples can be provided if im understanding what your trying to do?

@melvinpaz Ok, this is a Mac client you are having problems with. Please tell us exactly which Mac you have (serial number!). The modifications you made are correct as far as I see.

I am wondering why it is saying “Could not open net1”. Are there two network cards in this client. Possibly wireless? Although I am pretty sure iPXE does not provide any wireless drivers. We need more information on the hardware (exact Mac model / serial number) to be able to help you.

Bonjour
Oui c’est bien FOG 1.2.0 et c’est bien la modification initrd=$imagefile qui à fait fonctionné sur MAC

#########
Hy
Yes it’s good FOG 1.2.0 and it is changing initrd=$imagefile who in fact worked on MAC