similar to: syslinux 6.03 does not boot some kernels

> Hi > > I've got a bit of a problem with syslinux 6.03. > > I am trying to deliver the debian stable netinstall to a vmware 5.1/5.5 > (tested both) vm using syslinux.efi in 64 bit. > > my pxelinux.cfg/default for everything I tried looks like this: > > --8<--- > prompt 1 > default local > label install > LINUX

Am 02.12.2014 schrieb Ady: > ( ... ) > > Since we are in the Syslinux Mailing List, please let me rephrase the > most relevant part of this case: syslinux.efi 6.03 is incapable of > booting some kernel, whereas syslinux.efi 6.01 can successfully boot it > under the same conditions. > I can now confirm that this can be replicated on hardware, a ThinkCentre M93 will reboot

> Am 02.12.2014 schrieb Ady: > > > ( ... ) > > > > Since we are in the Syslinux Mailing List, please let me rephrase the > > most relevant part of this case: syslinux.efi 6.03 is incapable of > > booting some kernel, whereas syslinux.efi 6.01 can successfully boot it > > under the same conditions. > > > I can now confirm that this can be

On Sun, Dec 07, 2014 at 05:35:37PM +0100, Johann Hartwig Hauschild wrote: > > I just had a look at the kernel-docs and the discussion here in november. > This issue should not be happening if I build a pre-3.3-kernel with > CONFIG_RELOCATABLE=y, CONFIG_EFI=y and CONFIG_EFI_STUB=y, right? Those are allready at those values at

Am 07.12.2014 schrieb Geert Stappers: > On Sun, Dec 07, 2014 at 05:35:37PM +0100, Johann Hartwig Hauschild wrote: > > > > I just had a look at the kernel-docs and the discussion here in november. > > This issue should not be happening if I build a pre-3.3-kernel with > > CONFIG_RELOCATABLE=y, CONFIG_EFI=y and CONFIG_EFI_STUB=y, right? > > Those are allready at

>Date: Sat, 6 Dec 2014 09:12:19 -0500 >From: Gene Cumm <gene.cumm at gmail.com> >To: Ady <ady-sf at hotmail.com> >Subject: Re: [syslinux] syslinux 6.03 does not boot some kernels > >On Fri, Dec 5, 2014 at 9:51 AM, Ady <ady-sf at hotmail.com> wrote: >> >> It sounds as if syslinux.efi 6.03 is only capable of booting a Linux >> kernel 3.3+ with an

Am 07.12.2014 schrieb Spike White: > >Date: Sat, 6 Dec 2014 09:12:19 -0500 > >From: Gene Cumm <gene.cumm at gmail.com> > > > >In an effort to get things started, I just wrote > >http://www.syslinux.org/wiki/index.php/Common_Problems#Linux_EFI_kernels > > > >I understand the CONFIG_RELOCATABLE issue well enough to write about > >it however Ady

Hello friends! HAXM is a hardware-assisted virtualization engine (hypervisor) that uses Intel Virtualization Technology to speed up IA (x86/ x86_64) emulation on a host machine running Windows or macOS. Latest Isolinux 6.03 hangs under VM after "Main image LBA =...". Please, help us investigate the root of the problem. Bug on github: https://github.com/intel/haxm/issues/15 Thank you!

