search for: bootloder

...optical media in EFI > mode. So your VM, when being set to use EFI and this ISO image as > virtual boot media, will fail. I assumed that post-precessing the ISO image with "isohybrid -u" (as I do when using grub2 as EFI bootloader would work the same when using syslinux as an EFI bootloder. So that was a wrong assumption... Maybe a warning about that in this wiki page: http://www.syslinux.org/wiki/index.php/Isohybrid wouldn't be useless, then... > I don't know how exactly you are building your virtual HDD to boot in > EFI mode. In /EFI/BOOT/syslinux.cfg, you could:...

...gt; then hanging. The menu.c32 in 6.0.3 doesn't seem to cause that... > About your customers' setup... Are they using official binaries downloaded from kernel.org? Which exact version of Syslinux are they using? Is the menu.c32 file from the same exact version (and build) as the bootloder file? What happens if they try to get to the Syslinux boot prompt, instead of immediately loading menu.c32? Does it hang too? Could you post their configuration file? Are they also using ipxe and chainloading? Is the behavior (menu.c32 showing one character only and then hanging) replicated b...

...Which exact version of Syslinux are they using? I've tried versions 3.86, 4.07, 6.01, 6.03. We can only generally use 4.07 or less because of the described ipxe compatibility issues, 6.0x will not load ldlinux.c32. > Is the menu.c32 file from the same exact version (and build) as the > bootloder file? In all cases, yes. > > What happens if they try to get to the Syslinux boot prompt, instead of > immediately loading menu.c32? Does it hang too? For the specific case where the hang is observed - It is required at least for the pxelinux.cfg downloaded to contain a "serial 0...

On 9/22/2015 4:33 AM, Gene Cumm wrote: > > https://sites.google.com/site/genecsyslinux/sl604p0g15-bios.tgz?attredirects=0&d=1 > https://sites.google.com/site/genecsyslinux/sl604p0g15-x64.tgz?attredirects=0&d=1 > Tried these new binaries this morning. No change, still will not attempt to load ldlinux.c32. As a context, what I'm really trying to do is get a newer

...; mode. So your VM, when being set to use EFI and this ISO image as > > virtual boot media, will fail. > > I assumed that post-precessing the ISO image with "isohybrid -u" (as I do > when using grub2 as EFI bootloader would work the same when using syslinux > as an EFI bootloder. > > So that was a wrong assumption... Maybe a warning about that in this > wiki page: > http://www.syslinux.org/wiki/index.php/Isohybrid > wouldn't be useless, then... No warning needed (it would be inappropriate). The problem is not in the isohybrid command, neither related...

...they using? > > I've tried versions 3.86, 4.07, 6.01, 6.03. > We can only generally use 4.07 or less because of the described ipxe > compatibility issues, 6.0x will not load ldlinux.c32. > > > Is the menu.c32 file from the same exact version (and build) as the > > bootloder file? > > In all cases, yes. > > > > > What happens if they try to get to the Syslinux boot prompt, instead of > > immediately loading menu.c32? Does it hang too? > > For the specific case where the hang is observed - It is required at > least for the pxelin...

> 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 >

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