similar to: syslinux 6.03 does not boot some kernels

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

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

> 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

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

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 Sun, 8 Feb 2015, Ady wrote: ... > There have been discussions and/or reports somewhat related to this > matter during 2013 (Mar-Dec), and reports about failing to boot some > kernels with Syslinux 6.03 (2014Q4). > > The topics involved: > > _ Kernels with no protected-mode code (e.g. grub's kernel lnxboot.img > initrd=core.img) > _ bzImage and zImage files

On Fri, 6 Feb 2015, Ady wrote: > ... > But if we are talking about Chromebooks with SeaBIOS, are we talking > about booting kernels in CSM mode? Or in UEFI mode? > > Other than Chromebooks with (stock) SeaBIOS, is this new reported > behavior also seen under other cases / hardware / firmware / kernels > (versions)? Hi Ady, With a clone of the git repo on kernel.org I run

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

> 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

> On Fri, 6 Feb 2015, Ady wrote: > > ... > > But if we are talking about Chromebooks with SeaBIOS, are we talking > > about booting kernels in CSM mode? Or in UEFI mode? > > > > Other than Chromebooks with (stock) SeaBIOS, is this new reported > > behavior also seen under other cases / hardware / firmware / kernels > > (versions)? > > Hi Ady,

> I have done another install to the usb stick. > > # syslinux --directory EFI/BOOT --install /dev/sdc1 > > ...this creates files ldlinux.c32 and ldlinux.sys in /EFI/BOOT > > I then mounted the 1st partition of the usb stick and copied > syslinux.efi and ldlinux.e64 from /usr/share/syslinux/efi64 to > /EFI/BOOT in the usb stick. > > I renamed syslinux.efi to

On 11/6/14, Ady <ady-sf at hotmail.com> wrote: > >> I have done another install to the usb stick. >> >> # syslinux --directory EFI/BOOT --install /dev/sdc1 >> >> ...this creates files ldlinux.c32 and ldlinux.sys in /EFI/BOOT >> >> I then mounted the 1st partition of the usb stick and copied >> syslinux.efi and ldlinux.e64 from

> > On 16/11/2014 18:33, Didier Spaier wrote: > > Hi all, > > > > I have requested tests of this USB installer: > > http://slint.fr/testing/slint64-14.1_syslinux.6.03.img > > in both BIOS and UEFI modes. > > > > A test in UEFI mode: > >

On 16/11/2014 18:33, Didier Spaier wrote: > Hi all, > > I have requested tests of this USB installer: > http://slint.fr/testing/slint64-14.1_syslinux.6.03.img > in both BIOS and UEFI modes. > > A test in UEFI mode: > http://www.linuxquestions.org/questions/slackware-14/%5Bann%5D-syslinux-6-03-has-been-released-4175521209/#post5270515 > > leaded to this message: >

Hi all, I have requested tests of this USB installer: http://slint.fr/testing/slint64-14.1_syslinux.6.03.img in both BIOS and UEFI modes. A test in UEFI mode: http://www.linuxquestions.org/questions/slackware-14/%5Bann%5D-syslinux-6-03-has-been-released-4175521209/#post5270515 leaded to this message: "Cannot relocate kernel, bailing out" That leaded me to this post in the ML:

> > efistub.jpg: > > >>Start PXE over IPv4. > Station IP address is 192.168.201.185 > > Server IP address is 10.210.32.100 > NBP filename is pxelinux.0 > NBP filesize is 6644000 Bytes > Downloading NBP file... > > Succeed to download NBP file. > > Downloading NBP file... > > Succeed to download NBP file. > I will not

A Toshiba CB35 Chromebook running Google's stock SeaBIOS reboots after selecting a relocatable kernel from extlinux 6.03. This is a regression caused by commit 8f470e7b movebits: Add syslinux_memmap_find() which factors syslinux_memmap_find() out of bios_boot_linux(). Prior to the refactoring, prot_mode_size was passed as the length in the first call to syslinux_memmap_type(). After

> 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 Mon, Nov 23, 2015 at 3:06 PM, Ady via Syslinux <syslinux at zytor.com> wrote: > It saddens (me) > C'mon; really? As you asked. -- -Gene

Hello, I'm booting linux-3.16-686-pae kernel (32-bit) via syslinux.efi 64-bit version. After boot linux sees only 2.5G of RAM while system has 32G installed. If I boot the same kernel with GRUB64 efi instead of syslinux then amount of RAM available to linux is 32G. Is this a bug or I'm missing something? syslinux.cfg: label live-686-pae menu label Linux (686-pae) menu