"Invalid or corrupt kernel image" -- except it isn
I have two boxes, one real one with a core2duo and a foxconn motherboard, and another virtual machine running inside VMWare. (Which would make it, I guess, a "vmware motherboard".) Both of them are exhibiting an identical problem when booting minimyth.
I've set up my tftp server, and it's serving pxelinux.0 just fine. But the problem comes with the handoff to loading the kernel. Every time you cold boot either the real (physical -- foxconn) or virtual (not physical -- vmware) machine, you get a "invalid or corrupt kernel image". (I apologize for using screenshots, but as the OS isn't actually loaded that's the only way to get the information, outside of lots of retyping.)
Now here's the weird part... As far as I can tell, the kernel image on the tftp server is just fine. Why do I say that? Because I can get either machine to boot by hitting enter!
In other words, not changing any files on the server, not throwing any flags, just basically saying "try again" causes both the VMware and real hardware systems to continue booting every time.
Anyone seen this before? And/or have any ideas on how to work around it?
(Happy to do any commands to help diagnose the problem, though the VMware machine has additional issues apparently stemming from the virtual video card that I haven't even started to dig into yet. I do have a fully working ubuntu frontend in an identically configured VM that I could use to do hardware probes, so not all is lost.)