[syslinux] vesamenu.c32 and EFI

[Ady Ady]

> When we use the vesamenu.c32 and libcom32.c32 from 6.03 we end up with a 
> blank screen and the machine
> seems to hang.  I've tried adding MENU RESOLUTION based on : 
> https://bugzilla.syslinux.org/show_bug.cgi?id=27#c2
> and that doesn't change the behaviour at all.
 
 
Are you able to replicate the same behavior when using a VM?

Are you able to replicate the same behavior when using the official 
pre-compiled binaries from Syslinux 6.04-pre1? Please avoid mixing 
binaries from different versions; use all the binaries from the same 
version/build.


> I figured it might be already working/fixed in master so I've built 
> syslinux myself instead last night
> and was consistently presented with errors when trying to load instead:
 
 
Current git master head is worthless for troubleshooting, the same as 
official binaries from 6.04-pre2 and 6.04-pre3.


> ls
> ```
> -a----       29/09/2019     16:35            465 syslinux.cfg
> -a----       29/09/2019     16:33         139968 ldlinux.e64
> -a----       29/09/2019     16:33          24480 libutil.c32
> -a----       29/09/2019     16:33          31760 menu.c32
> -a----       29/09/2019     16:33          32456 vesamenu.c32
> -a----       29/09/2019     16:33         201680 libcom32.c32
> -a----       29/09/2019     16:33         199952 bootx64.efi
> ```
> 
> (bootx64.efi is efi64/efi/syslinux.efi renamed
> 
> syslinux.cfg
> ```
> UI vesamenu.c32
> 
> TIMEOUT 140
> MENU ROWS 4
> 
> MENU CLEAR
> MENU BACKGROUND /slax/boot/bootlogo.png
> MENU RESOLUTION 1024 768
> 
> LABEL default
> MENU LABEL Run Linux
> KERNEL /slax/boot/vmlinuz
> APPEND vga=769 initrd=/slax/boot/initrfs.img load_ramdisk=1 
> prompt_ramdisk=0 rw printk.time=0 apparmor=0
> 
> LABEL default
> MENU LABEL Run Linux debug
> KERNEL /slax/boot/vmlinuz
> APPEND vga=769 initrd=/slax/boot/initrfs.img load_ramdisk=1 
> prompt_ramdisk=0 rw printk.time=0 apparmor=0 debug
> ```
 
 
I can think of several reasons for this problem with vesamenu.c32.

You posted the content of the directory in which ldlinux.e64 is 
located, but it is not clear (to me) where this directory is located. 
Could you post its complete exact path?

With the above information we might be able to provide at least a basic 
troubleshooting procedure, and/or replicate the reported behavior.

Regards,
Ady.