On Sat, 7 Feb 2015, Ady via Syslinux wrote: > Thank you for this meaningful report. Ideally, I would suggest > performing a similar test (at least with the same kernel built with all > the above "config_*=y" settings) with official pre-built Syslinux > versions 4.07 and 3.86 (remembering that all Syslinux-related files, > including c32 modules, if being used, shall

On Thu, Sep 19, 2013 at 5:13 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Wed, Sep 18, 2013 at 4:09 PM, Chris Valentino > <chris.valentino at 1010data.com> wrote: >> I upgraded from syslinux 4.x to syslinux 6.01 and am now having issues with >> pxe chaining. I've tried moving up as far as 6.02-pre16, but I'm still experiencing the same problem. The

Gene, Where did you find the precompiled binaries for syslinux 6.03-pre7? Actually, I'm interested in the pre-compiled binaries for syslinux 6.03-pre6. I went out to kernel.org, but the latest they have is 6.02. Which appears to have an endian problem in its TFTP client code (when syslinux.efi tries to connect to the TFTP server, attempts to connect to UDP port 17664 instead of 69).

On Tue, May 13, 2014 at 7:51 PM, Ady <ady-sf at hotmail.com> wrote: > > I wonder why the already built-in binaries are not enough / adequate. > Or, in other words, I am curious about why do you need to build your > own binary files, instead of using the files that are already there > in the official archives in kernel.org. I don't believe it can be used as is: bash# file

Gene Cumm <gene.cumm at gmail.com> on Tue, 2013/10/22 06:35: > On Tue, Oct 22, 2013 at 5:41 AM, Christian Hesse <list at eworm.de> wrote: > > Hello everybody, > > > > iPXE builds an ISO image by default. (The build system has to be updated > > for new paths and to integrate ldlinux.c32, but that's not my problem.) > > > > With the binary

> On Fri, 6 Feb 2015, Ady wrote: > ... > > Testing with public popular kernels that are known to work (so to > > compare the behavior) might be useful too, but I don't know of any > > particular kernels to suggest for such tests. > > Right, I've confirmed boot failure using CONFIG_RELOCATABLE with > unmodified Linux 3.12.24, 3.13, 3.15, 3.18, and

On Fri, 6 Feb 2015, Ady wrote: ... > Testing with public popular kernels that are known to work (so to > compare the behavior) might be useful too, but I don't know of any > particular kernels to suggest for such tests. Right, I've confirmed boot failure using CONFIG_RELOCATABLE with unmodified Linux 3.12.24, 3.13, 3.15, 3.18, and 3.19-rc7 kernels. > I know that for

With the release of 6.03 on October 6th. but page still shows latest as 2013-10-13 : Syslinux 6.02 released. http://www.syslinux.org/wiki/index.php/The_Syslinux_Project On 6 Oct 2014 at 9:35, H. Peter Anvin wrote: Date sent: Mon, 06 Oct 2014 09:35:19 -0700 From: "H. Peter Anvin" <hpa at zytor.com> To: For discussion of Syslinux and tftp-hpa

? In qemu (virtual machine) it is working ok. ? On?a physsical machine syslinux does not boot at all : ? ? SYSLINUX 6.02 EDD 6.02-pre9 ... ? Boot error. I attached the usb drive info. ________________________________ From: Matt Fleming <matt at console-pimps.org> To: Adrian Irimia <adixtx at yahoo.com> Cc: "syslinux at zytor.com" <syslinux at zytor.com> Sent:

Yes. Prior versions (all to 6.01 inclusive) are working very well. ?And yes it fail before invoking chain.c32 (as I said in qemu there is no errors). ________________________________ From: Matt Fleming <matt at console-pimps.org> To: Adrian Irimia <adixtx at yahoo.com> Cc: "syslinux at zytor.com" <syslinux at zytor.com> Sent: Tuesday, July 23, 2013 5:16 PM

Hi everyone, I have released Syslinux 6.03. It is by and large identical to 6.03-pre20. I would like to do a short cycle for 6.04, because 64-bit support for ext4 has come up as a very high priority. Therefore I do not want to stuff too many things into the 6.04 release but hold them for 6.05. Thanks to Ady for most of the changelog. Changes in 6.03: * chain: Fix chainloading on 6.02

I just tested 6.02-pre10 version. ? On physsical machine it is booting ok now,?but chain.c32 result is the same errors :? ERR: Primary partition (in MBR) with invalid offset and/or length. ? ERR: Cant't find myself on the drive I booted from Adding 'relax' option to chain.c32 invocation resolves the problem. ? In qemu the boot and chaining works ok (without 'relax' option).