similar to: Changes to get CD to boot on EFI System.

On 9 Jul 2014 at 6:01, Gene Cumm wrote: Date sent: Wed, 9 Jul 2014 06:01:22 -0400 Subject: Re: [syslinux] isohybrid binary not in 6.03-pre18? (utils bt is in bios/utils?) From: Gene Cumm <gene.cumm at gmail.com> To: "Michael D. Setzer, II" <mikes at kuentos.guam.net> Copies to: Syslinux at zytor.com > > On Jul 9, 2014 5:15 AM, "Michael D. Setzer II" >

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

I've got a user of my g4l project that is having a system that locks with my kernels, but also with hdt? The default versions are using the 5.10 version of syslinux, but build a special setup using 6.02 and it still locks with both the kernels and the hdt? He was able to get gparted i486 live iso to boot on the machine, so not clear what the issue might be. The system is a Fujitsu T734

I have been using syslinux-6.x along with isohybrid --mac and --efi option to create a usb hybrid iso with EFI support. The thing with EFI is that you'll need to use grub as your bootloader for EFI but isohybrid does setup the proper partition schema for EFI. You'll need to use the following to generate an iso that works. xorriso -as mkisofs -J -R -l -V some-vol-label \ -o ../image.iso

Hi, piranna wrote: > > Quoting http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI: > > "The additional isohybrid feature for UEFI adds a partition to the MBR > > partition table pointing to the same file in the ISO 9660 filesystem > > as does the El Torito catalog entry for EFI." Ady wrote: > IMHO, the current content of the Isohybrid page in the Syslinux

Hi, Ady wrote: > * ISO images, > * burnt to _optical media_, > * and using then the resulting _optical media_ to boot in _UEFI mode_, > * in which the _main bootloader_ for such _optical media_ booting in > such _UEFI mode_ is part of The Syslinux Project. I would be willing to try such an ISO with qemu+OVMF. Regrettably my real test iron has no EFI firmware. Do you know the

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

> > I am still interested in improving the isohybrid wiki > and will watch for pointers to descriptions of the FAT > production process (with GRUB/GRUB2 if not with SYSLINUX). > > If no such descriptions appear within the next weeks, > then i plan to state in > http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI > > "The SYSLINUX project cannot yet provide

On 22/03/2016 16:35, Thomas Schmitt via Syslinux wrote: ... > How can we augment > http://www.syslinux.org/wiki/index.php?title=ISOLINUX > http://www.syslinux.org/wiki/index.php?title=Isohybrid > so that users do not believe to have missed the trick for UEFI booting > from optical media ? +1. I have read Ady's answer to this message, but still: why not just state clearly in

Wondering what the best process would be to create livecds using the newer version of syslinux. Currently my G4L project has just been upgraded to syslinux 5.10 and works fine with regular 32 and 64 bit systems using the 32bit kernels, but have seen comments about EFI and somethings about 32bit only working with 32bit and 64bit with 64bit? Since I average about 1,000 downloads per week, I

> Hi, > > Ady wrote: > > This could be misinterpreted by some users as: "if > > you want to build an isohybrid image, then you cannot use > > 'syslinux.efi'". This would be incorrect. > > I don't know whether syslinux.efi can be used for booting > from ISO 9660 via UEFI. Currently there is no example > around which would succeed

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,

Quoting http://www.syslinux.org/wiki/index.php/Isohybrid#UEFI: "The additional isohybrid feature for UEFI adds a partition to the MBR partition table pointing to the same file in the ISO 9660 filesystem as does the El Torito catalog entry for EFI." According to this (and can be see using fdisk) it's being created a partition-inside-partition just by setting its start and end

On 4 Apr 2016 at 8:06, H. Peter Anvin wrote: Subject: Re: [syslinux] hdt error on syslinux 6.0.4-pre1? To: "Michael D. Setzer II" <mikes at kuentos.guam.net>, syslinux at zytor.com From: "H. Peter Anvin" <hpa at zytor.com> Date sent: Mon, 4 Apr 2016 08:06:13 -0700 > On 04/04/16 07:14, Michael D. Setzer II via Syslinux

> Hello, > > Ady via Syslinux said on Sun, Oct 25, 2015 at 08:15:37PM +0200: > >_ Creating filesystem that _does_ conform to ISO-9660; > > I think the only issue is with a tag. That same image boots with grub > 0.99 I understand. My point is, in theory, "everything" is frequently expected to work as it was designed; in practice, it is not. So my suggestions

On 10/11/2014 04:02, Ady wrote: > >> Hi there, >> >> I failed to boot an installer in a VMware player (Version6.0.3 >> build-1895310) >> using syslinux 6.03, be it off an hybrid ISO image and an USB stick. >> >> Booting succeeds if the VM is set to use a BIOS firmware with both media, >> but fails using an efi firmware. >>

Hi there, I failed to boot an installer in a VMware player (Version6.0.3 build-1895310) using syslinux 6.03, be it off an hybrid ISO image and an USB stick. Booting succeeds if the VM is set to use a BIOS firmware with both media, but fails using an efi firmware. Trying to boot off the ISO image I get an error message "The firmware encountered an unexpected exception" Trying to

> > 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, if I inspect an hybrid ISO with tools like fdisk and gdisk, then looks like hybrid ISO has both the MBR and GPT in order to support both the BIOS and UEFI: # gdisk -l /dev/sdb GPT fdisk (gdisk) version 0.8.10 Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: present Found valid MBR and GPT. Which do you want to use? 1 - MBR 2 - GPT 3 - Create blank GPT

Was seeing it I could get any closer with the efi boot using the 6.0.4, and didn't have any more luck. Did a test with it in bios mode and it works for the regular kernels, but when I tried the hdt.c32 I get the following error? Undef symbol FAIL: parse_url Failed to load COM32 file hdt.c32 Only find urlparce.c in the PXE directory, and no reference to it in any files in the hdt