search for: filepathlist

...d to use the canonical one (and why)? I would have expected that EFI falls back to the EFI shell if no /efi/boot/bootx64.efi is present in the ESP. Hrmpf ... The file names are defined in 3.4.1.1 "Removable Media Boot Behavior". In general, the file paths can be set by a NVRAM variable (FilePathList[0] ?) for particular devices. Do you have indications that syslinux.efi was really executed ? > > The only non-expert option is --uefi. > > There is no further non-expert documentation known to me. > I think --mac could fall in this topic too. Cough. I still riddle how to descri...

...hy)? > > I would have expected that EFI falls back to the EFI shell > if no /efi/boot/bootx64.efi is present in the ESP. > > Hrmpf ... The file names are defined in 3.4.1.1 "Removable Media > Boot Behavior". In general, the file paths can be set by a NVRAM > variable (FilePathList[0] ?) for particular devices. > > Do you have indications that syslinux.efi was really executed ? I get the rEFInd shell, and under it the lines "SYSLINUX 6.03", "Booting NodeOS..." (what I have in the SAY field in syslinux.cfg file), "Loading kernel.img... ok"...

Hi, i wrote: > > Well, it is about really usable capabilities of isohybrid, Ady wrote: > but their practical combination, usage, effects, > goals... are not expressed clearly enough for the common user to put in > practice. How to express the embarrassing fact that ISOLINUX is not ready for UEFI but isohybrid is ? http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI would