Hi sebastian,
Thanks for this answer.
@Sebastian-Roth said in Black screen and blinking cursor after vesamenu:
@Luc-Novales said in Black screen and blinking cursor after vesamenu:
IPXE didn’t work out of the box, and I applied Chainloading PXE to iPXE using pxelinux.0.
The wiki article was edited in 2014 last and I don’t think this is up to date information. Would be really cool if we ever find the time to clean up the wiki and remove such old stuff.
It help to understant, perhaps it should not be removed 
There have been a lot of changes in iPXE as well for newer hardware and I’d suggest we try to find a solution with current iPXE instead of trying to fix the old pxelinux hack.
The problem is that it is an old hardware that we could clone with an old version of clonezilla, but impossible with newer versions. Now, we decided to use FOG and we need to debug this PXE boot.
When you say “IPXE didn’t work out of the box”, what exactly does that mean. Please describe in more detail and take a picture of the screen and post here.
IPXE boot
Using “stock” configuration with undionly.kpxe, result is conform to this screenshot :
.
Client gets undionly.kpxe by TFTP and it stops. It doesn’t reply to ARP request send by the server.
PXE boot
When applying Chainloading PXE to iPXE using pxelinux.0.
The client gets pxelinux.0 and the screen is :
Then it displays the fugitive vesamenu as below :
The ipxe.krn file is downloaded by the client using TFTP and it stops.
There is a black screen and blinking cursor, no HTTP request or other communication on the LAN from the client.
No log in apache2 server.
Only WOL request are emitted by server.
Luc.
GeodeTM LX 800 500Mhz).