search for: fat1x

...what exactly you mean by "can navigate to it". Do you mean that from the EFI shell you can read the content of the FAT image and you can find (from the EFI shell) the relevant efi boot file (which should be a copy of 'syslinux.efi')? Also, please note that I keep talking about FAT1x, and not a VFAT32 image. For troubleshooting, I would avoid unnecessary long-file-name support in FAT (so, simple FAT, no VFAT, although the UEFI Specs support LFN) and I would suggest using FAT1x as expected by the UEFI Specs for removable media (not FAT32, although in some sections the UEFI...

...age". > > Bruno obviously uses genisoimage from Fedora or RedHat, which > has options -e and -efi-boot. > The output from this program suffices for EFI purposes, as > i can tell from the output of xorriso -report_el_torito: Once again, we are troubleshooting syslinux.efi in a FAT1x image for booting optical media in UEFI mode. I cannot understand the logic of using a code (patched or not) that has not been maintained since 2010 and that has not been tested with syslinux.efi. Although RH and Fedora have info and code for booting in UEFI mode, there is no document that is...

> Hello, > > Gene Cumm said on Thu, Oct 22, 2015 at 06:39:44PM -0400: > >On Thu, Oct 22, 2015 at 1:56 PM, Bruno Cornec via Syslinux > ><syslinux at zytor.com> wrote: > > > >> 3/ Using syslinux.efi in a FAT32 image (similar to the previous 2 > >> confs) stored on a iso9660 media by genisoimage and its > >> -eltorito-alt-boot -efi-boot

> Hi, > > Ady wrote: > > Is this "32MiB" a limitation related to the UEFI specs in any way? Or > > is it relevant for BIOS (non-EFI) too? > > It comes from El Torito specs which are referred to by UEFI 2.4 > specs. In EL Torito 1.0, Figures 3 and 5, "Sector Count" is a 2-byte > "Word". So it can count up to 65535. > Sector count