search for: _hybrid_

...) limitation as "[not] able to boot in UEFI and BIOS modes > using Syslinux" is inaccurate. Thanks Ady, I appreciate your accuracy and stand corrected. However, in my use cases at least (providing installers able to boot in in BIOS _and_ UEFI modes) there's no point in providing _hybrid_ images relying _only_ on Syslinux as they will be usable _only_ for USB booting anyway, in case of UEFI. So if I want to "uniformize" the look of the greeting screens I'll have to provide "USB only" images, not hybrid ones. Or use grub for both BIOS and USB booting, but tha...

...le to boot in UEFI and BIOS modes > > using Syslinux" is inaccurate. > > Thanks Ady, I appreciate your accuracy and stand corrected. > > However, in my use cases at least (providing installers able to boot in > in BIOS _and_ UEFI modes) there's no point in providing _hybrid_ images > relying _only_ on Syslinux as they will be usable _only_ for USB booting > anyway, in case of UEFI. > > So if I want to "uniformize" the look of the greeting screens I'll have > to provide "USB only" images, not hybrid ones. Or use grub for both BIOS...

> > Hi, > > On 11/11/2014 02:55, Ady wrote: > > Again, dd'ing your isohybrid image onto your (virtual or real) drive > > will fail to boot in EFI mode. Your "syslinux.efi-based" > > "/isolinux/efiboot.img" will not be capable of booting. This is one > > of the steps that corresponds to grub2, not to whichever other EFI > >

Hi, On 11/11/2014 02:55, Ady wrote: > Again, dd'ing your isohybrid image onto your (virtual or real) drive > will fail to boot in EFI mode. Your "syslinux.efi-based" > "/isolinux/efiboot.img" will not be capable of booting. This is one > of the steps that corresponds to grub2, not to whichever other EFI > bootloader you use (e.g. syslinux.efi). So,