search for: add_efi_memmap

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

...ated after that, in later kernel versions (at least kernel v.3.8). Quote: "Protocol 2.12: (Kernel 3.8) Added the xloadflags field and extension fields to struct boot_params for loading bzImage and ramdisk above 4G in 64bit." Question for (kernel) developers: Could APPENDing the "add_efi_memmap" kernel option be involved in allowing the whole RAM to be seen by a 32-bit PAE kernel (booted by syslinux.efi X64)? Quote: "add_efi_memmap include EFI memory map of available physical RAM" As of today, the "Extensible Firmware Interface kernel tree" [2] repository (m...

.../cgit/linux/kernel/git/torvalds/linux.git/plain/Do cumentation/x86/boot.txt there is: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/Do cumentation/x86/x86_64/uefi.txt "CONFIG_RELOCATABLE" is not mentioned in this "uefi.txt" document, but there is "add_efi_memmap" as boot parameter. I wonder if "add_efi_memmap" can be of any help when the kernel was not built with "CONFIG_RELOCATABLE". Considering the Syslinux commit: http://www.zytor.com/pipermail/syslinux-commits/2013-July/002381.html "We don't absolutely need a kerne...

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: