search for: config_efi

...w 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 EFISTUB, the kernel config should include: > > CONFIG_RELOCATABLE=y > CONFIG_EFI=y > CONFIG_EFI_STUB=y > CONFIG_FB_EFI=y > CONFIG_FRAMEBUFFER_CONSOLE=y > > For UEFI ia32 firmware, it should be possible (in theory, and if I > understand correctly) to use 32 bit Syslinux to load a 64 bit kernel, > as long as the latter has CONFIG_EFI_MIXED enabled. > &...

...gest 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 EFISTUB, the kernel config should include: > > > > CONFIG_RELOCATABLE=y > > CONFIG_EFI=y > > CONFIG_EFI_STUB=y > > CONFIG_FB_EFI=y > > CONFIG_FRAMEBUFFER_CONSOLE=y > > > > For UEFI ia32 firmware, it should be possible (in theory, and if I > > understand correctly) to use 32 bit Syslinux to load a 64 bit kernel, > > as long as the latter ha...

...ersion 6.03, "as-is". 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. I know that for EFISTUB, the kernel config should include: CONFIG_RELOCATABLE=y CONFIG_EFI=y CONFIG_EFI_STUB=y CONFIG_FB_EFI=y CONFIG_FRAMEBUFFER_CONSOLE=y For UEFI ia32 firmware, it should be possible (in theory, and if I understand correctly) to use 32 bit Syslinux to load a 64 bit kernel, as long as the latter has CONFIG_EFI_MIXED enabled. We have seen reports of failure to boot r...

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 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 http://www.alle-irre.de/~hardy/syslinux/linux-3.2.0-4-amd64/config-3.2.0-4-amd64 Groeten Geert Stappers -- Leven en laten leven

Thanks for the hints - I have NOT CONFIG_EFI enabled - do I need this actually? I do not know which variables I need to boot... The kernel APPEND parameters are sufficient for me... And the relocatable config is set already. .. I enabled the EFI kernel config parts - no change... the console prints: Booting System... Loading linux... ok Loa...

...hat late. (I had some issues with my server's Ethernet NIC, and without it, no PXE / syslinux.) So, it's time to be a bit more specific. The kernel I want to boot in EFI mode is a debian installer. It *has* a module "efivars" loaded. Which means this kernel has been compiled with CONFIG_EFI_VARS, which itself depends on CONFIG_EFI. Therefore I should be able to boot this kernel in EFI mode. I don't remember whether I tried or not, so I'll re-test ASAP. However, as I discussed on IRC, the 'file' command only say "x86 boot sector". Celelibi

...39;s explanation is > congruent with Ady's Linux pre-3.3 kernel research, would you add a link to > this fuller explanation? 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? -- Cheers, Hardy

...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 those values > at http://www.alle-irre.de/~hardy/syslinux/linux-3.2.0-4-amd64/config-3.2.0-4-amd64 > That's why I am asking. If this is an issue that was broken with every kernel release before 3.3 and there's no way to...

...;> Ethernet NIC, and without it, no PXE / syslinux.) >> >> So, it's time to be a bit more specific. >> The kernel I want to boot in EFI mode is a debian installer. It *has* >> a module "efivars" loaded. Which means this kernel has been compiled >> with CONFIG_EFI_VARS, which itself depends on CONFIG_EFI. Therefore I >> should be able to boot this kernel in EFI mode. >> >> I don't remember whether I tried or not, so I'll re-test ASAP. >> However, as I discussed on IRC, the 'file' command only say "x86 boot >&gt...

...listinfo/syslinux > Ok, thanks, things are becoming clearer. I have a success story now. I tested with both 32-bit and 64-bit kernels, got the same problem, that is, nothing after "Loading vmlinuz... ok". I took a punt on something. From the docs, I thought that the kernel parameter CONFIG_EFI_STUB is not required. However, I set it: CONFIG_EFI_PARTITION=y CONFIG_EFI=y CONFIG_EFI_STUB=y CONFIG_EFI_MIXED=y CONFIG_FB_EFI=y CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y CONFIG_EFI_VARS=m # CONFIG_EFIVAR_FS is not set CONFIG_EARLY_PRINTK_EFI=y For a generic x86-64 kernel, after the "Loadi...

> 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

