search for: linux_efi_kernels

...uot; bootable in BIOS and/or (U)EFI > systems at the time (e.g. Slackware 14.0 / 14.1, Debian 7 Wheezy, RHEL > 6.x / 7 ) > _ BIOS and/or (U)EFI systems > > As a remainder and FWIW, from prior discussions (2014Q4) we have: > http://www.syslinux.org/wiki/index.php/Common_Problems#Linux_EFI_kernels http://www.syslinux.org/archives/2013-October/021021.html is the only possible match I see on the list, if that helps. Plus the Fedora and Arch bug reports.

...ards", "supposedly" bootable in BIOS and/or (U)EFI systems at the time (e.g. Slackware 14.0 / 14.1, Debian 7 Wheezy, RHEL 6.x / 7 ) _ BIOS and/or (U)EFI systems As a remainder and FWIW, from prior discussions (2014Q4) we have: http://www.syslinux.org/wiki/index.php/Common_Problems#Linux_EFI_kernels Yet, "fallback" method(s) should be allowed (in some way; with and/or without user intervention, and/or with/without printing information for the user). This feature is currently not present in Syslinux 6.03. Additionally, I would tend to think that whichever the conditions / standar...

...h >> as for kernel 3.2 (which is going to be alive in Debian Wheezy for at >> least a couple more years). >> >> So, can someone please clarify this situation? > >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 seems to have stumbled upon a real key for the >pre-Linux-3.3 kernels. If I'm understanding correctly, I think H. Peter Anvin on Tues Nov 18th, 10:24:15 PST 2014 explained this pre-Linux-3.3 ker...

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

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 seems to have stumbled upon a real key for the > >pre-Linux-3.3 kernels. > > If I'm understanding correctly, I think H. Peter Anvin on Tues Nov 18th, > 10:24:15 PST 20...

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

...which is going to be alive in Debian Wheezy for at > >> least a couple more years). > >> > >> So, can someone please clarify this situation? > > > >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 seems to have stumbled upon a real key for the > >pre-Linux-3.3 kernels. > > If I'm understanding correctly, I think H. Peter Anvin on Tues Nov 18th, > 10:24:15 PST 20...