Likely unfixable; disabling vesamenu.c32 globally would mean that all users would be left with a command-line syslinux interface, which would greatly reduce usability, especially for those using ISOs which include numerous menu options. Since I'm not aware of any way to detect hardware which has a broken framebuffer unable to display syslinux, while manually blacklisting each individual computer unable to display a graphical syslinux menu is unfeasible, only perhaps an improvement in syslinux for supporting semi-functional hardware can potentailly fix this.
Likely unfixable; disabling vesamenu.c32 globally would mean that all users would be left with a command-line syslinux interface, which would greatly reduce usability, especially for those using ISOs which include numerous menu options. Since I'm not aware of any way to detect hardware which has a broken framebuffer unable to display syslinux, while manually blacklisting each individual computer unable to display a graphical syslinux menu is unfeasible, only perhaps an improvement in syslinux for supporting semi-functional hardware can potentailly fix this.