search for: letan

...be updated, but they are not 3. Disabling paging has to be done before disabling long mode, but the implementation does the opposite In most cases, a computer that tries to execute the kernel_jump routine reboot (it can also hangs). This patch fixes the kernel_jump routine. Signed-off-by: Thomas Letan <thomas.letan at ssi.gouv.fr> --- efi/x86_64/linux.S | 61 ++++++++++++++++++++++++++++++++++++------------------ 1 file changed, 41 insertions(+), 20 deletions(-) diff --git a/efi/x86_64/linux.S b/efi/x86_64/linux.S index 0a0e996..972c0b2 100644 --- a/efi/x86_64/linux.S +++ b/efi/x86_64/li...

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

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

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

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. After setting a new GADT, `cs` h...

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

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

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

...d 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 kernels with a 64-bit syslinux > two years ago. There were a bug in syslinux that prevented it, but I was > able to write a patch which is now in the latest tagged version as far > as I remember. > > Best regards, > Thomas...

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. 2015-09-16 8:44 GMT+02:00 Thomas Letan via Syslinux <syslinux at zytor.com>: > Hi. > > Sometimes, it may happen that we do not want to clone a repo (here the > submodule) and just use the version installed in the system. I have > myself one use case. > > Unfortunately, it is not possible to do that with sysli...

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

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

Hi > The effect was simply that the (physical) machine rebooted exactly on > the wrmsr instruction. The result of my investigation was that the > code wasn't following the protocol (by intel and by AMD) for leaving > long mode as pointed out by Thomas Letan. Indeed it's exactly that! > I think qemu and some processors are just more permissive and allow > the current code to work. Yes, I had the same conclusion myself. > Given the code involved, I'm not sure it is relevant whether we want > to boot a 32 bits or 64 bits kernel....

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

...;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 kernels with a 64-bit syslinux >> two years ago. There were a bug in syslinux that prevented it, but I was >> able to write a patch which is now in the latest tagged version as far >> as I remember. >> >> Be...

...kages/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 you for your contribution. -- -Gene > 2015-09-16 8:44 GMT+02:00 Thomas Letan via Syslinux <syslinux at zytor.com>: > >> Hi. >> >> Sometimes, it may happen that we do not want to clone a repo (here the >> submodule) and just use the version installed in the system. I have >> myself one use case. >> >> Unfortunately, it is no...

...ux-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 you for your contribution. > > -- > -Gene > > > 2015-09-16 8:44 GMT+02:00 Thomas Letan via Syslinux <syslinux at zytor.com > >: > > > >> Hi. > >> > >> Sometimes, it may happen that we do not want to clone a repo (here the > >> submodule) and just use the version installed in the system. I have > >> myself one use case. >...

Hello Ady thank you very much for the accurate reply and for saving my time :-) Best Regards, On 17.10.18 18:06, Ady Ady via Syslinux wrote: >> is it possible to boot a 32 Bit Kernel on 64 EFI firmware with Syslinux? > > In theory, booting 32-bit kernels from 64-bit EFI is supposed to be > supported by "efi64/efi/syslinux.efi" since 2013Jun. > > In practice:

2015-09-15 13:57 UTC+02:00, Patrick Masotta <masottaus at yahoo.com>: >>>> > > What's the default strategy for checking out new gnu-efi sources? > > We should have a way to set the version we want to work with > > and only update when we want to do so. > > That's true. All I did in these patches was to inline those shell > scripts in the

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.