@JJ-Fullmer This was it, thank you!!

Everything I read kept telling me this machine was x86 based and there is no hint in the BIOS or the serial number lookup tool, of it running an ARM processor(other then “Elite”). We are going to return these machines to the vendor, so problem solved for us.

Would be interested in hearing about future support for ARM in FOG because I’m sure this isn’t the last time we will cross paths with it.

@JJ-Fullmer It is the Intel variant,

@Tom-Elliott We just tried the following experimental kernels, same reboot behavior.

bzImage Version: 6.18.38
bzImage32 Version: 6.18.38
arm_Image Version: 6.18.38

and

bzImage Version: 6.12.35
bzImage32 Version: 6.12.35
arm_Image Version: 6.12.35

Anything else we could try?

Having major issues PXE booting an intel based Surface Laptop 7th Edition. I have two these same devices that are unable to boot; secure boot is fully disable, pxe boot enabled.

PXE successfully downloads the file with no errors then machine immediately reboots. I am using the surface USB Ethernet adapter (which works fine with other surface pro devices). Microsoft changed something with this latest iteration of the Surface Laptop.

Same behavior when changing out the following:

• snponly.efi
• ipxe.efi
• Tried at least 6 different development kernel
• Not having any pxe issues with HP, Lenovo, Dell and Surface Pro(tablet) devices

FOG Server

• 1.5.10.1903
• bzImage Version: 6.6.69
• bzImage32 Version: 6.12.35
• arm_Image Version: 6.12.35

Help @Tom-Elliott Elliott I’m at my wits end!

Thanks!

Joe

We are having this same exact issue when attempting to boot Z240’s. Has there been any progress with addressing this? We can get around it somewhat by manually registering the workstations but that really isnt a soulution.

Any config hacks/bios tweaks/kernal updates for the Z240 would be greatly aptreatiated.

Thanks all!

We would very much love to see mac support!

Wahoo!!

Shes up and running! Thank you both for the feedback, you guys deserve a beer! If your ever in Fort Collins, Colorado PM me haha.

So for everyone else my problem was totally due to syntax and directory location,

By changing CODE initrd ${fog-ip}/fog/iso/Hirens152.iso[/CODE] to CODE initrd http://${fog-ip}/fog/service/ipxe/iso/Hirens152.iso[/CODE] iPXE was able to fully resolve the path. This was only accomplished by making iPXE produce some sort of feedback via the below code(most graciously posted by Junkhacker),

menu
item --gap – ---------------- iPXE boot menu ----------------
item BOOTCD Hirens BOOTCD
item shell ipxe shell
choose target && goto ${target}

:BOOTCD
initrd 192.168.1.130/fog/iso/Hirens152.iso ||
echo failed to load iso if it stops here
prompt
chain memdisk iso raw ||
echo failed to chain memdisk if it stops here
prompt
boot ||
echo failed to boot here if it stops here
prompt
goto MENU

:shell
shell ||
goto MENU

autoboot[/CODE]

Thanks again guys!!

I actually noticed that mistake right after I posted the code. This is what I have now,
[CODE]:MENU
menu
item --gap – ---------------- iPXE boot menu ----------------
item BOOTCD Hirens BOOTCD
item shell ipxe shell
choose target && goto ${target}

:BOOTCD
initrd 192.168.1.130/fog/iso/Hirens152.iso
chain memdisk iso raw ||
echo failed to boot
prompt
goto MENU

:shell
shell ||
goto MENU

autoboot[/CODE]

And the link resolves fine via a browser,

[IMG]https://collinscustoms.info/public.php?service=files&t=179ccb1dc8da0d41cb951c602e37ea4e[/IMG]

But it continues to immediately return to the previous main menu. It seems strange to me that it returns to the main menu so fast without throwing any sort of error or timeout message.

Hi Junkhacker,

Thanks for the quick response! I just changed that around and unfortunately the boot menu is still acting the same way. I double checked all the permissions on the folder and everything seems fine. Does the .iso need to be mounted or is it correct to have the file just as a stand alone .iso inside that pxe “pointed” folder? Thanks again for taking the time.

Hello all first time poster here,

Ive been trying to boot Hirens live CD(or any iso for that matter) from the advanced ipxe menu(i.e. fog admin area). When booting a client the menu & iPXE shell appear correctly but when I select Hirens boot CD it brings me immediately back to the the main pxe menu. This is the code that I am using,

menu
item --gap – ---------------- iPXE boot menu ----------------
item BOOTCD Hirens BOOTCD
item shell ipxe shell
choose target && goto ${target}

:BOOTCD
initrd ${192.168.1.130}/var/www/fog/service/ipxe/iso/Hirens152.iso
chain memdisk iso raw ||
echo failed to boot
prompt
goto MENU

:shell
shell ||
goto MENU

autoboot[/CODE]

Any insight would be greatly appreciated thanks!

Server specs:

FOG version 1.1.1
Ubuntu 14.04 LTS