Good news, lunch was great!

The menu delay had been set at 5, which just flashed by. But, holding up-arrow made it stay, and my machine is now happily imaging. Thank you very much!

I wonder if the menu delay is related to the Mobile A8 that is in the Brix computer, some kind of driver/clockspeed issue. No matter, it’s easy enough to work around, and you have defeated the evil Realtek!

Ooo, I think that worked. The menu flashed by too fast to get into it, but I did see something new that time. I’m off to lunch, so I’ll try holding up arrow when I return, and report back.
Thanks!

Actually, cancel that Realtek model number, as I’m not 100% sure it’s right. The motherboard is a gigabyte m1m3xap from a new Brix A8, but I’ve also tested with a realtek from about 2 years ago on an MSI 970A-G46. (I know they can put different nics in without changing motherboard model names.)

Still no menu, and it rebooted to the pxe. If it helps, the main nic I’m currently concerned with is a Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC.
My guess is that I screwed up something small and dumb on the FOG server, but I don’t know what to troubleshoot, past verifying tftp function. A tech long ago set up the 0.32 version, so I don’t know what (if any) customizations he may have done to it. I ran the update to 1.0.1 and it seemed to go smoothly.
IF the answer winds up being ‘kill it with fire, and start over’ - can I save the old images (we only have 2 saved) and have the new instal recognize them? If not, re-building those images wouldn’t be the end of the world.

Thanks for the quick reply.
With that new file, after the 'configuring (net0 -{mac}) line, the machine reboots back to the start of the pxe process. So on the upside, it’s not booting off the hdd now. But I still didn’t get to the FOG menu.

Hello,
I’ve done a fair amount of forum reading the past two days, so now I’m posting. Everything worked on 0.32, but I recently got crazy and updated a working system. Ooops! So now I’m on a non-working 1.0.1
The problem I need help with is that clients now seem to get the bootloader (bad cellphone picture attached) - but then fails to load the FOG menu, and proceeds to just boot off of other devices. The attached image is right before the machine gives up and boots off an hdd.

Things I can tell you about the install so you don’t have to ask:
FOG server: Ubuntu 11.04 running as an ESXI VM.
DHCP option 66 set to FOG server IP, option 67 set to undionly.kpxe
I have verified via a windows machine that 1) TFTP is working on FOG server, and 2) undionly.kpxe is where it’s supposed to be.
No VLANs involved, machines can reach the FOG server.
On one machine, UEFI network booting and the UEFI network stack are disabled. My other test machine’s bios menu is somewhat lacking (thanks, MSI!) so I can’t verify that.

So, where do I go from here? Please use small words - I can copy/paste in putty just fine, but that’s about as far as my linux “expertise” goes.
Thanks!

[ATTACH]860[/ATTACH]

[url=“/_imported_xf_attachments/0/860_2014-05-30 09.50.23-2048.jpg?:”]2014-05-30 09.50.23-2048.jpg[/url]