search for: syslnx64

...slinux.cfg in the same searched-for location. > > [...] > > Your suggested proposal is, entirely by chance, almost exactly the same > solution that I'm currently using in Knoppix since version 7.2, i.e. > bitness-dependent ldlinux.e32/ldlinux.e64 and also a > syslnx32.cfg/syslnx64.cfg with a fallback to syslinux.cfg. It's merely > renaming and adding file names to the syslinux configuration file array, > just a few lines of code. So far, the patch is only included on Knoppix, > but feel free to use it on your distro as well. > > I'd vote for acceptanc...

...location. > > > > [...] > > > > Your suggested proposal is, entirely by chance, almost exactly the same > > solution that I'm currently using in Knoppix since version 7.2, i.e. > > bitness-dependent ldlinux.e32/ldlinux.e64 and also a > > syslnx32.cfg/syslnx64.cfg with a fallback to syslinux.cfg. It's merely > > renaming and adding file names to the syslinux configuration file array, > > just a few lines of code. So far, the patch is only included on Knoppix, > > but feel free to use it on your distro as well. > > > > I...

...yslinux at knopper.net> wrote: > Apparently, the rename of ldlinux.e32 to ldlinux.e64 for the 64bit > variant is already in the mainline git, so the only change left for > automatically chosing a different config file is the tiny patch attached > here, which will > > - prepend syslnx64.cfg to the config file search path for the 64bit variant > - prepend syslnx32.cfg to the config file search path for the 32bit variant > - add /boot/isolinux and /isolinux plus isolinux.cfg to the search path for > all variants, just for the case that the "rename" was forgotten...

...; > [...] > > > > > > Your suggested proposal is, entirely by chance, almost exactly the same > > > solution that I'm currently using in Knoppix since version 7.2, i.e. > > > bitness-dependent ldlinux.e32/ldlinux.e64 and also a > > > syslnx32.cfg/syslnx64.cfg with a fallback to syslinux.cfg. It's merely > > > renaming and adding file names to the syslinux configuration file array, > > > just a few lines of code. So far, the patch is only included on Knoppix, > > > but feel free to use it on your distro as well. > &g...

...uot;, and then fallback to > syslinux.cfg in the same searched-for location. [...] Your suggested proposal is, entirely by chance, almost exactly the same solution that I'm currently using in Knoppix since version 7.2, i.e. bitness-dependent ldlinux.e32/ldlinux.e64 and also a syslnx32.cfg/syslnx64.cfg with a fallback to syslinux.cfg. It's merely renaming and adding file names to the syslinux configuration file array, just a few lines of code. So far, the patch is only included on Knoppix, but feel free to use it on your distro as well. I'd vote for acceptance of your proposal. Rega...

...t; > > > > > Your suggested proposal is, entirely by chance, almost exactly the same > > > > solution that I'm currently using in Knoppix since version 7.2, i.e. > > > > bitness-dependent ldlinux.e32/ldlinux.e64 and also a > > > > syslnx32.cfg/syslnx64.cfg with a fallback to syslinux.cfg. It's merely > > > > renaming and adding file names to the syslinux configuration file array, > > > > just a few lines of code. So far, the patch is only included on Knoppix, > > > > but feel free to use it on your distro a...

I've been using various versions of syslinux as the boot loader for the g4l project that I have been the maintainer of since 2004. It was already using syslinux, so I've just updated it over the years, and currently have it use 5.10 version, but have done test builds with the 6.x versions. Recently had request from to users about EFI support, and one suggested that virtualbox has

....x versions with 6.x > > versions, and build process remained the same. > > You may check the current version of Knoppix 7.3 (or 7.2), which > contains a efi/boot directory with a patched version of syslinux.efi > that will read the standard syslinux.cfg file for 32bit, and > syslnx64.cfg for 64bit. This version, when copied to USB flash disk, is > know to work in both cases, the standard BIOS (called CSM in EFI) or EFI > mode, just no secure boot possible since the boot loader is not signed. > > Seems to work on many notebooks set to EFI-boot, just apple seems to &...

...nt directory and replace the 5.x versions with 6.x > versions, and build process remained the same. You may check the current version of Knoppix 7.3 (or 7.2), which contains a efi/boot directory with a patched version of syslinux.efi that will read the standard syslinux.cfg file for 32bit, and syslnx64.cfg for 64bit. This version, when copied to USB flash disk, is know to work in both cases, the standard BIOS (called CSM in EFI) or EFI mode, just no secure boot possible since the boot loader is not signed. Seems to work on many notebooks set to EFI-boot, just apple seems to have problems reiniti...

Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 (with an optional Syslinux menu containing multiple entries). Problem (solved) #1: The default directory location for both syslinux.efi is the same. Solution #1: Rename each syslinux.efi to bootx64.efi and to bootia32.efi. Problem (solved) #2: Each syslinux.efi needs at least its respective ldlinux module. Solution #2:

...slinux.cfg in the same searched-for location. > > [...] > > Your suggested proposal is, entirely by chance, almost exactly the same > solution that I'm currently using in Knoppix since version 7.2, i.e. > bitness-dependent ldlinux.e32/ldlinux.e64 and also a > syslnx32.cfg/syslnx64.cfg with a fallback to syslinux.cfg. It's merely > renaming and adding file names to the syslinux configuration file array, > just a few lines of code. So far, the patch is only included on Knoppix, > but feel free to use it on your distro as well. I didn't know that Knoppix was...

Hi all, We're using the classic boot BIOS syslinux successfully for many years, but meanwhile it's getting harder to buy hardware the still supports this boot mode. The option for us would be syslinux EFI boot. To avoid too many changes we would like to generate an image for our different hardware parts that supports both - classic BIOS boot and (U)EFI boot. This would allow us to leave