PXE Menu Problem - timeout and boot from HDD (menu option 1) -- doesn't happen
-
So, you basically need to play around in the firmware settings on the system, I think.
Look at your HDD mode, BIOS vs UEFI, Legacy ROM support, things like that. Play around with it.
From my experience, sanboot works for the handful of machine types in my building.
-
I looked and these are the only BIOS things that seem like they might have something to do with it.
Under ATA DRIVE SETUP:
- SATA controller = Enabled
- Configure SATA as= AHCI
Under STARTUP:
-
Boot Mode
The description says: Sets the boot policy as to whether to try Legacy Boot devices first or UEFI Boot options.
The value is “AUTO”, which is says will prioritize as: UEFI, Legacy -
Boot Priority
The value is “Legacy First”, which it says means “the system will try to boot legacy OS first and then UEFI”
-
If I change the BOOT MODE from AUTO to Legacy or UEFI, then the BOOT PRIORITY disappears from the BIOS menu.
If I change the BOOT PRIORITY to UEFI, it goes into a rebooting loop.I’ve changed it back, and I also moved the origin kpxe file back… but now the situation is worse.
After the Fog PXE menu, it goes to a black screen with cursor and the error beep starts beeping in a constant stream and nothing happens after that.Even now when I do the NO MENU option, I can no longer get it to boot after PXE.
If I hit ESC to abandon PXE, then it will boot to Windows and is happy.As far as PXE Fog Menu, I’ve gone from something that was not ideal but functional by specifying NO MENU…to now something that is non-functional.
-
You may have made a mistake copying the old undionly.kpxe back into it’s place.
The command should have been:
[CODE]cp /tftpboot/undionly.kpxe_orig /tftpboot/undionly.kpxe[/CODE]And, you played around in the firmware, so maybe resetting it to defaults might help too.
additionally, if you’re brave, you might try the undionly.kpxe file from FOG 0.32 and see if the menu works then.
You’ll have to download it (or pull it from your old FOG server), extract that single file, and place it into your current FOG’s tftpboot directory… Maybe you’ll have luck? I’d recommend re-naming the old file to something like undionly-old.kpxe -
I didn’t make a mistake in the copying. I looked at the directory and the file that is undionly.kpxe matches (in number of bytes) to undionly.kpxe_orig, and those two are different in number of bytes from undionly.kkxe.
In the firmware, I only changed the BOOT PRIORITY and BOOT MODE values. Nothing else. I’ve restored those to their original values.
So, … I guess the only remaining thing is for me to be brave?
-
Something else must have been done…
It doesn’t just break. If you set everything back the way it was, it should work as it did before.
Did it work with undionly.kkpxe ?
Remember this post ??
Fog PXE Boot Menu Configuration.No-Menu=**checked
Fog PXE Boot Menu Configuration.Exit-to-hard-drive-type=(any value)
Result: after PXE menu, Windows boots and it’s happy -
If it is prioritizing the mode as uefi then legacy but booting to legacy first, change the mode back to legacy. Sure you lose the priority because you’ve implicitly set it so there is no priority to use. I don’t know if it will make the system work but this, for now, seems the best starting point.
-
Honestly, I took a siesta for about 2 hours. Then went into Fog to the IPXE Boot Menu config and just did an update without changing any values (i.e. still said NO MENU). Went to the Com Lab and it worked just like it did before. I think I will be happy with NO MENU and not try to improve on this.
-
Isn’t the menu required to register at the host? Or did you change it to do quick-register for anything that isn’t registered?
-
I’ve left the PXE menu activated to register everything to begin with during my deploy period.
But for my use/production period, I will have it as NO MENU.