...seeing something after the switch to a graphics mode. Unless the kernel hangs before then. Anyway, I was wondering if anyone reading this has any experience that might suggest why I have the hanging after the "ok". Oh, I suppose for completeness, I should show the config of the kernel: CONFIG_EFI_PARTITION=y CONFIG_EFI=y # CONFIG_EFI_STUB is not set # CONFIG_FB_EFI is not set CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y # EFI (Extensible Firmware Interface) Support CONFIG_EFI_VARS=m # CONFIG_EFIVAR_FS is not set # CONFIG_EARLY_PRINTK_EFI is not set ...hmm, is that last one the cause of the p...

...el hangs >> before then. >> >> Anyway, I was wondering if anyone reading this has any experience that >> might suggest why I have the hanging after the "ok". >> >> Oh, I suppose for completeness, I should show the config of the kernel: >> >> CONFIG_EFI_PARTITION=y >> CONFIG_EFI=y >> # CONFIG_EFI_STUB is not set >> # CONFIG_FB_EFI is not set >> CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y >> # EFI (Extensible Firmware Interface) Support >> CONFIG_EFI_VARS=m >> # CONFIG_EFIVAR_FS is not set >> # CONFIG_...

...raphics mode. Unless the kernel hangs > before then. > > Anyway, I was wondering if anyone reading this has any experience that > might suggest why I have the hanging after the "ok". > > Oh, I suppose for completeness, I should show the config of the kernel: > > CONFIG_EFI_PARTITION=y > CONFIG_EFI=y > # CONFIG_EFI_STUB is not set > # CONFIG_FB_EFI is not set > CONFIG_DMI_SCAN_MACHINE_NON_EFI_FALLBACK=y > # EFI (Extensible Firmware Interface) Support > CONFIG_EFI_VARS=m > # CONFIG_EFIVAR_FS is not set > # CONFIG_EARLY_PRINTK_EFI is not set >...

>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

> Thanks for the hints - I have NOT CONFIG_EFI enabled - do I need this actually? > I do not know which variables I need to boot... The kernel APPEND parameters are > sufficient for me... And the relocatable config is set already. > > .. I enabled the EFI kernel config parts - no change... the console prints: > > Booting Sys...

...rnel/setup.c | 2 +- arch/x86_64/kernel/setup.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/i386/kernel/setup.c b/arch/i386/kernel/setup.c index 54c72d9..4945931 100644 --- a/arch/i386/kernel/setup.c +++ b/arch/i386/kernel/setup.c @@ -1460,7 +1460,7 @@ #ifdef CONFIG_EFI efi_enabled = 1; #endif - ROOT_DEV = old_decode_dev(ORIG_ROOT_DEV); + ROOT_DEV = old_decode_dev(ORIG_ROOT_DEV); drive_info = DRIVE_INFO; screen_info = SCREEN_INFO; edid_info = EDID_INFO; diff --git a/arch/x86_64/kernel/setup.c b/arch/x86_64/kernel/setup.c index 6d4f025..003667e 10064...

...with my server's > Ethernet NIC, and without it, no PXE / syslinux.) > > So, it's time to be a bit more specific. > The kernel I want to boot in EFI mode is a debian installer. It *has* > a module "efivars" loaded. Which means this kernel has been compiled > with CONFIG_EFI_VARS, which itself depends on CONFIG_EFI. Therefore I > should be able to boot this kernel in EFI mode. > > I don't remember whether I tried or not, so I'll re-test ASAP. > However, as I discussed on IRC, the 'file' command only say "x86 boot > sector". >...

...| 4 ---- init/main.c | 12 ++++++++++++ 4 files changed, 14 insertions(+), 4 deletions(-) diff --git a/arch/i386/kernel/setup.c b/arch/i386/kernel/setup.c index 16784a6..54c72d9 100644 --- a/arch/i386/kernel/setup.c +++ b/arch/i386/kernel/setup.c @@ -1460,6 +1460,7 @@ #ifdef CONFIG_EFI efi_enabled = 1; #endif + ROOT_DEV = old_decode_dev(ORIG_ROOT_DEV); drive_info = DRIVE_INFO; screen_info = SCREEN_INFO; edid_info = EDID_INFO; diff --git a/arch/x86_64/kernel/setup.c b/arch/x86_64/kernel/setup.c index cadbe33..6d4f025 100644 --- a/arch/x86_64/kernel/setup.c +++ b/arch...