search for: config_relocat

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

...ased-4175521209/#post5270515 leaded to this message: "Cannot relocate kernel, bailing out" That leaded me to this post in the ML: http://www.zytor.com/pipermail/syslinux-commits/2013-July/002381.html The kernel in the image file being not relocatable. I'll replace it with one with CONFIG_RELOCATABLE=Y to confirm the issue. But meanwhile, is there some other thing I can do, like moving the kernel elsewhere in the image? Currently the tree is: . |-- EFI | `-- BOOT | |-- bootx64.efi | |-- bzImage | |-- f2.txt | |-- initrd.img | |-- ldlinux.c32 | |-- ldlinux.e64 | |-- ldlinux.sys | |-- memte...

...s message: > > "Cannot relocate kernel, bailing out" > > That leaded me to this post in the ML: > http://www.zytor.com/pipermail/syslinux-commits/2013-July/002381.html > > The kernel in the image file being not relocatable. I'll replace it > with one with > CONFIG_RELOCATABLE=Y to confirm the issue. With CONFIG_RELOCATABLE=Y (only change to the kernel) the installer bow boots OK, > But meanwhile, is there some other thing I can do, like moving the > kernel elsewhere in the image? Stupid idea, of course. I should have dropped an eye on /usr/src/linux/Documenta...

...elocate kernel, bailing out" > > > > That leaded me to this post in the ML: > > http://www.zytor.com/pipermail/syslinux-commits/2013-July/002381.html > > > > The kernel in the image file being not relocatable. I'll replace it > > with one with > > CONFIG_RELOCATABLE=Y to confirm the issue. > With CONFIG_RELOCATABLE=Y (only change to the kernel) the installer > bow boots OK, > > But meanwhile, is there some other thing I can do, like moving the > > kernel elsewhere in the image? > Stupid idea, of course. I should have dropped an eye on...

...eb 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 EFISTUB, the kernel config should include: > > > > CONFIG_RELOCATABLE=y > > CONFIG_EFI=y > > CONFIG_EFI_STUB=y > > CONFIG_FB_EFI=y > > CONFIG_FRAMEBU...

...l upstream archives version 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...

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

...pike 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 2014 explained this pre-Linux-3.3 kernel problem well...

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

...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 kernel problem well. It was a discussion of...

...subscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux > I really wish one of the (past or present) Syslinux developers would reply to this issue. Last month, a stable standard Slackware kernel could not be booted by syslinux.efi. It had to be customized with "CONFIG_RELOCATABLE". Now a standard Debian Wheezy stable kernel 3.2 is being reported as not bootable with Syslinux 6.03, but successfully bootable with Syslinux 6.01. IMHO, this should be considered a Syslinux regression. It sounds as if syslinux.efi 6.03 is only capable of booting a Linux kernel 3.3+...

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

...B. The problem is, if you compile x86_64 kernel, the value of CONFIG_PHYSICAL_ALIGN will be fixed, and the next time you compile i386 kernel, previous CONFIG_PHYSICAL_ALIGN value of x86_64(default: 2MB) will be used by default. The follwing patch will fix this problem. With this patch, either CONFIG_RELOCATABLE's option or CONFIG_EMNBEDDED's option is set "Y", you can configure the value of CONFIG_PHYSICAL_ALIGN. Signed-off-by: Yoshimi Ichiyanagi <ichiyanagi.yoshimi@lab.ntt.co.jp> --- diff --git a/arch/i386/Kconfig b/arch/i386/Kconfig index f952493..05c3316 100644 --- a/arc...

...B. The problem is, if you compile x86_64 kernel, the value of CONFIG_PHYSICAL_ALIGN will be fixed, and the next time you compile i386 kernel, previous CONFIG_PHYSICAL_ALIGN value of x86_64(default: 2MB) will be used by default. The follwing patch will fix this problem. With this patch, either CONFIG_RELOCATABLE's option or CONFIG_EMNBEDDED's option is set "Y", you can configure the value of CONFIG_PHYSICAL_ALIGN. Signed-off-by: Yoshimi Ichiyanagi <ichiyanagi.yoshimi@lab.ntt.co.jp> --- diff --git a/arch/i386/Kconfig b/arch/i386/Kconfig index f952493..05c3316 100644 --- a/arc...

Am 07.12.2014 schrieb 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 the...

...op. > Between these 2 strings is the gunzip() function at = > boot/compressed/misc.c which does the real job, and the problem seemed = > to appear since commit 1ab60e0f72f71ec54831e525a3e1154f1c092408. = > (2.6.22-rc1 hangs, 2.6.21.6 works). The problem occurs with or without = > CONFIG_RELOCATABLE enabled. > > What are the possible solutions to confirm where the problem is coming = > from ? Since I was just involved in the boot decompressor for another bug, I = took a look at this. 2.6.22 switches it to be 64-bit code. VT is very = picky about what state it can run in. No...

...op. > Between these 2 strings is the gunzip() function at = > boot/compressed/misc.c which does the real job, and the problem seemed = > to appear since commit 1ab60e0f72f71ec54831e525a3e1154f1c092408. = > (2.6.22-rc1 hangs, 2.6.21.6 works). The problem occurs with or without = > CONFIG_RELOCATABLE enabled. > > What are the possible solutions to confirm where the problem is coming = > from ? Since I was just involved in the boot decompressor for another bug, I = took a look at this. 2.6.22 switches it to be 64-bit code. VT is very = picky about what state it can run in. No...

Finally, the Syslinux 6.00 release is out. This release includes support for booting from EFI, both from disk-based media and over the network via PXE. Thanks to everyone who has been testing this out. There are some EFI bugs that I'm aware of, * booting Linux kernels without CONFIG_RELOCATABLE doesn't work * 64-bit syslinux.efi cannot boot 32-bit kernels and vice versa * displaying of Fn files messes up the console Please do test out the release and report any regressions. I'm particularly interested to hear about any problems with the BIOS code, which will be a result o...

...l/git/groeck/staging (2011-08-13 18:37:28 -0700) are available in the git repository at: ssh://master.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-for-linus.git master Rusty Russell (2): virtio: Add text copy of spec to Documentation/virtual. lguest: allow booting guest with CONFIG_RELOCATABLE=y Documentation/virtual/00-INDEX | 3 + Documentation/virtual/lguest/lguest.c | 3 + Documentation/virtual/virtio-spec.txt | 2200 +++++++++++++++++++++++++++++++++ 3 files changed, 2206 insertions(+), 0 deletions(-) create mode 100644 Documentation/virtual/virtio-spec.txt

...l/git/groeck/staging (2011-08-13 18:37:28 -0700) are available in the git repository at: ssh://master.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-for-linus.git master Rusty Russell (2): virtio: Add text copy of spec to Documentation/virtual. lguest: allow booting guest with CONFIG_RELOCATABLE=y Documentation/virtual/00-INDEX | 3 + Documentation/virtual/lguest/lguest.c | 3 + Documentation/virtual/virtio-spec.txt | 2200 +++++++++++++++++++++++++++++++++ 3 files changed, 2206 insertions(+), 0 deletions(-) create mode 100644 Documentation/virtual/virtio-spec.txt