similar to: [PATCH] efi: leaving long mode in kernel_jump routine

On Tue, Aug 4, 2015 at 2:55 AM, Thomas Letan via Syslinux <syslinux at zytor.com> wrote: > Syslinux 6.03 (efi64) fails to boot a 32-bit kernel. The way Syslinux > leaves long mode in kernel_jump assembly routine does not follow AMD64 > specifications. More precisely: > 1. After setting a new GADT, `cs` has to be refresh by doing a long > jump, but it is not > 2. Other

Syslinux 6.03 (efi64) fails to boot a 32-bit kernel. The way Syslinux leaves long mode in kernel_jump assembly routine does not follow AMD64 specifications. More precisely: 1. After setting a new GADT, `cs` has to be refresh by doing a long jump, but it is not 2. Other segments have to be updated, but they are not 3. Disabling paging has to be done before disabling long mode, but the

Actually your Syslinux config is less relevant than the kernel config file. Indeed Syslinux infers the method to use from the kernel image itself. I assume the .config is public. I will take a look as soon as I can Thomas Le 04/08/2015 14:09, intrigeri via Syslinux a ?crit : > Thomas Letan via Syslinux wrote (04 Aug 2015 09:27:38 GMT) : >> Are you using EFI Handover Protocol? >

> On Tue, Aug 4, 2015 at 2:55 AM, Thomas Letan via Syslinux <syslinux at zytor.com> wrote: > Syslinux 6.03 (efi64) fails to boot a 32-bit kernel. The way Syslinux > leaves long mode in kernel_jump assembly routine does not follow AMD64 > specifications. More precisely: > 1. After setting a new GADT, `cs` has to be refresh by doing a long > jump, but it is not > 2.

On Tue, Aug 4, 2015 at 2:55 AM, Thomas Letan via Syslinux <syslinux at zytor.com> wrote: > Syslinux 6.03 (efi64) fails to boot a 32-bit kernel. The way Syslinux > leaves long mode in kernel_jump assembly routine does not follow AMD64 > specifications. More precisely: > 1. After setting a new GADT, `cs` has to be refresh by doing a long > jump, but it is not > 2. Other

2015-08-23 20:09 UTC+02:00, Gene Cumm via Syslinux <syslinux at zytor.com>: > On Tue, Aug 4, 2015 at 2:55 AM, Thomas Letan via Syslinux > <syslinux at zytor.com> wrote: >> Syslinux 6.03 (efi64) fails to boot a 32-bit kernel. The way Syslinux >> leaves long mode in kernel_jump assembly routine does not follow AMD64 >> specifications. More precisely: >> 1.

On Tue, Aug 4, 2015 at 2:55 AM, Thomas Letan via Syslinux <syslinux at zytor.com> wrote: > Syslinux 6.03 (efi64) fails to boot a 32-bit kernel. The way Syslinux > leaves long mode in kernel_jump assembly routine does not follow AMD64 > specifications. More precisely: > 1. After setting a new GADT, `cs` has to be refresh by doing a long > jump, but it is not > 2. Other

Thomas Letan via Syslinux wrote (04 Aug 2015 09:27:38 GMT) : > Are you using EFI Handover Protocol? What we're doing is: label livefailsafe menu label Live (failsafe) kernel /live/vmlinuz2 append initrd=/live/initrd2.img boot=live config live-media=removable apparmor=1 security=apparmor nopersistent noprompt timezone=Etc/UTC block.events_dfl_poll_msecs=1000 splash noautologin

Hi > Maybe I'm missing something, but this has been working flawlessly for > us in Tails so far. What exactly fails? Are you using EFI Handover Protocol? It might explain the difference Thomas

Hi, Thomas Letan via Syslinux wrote (04 Aug 2015 06:55:48 GMT) : > Syslinux 6.03 (efi64) fails to boot a 32-bit kernel. Maybe I'm missing something, but this has been working flawlessly for us in Tails so far. What exactly fails? Cheers, -- intrigeri

>>> > Syslinux 6.03 (efi64) fails to boot a 32-bit kernel. The way Syslinux > leaves long mode in kernel_jump assembly routine does not follow AMD64 > specifications. More precisely: > 1. After setting a new GADT, `cs` has to be refresh by doing a long > jump, but it is not > 2. Other segments have to be updated, but they are not > 3. Disabling paging has to be

> Syslinux 6.03 (efi64) fails to boot a 32-bit kernel. The way Syslinux > leaves long mode in kernel_jump assembly routine does not follow AMD64 > specifications. More precisely: > 1. After setting a new GADT, `cs` has to be refresh by doing a long > jump, but it is not > 2. Other segments have to be updated, but they are not > 3. Disabling paging has to be done before

>>> > Have you tested it? > Have you checked that efi64 loading 64bit kernels is OK from a kernel_jump point of view? For a 32-bit kernel, I did. For a 64-bit kernel, I didn't but I see no reason it should failed. I will try just to be sure. <<< Unfortunately at the moment I cannot test your finding (probably Gene will). Now that you are immerse in the topic it

Hi! Sorry for not responding earlier. I was planning to but I lack time. > AFAIK it seems this patch is even necessary for new kernels in the case > EFI64 boots a 32 Bit kernel, right? I think it is, yes. I will try to do more test myself. I hope I will be able to tell more this week.

> 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 I appreciate the replies. Hopefully someone might be able to come up with some contribution / answer. The Syslinux code has already received at some point some patches regarding the EFI

Thank you for the info, I tested the latest version Syslinux 6.03 (64 bit) and it didn't work. the boot loader text shows up, then the screen freezes. maybe it works only on some specific boards/CPUs. Thank you for the reply's, the problem is now solved by using another Bootloader. Best Regards, On 29.10.18 15:29, Letan Thomas wrote: > I was able to successfully boot 32-bit

> On Sat, Nov 21, 2015 at 1:04 AM, Andrey Plankin via Syslinux > <syslinux at zytor.com> wrote: > > Hello, > > > > I'm booting linux-3.16-686-pae kernel (32-bit) via syslinux.efi 64-bit version. > > After boot linux sees only 2.5G of RAM while system has 32G installed. > > Why not use a 64-bit kernel with such a large machine? > > Do you have

2015-11-26 16:39 UTC+01:00, Ady via Syslinux <syslinux at zytor.com>: > >> On Sat, Nov 21, 2015 at 1:04 AM, Andrey Plankin via Syslinux >> <syslinux at zytor.com> wrote: >> > Hello, >> > >> > I'm booting linux-3.16-686-pae kernel (32-bit) via syslinux.efi 64-bit >> > version. >> > After boot linux sees only 2.5G of RAM

Indeed, the fix is in 6.04-pre1 but not 6.03. See https://repo.or.cz/syslinux.git/commit/ae853e99a7aed22cb28b387e1e3cb32dbf1ab8fa Best regards Le 30/10/2018 ? 08:53, hfekih a ?crit?: > Thank you for the info, > > I tested the latest version Syslinux 6.03 (64 bit) and it didn't work. > > the boot loader text shows up, then the screen freezes. > > maybe it works only

On Wed, Sep 16, 2015 at 10:55 AM, Erwan Velu via Syslinux <syslinux at zytor.com> wrote: > On mageia I'm using the following patch > https://svnweb.mageia.org/packages/cauldron/syslinux/current/SOURCES/syslinux-nogit.patch?revision=600959&view=markup > > > If it does solve your issue to, I could try pushing it into the repo. Commit ID 0f8cbe04 was 8 months ago. Thank