pxe boot/fog menu
-
I setup a new fog server 1.5.4 and when I boot a computer via pxe boot, The fog menu comes up but then disappeared after a second and then all i had is a blinking cursor. Tried with a laptop and it also connected for a second then the backround went away had black screen with the works but can not do anything, Seems like it connects for a second and then disconnect. Dell computers. Any ideas?
-
Interesting, I have not seen that with any Dells we have. For the FOG iPXE menu to “disappear” that would mean the iPXE kernel would either have crashed or you have already register the target computer and scheduled a task for it.
Lets start out with some basics.
- What you do have configured for dhcp options 66 and 67. Also be sure you don’t have dhcp option 60 set.
- What model of dell computer is this?
- Is this computer in uefi or bois mode?
- Is the target computer and the fog server on the same subnet?
-
@george1421 said in pxe boot/fog menu:
Lets start out with some basics.
What you do have configured for dhcp options 66 and 67. Also be sure you don’t have dhcp option 60 set.
What model of dell computer is this?
Is this computer in uefi or bois mode?
Is the target computer and the fog server on the same subnet?Tried on a laptop and also desktop
opt 66 fogserver IP
opt 67 undionly.kpex
No out 60
Tried on same network and different network. -
@pa_fog_man said in pxe boot/fog menu:
No out 60
I’m not sure what that means, maybe no option 60. If so that is good.
What about the target computer, is it in bios or uefi mode? The iPXE boot kernel needs to match the firmware mode of the computer. undionly.kpxe for BIOS and ipxe.efi for UEFI systems. -
I meant no opt 60. I changed the DHCP to use ipex.efi and now I get error PXE-E79: NBP is too big to fit in free base memory. Using dhcp server from windows 2008 server.
-
@pa_fog_man This error happens when you try to load a file designed for UEFI BIOS while you are booting in LEGACY BIOS.
Try bootfile ipxe.pxe instead.
-
@pa_fog_man said in pxe boot/fog menu:
NBP is too big to fit in free base memory
This tells us that if you sending ipxe.efi and you get this message your target computer is in BIOS/legacy mode. In that case, undionly.kpxe (make sure it spelled right) is the proper boot file for this computer.
You haven’t answer the model of computer in question here.
-
I am using a Dell Opitplex 390. When I boot using legacy with ipxe.pxe everything seems to work. How can I get it to work using UEFI. Even getting the option to come up using just UEFI as an option. I select it in the bios but not an option when booting.
-
@pa_fog_man I think we have a bit of confusion here (and the 390 is not helping with clarification). First let me say that the Dell’s will let you dynamically boot in the other mode without changing the firmware (where it gets its default value). You can do this dynamic switching from the F12 boot menu. The other issue with the 390s (I can’t speak for personal experience with the 390s, but we have 790s in our fleet) the 790s were the first generation to support UEFI mode. But as far as I know, the 790s don’t support pxe booting in uefi mode. The 7010s was the first generation to support pxe booting in uefi mode. To pxe boot on the 7010s you would have to enable the uefi network stack on the network adapter settings in the bios. Otherwise you would not get ipv4 and ipv6 entries under uefi on the F12 boot menu.
Back on point. You MUST select the proper boot kernel for the target system bios mode (legacy/bios or UEFI). If you sent the wrong boot file to the system you will not see the FOG iPXE boot menu.
for bios mode you can use ipxe.pxe or undionly.kpxe
for uefi mode you can use ipxe.efi or snponly.efiThe bold text above are the typical kernels to set for dhcp option 67.
You can not mix the boot kernels. This isn’t a FOG issue, but rather a firmware one.
