search for: config_efi_stub

...ticular 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. > > We have seen report...

...EFI mode, >> will the driver efivars have access to the EFI variables? Or does the >> kernel need to be recompiled specially for EFI? > > Doubtful. Yes (although I think most EFI kernels I've seen will > function for both). Just to be clear, it requires enabling of `CONFIG_EFI_STUB` configuration variable right? Because although I'm using one of the pre-release versions of `6.02` which should support x32 kernel loading (with x64 UEFI) it still doesn't work for me. (Although I haven't fiddle too much with it.) Ciprian.

..."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 relocatable kernels...

...t; > 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....

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

...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 "Loading vm...

> 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

...driver efivars have access to the EFI variables? Or does the >>> kernel need to be recompiled specially for EFI? >> >> Doubtful. Yes (although I think most EFI kernels I've seen will >> function for both). > > > Just to be clear, it requires enabling of `CONFIG_EFI_STUB` > configuration variable right? > > Because although I'm using one of the pre-release versions of > `6.02` which should support x32 kernel loading (with x64 UEFI) it > still doesn't work for me. (Although I haven't fiddle too much with > it.) If I understood cor...

...o the EFI variables? Or does the >>>> kernel need to be recompiled specially for EFI? >>> >>> Doubtful. Yes (although I think most EFI kernels I've seen will >>> function for both). >> >> >> Just to be clear, it requires enabling of `CONFIG_EFI_STUB` >> configuration variable right? >> >> Because although I'm using one of the pre-release versions of >> `6.02` which should support x32 kernel loading (with x64 UEFI) it >> still doesn't work for me. (Although I haven't fiddle too much with >> i...

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

...gt; 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 generate an appropria...

On 6/7/19 10:48 PM, H. Peter Anvin via Syslinux wrote: > On 6/7/19 10:34 PM, H. Peter Anvin via Syslinux wrote: >> On 6/7/19 10:25 PM, H. Peter Anvin via Syslinux wrote: >>>> >>>> However, the CRC polynomial for zlib and the Linux kernel should both be the >>>> same: 0x04c11db7. >>> >>> I just double-checked, and the CRC tables are

...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 problem? When I do get this working, I shal...

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

...e 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 prob...

>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

...v vmlinuz-5.2.0-rc1-2.gb225e5a-default-nosig-fixed.gz method crc date time compressed uncompressed ratio uncompressed_name defla ffffffff Jun 9 20:30 8120363 8485248 4.3% vmlinuz-5.2.0-rc1-2.gb225e5a-default-nosig-fixed So we need to 1. Check for CONFIG_EFI_STUB 2. Check if kernel ever contained certificates (PE Certificate Table) 3. Get offset from PE Certificate Table 4. crc32 kernel until offset and skip PE Certificate Table 5. Compare checksum Sebastian

...(cflags-y) KBUILD_CFLAGS += -mno-mmx -mno-sse KBUILD_CFLAGS += $(call cc-option,-ffreestanding) @@ -87,7 +87,7 @@ endif vmlinux-objs-$(CONFIG_ACPI) += $(obj)/acpi.o -$(obj)/eboot.o: KBUILD_CFLAGS += -fshort-wchar -mno-red-zone +$(obj)/eboot.o: KBUILD_CFLAGS += -fshort-wchar vmlinux-objs-$(CONFIG_EFI_STUB) += $(obj)/eboot.o \ $(objtree)/drivers/firmware/efi/libstub/lib.a -- 2.17.1

Hello, My question is quite straightforward, still I couldn't find an anwser on the interweb. Is it possible to boot the Linux kernels I used to boot in legacy mode, but now in EFI mode? I mean, I would like to keep all my PXE settings with my menus and kernels and stuff, but now boot them in PXE-EFI mode. I've been able to boot on syslinux.efi and keep my config files, but when I try