AFAIK normal linux systems boot via: kernel followed by initrd?
Does the syslinuxVer7's corepure64.gz correspond to grub's rootfs64.gz?
The sizes are similar: 6M8 & 8M6.
Is modules64.gz just for grub's modules ?
core.gz = modules.gz + rootfs.gz
corepure64.gz = modules64.gz + rootfs64.gz
It doesn't matter which bootloader you're using.
SYSLINUX:
KERNEL /boot/vmlinuz64
INITRD /boot/corepure64.gz
or
INITRD /boot/modules64.gz
,/boot/rootfs64.gz
concatenate with a commaGRUB2:
linux /boot64/vmlinuz64
initrd /boot/corepure64.gz
or
initrd /boot64/rootfs64.gz /boot64/modules64.gz
space is finePS. the other complication is that: the problematic laptop has SDcard,
but is not seen by <EFIbootMenu>. So must boot from USBstik, which
occupies NEEDED socket.
Since grub is more-powerfull than EFI: will it find the UUiD/SDcard ?
Most likely not.
I've seen stubborn laptops refuse to boot from SD cards, sometimes from USBs.
Here's an abbreviate version of how a PC usually boot:
power up -> hardware check -> UEFI / LegacyMBR (<EFIbootMenu> here) -> find a storage media (HDD,USB) -> look for boot manager -> syslinux/grub -> search for files (anywhere should be fine) -> kernel booting...
Since your <EFIbootMenu> can't see your SD card, it doesn't matter which boot manager you're using. (syslinux / grub)
It's a Mother Board problem.