search for: efi_boot_linux

...the recent kernel changes. For > x86-64 we now try to boot a Linux kernel via the 32-bit entry point. > It's possible that code doesn't work correctly with vmware. > > Could you grab -pre10 and change the APPEND argument for your debug.c32 > line to, > > APPEND -e efi_boot_linux handover_boot valid_pecoff_image > > which should hopefully print some info from the kernel boot paths. > > -- > Matt Fleming, Intel Open Source Technology Center > I tried it with pre11, same problem. I modified the debug append line to the one above. I get the following o...

...lecting a 32bit kernel > entry, screen went black for about 2 seconds, then dropped back to > Syslinux menu. 64bit kernel booted just fine. > > Any further info I can give you to debug this? Are there any > specific requirements for the kernel? You could try running, debug.c32 -e efi_boot_linux handover_boot before executing your kernel. What kernel version are you using? -- Matt Fleming, Intel Open Source Technology Center

> Actually, can you grab the version I built from, > > ftp://syslinux.org/pub/syslinux/tests/syslinux-6.02-pre2.tar.gz > > And see whether things work for you? I'm just trying to rule out any > kind of distribution error on the Syslinux build machine. > > -- > Matt Fleming, Intel Open Source Technology Center > _______________________________________________

Hi, Line 762 of efi/main.c (git firmware branch) should be changed to if (hdr->version < 0x20b) { Without this change syslinux efi64 gives out "handover protocol unimplemented error" and fails to boot. With this change syslinux boots the kernels fine (tested with 3.6.9 and 3.7rc6 kernels). Please fix this. Thanks in advance. Regards. Keshav

...t Fleming: > > On Wed, 10 Jul, at 03:44:57PM, Andreas Heinlein wrote: > > > > > > Any further info I can give you to debug this? Are there any > > > specific requirements for the kernel? > > > > You could try running, > > > > debug.c32 -e efi_boot_linux handover_boot > > > > before executing your kernel. > > > Euh how? Where? > > In a syslinux config file? > At the `boot:` prompt? > > Please provide an example. It needs a lot of work but an example is here, http://www.syslinux.org/wiki/index.php/Developm...

On Thu, 25 Jul, at 09:18:30AM, Michael Szerencsits wrote: > I tried it with pre11, same problem. > > I modified the debug append line to the one above. > > I get the following output: > efi_boot_linux: kernel_start 0x1000000 kernel_size 0x472390 initramfs 0x7e3dc998 setup_data 0x0 cmdline 0x9f000 > efi_boot_linux: setup_sects 32 kernel_size 4662160 > > Hope this helps > Regards Michael Thanks, that does help. At least we know it's taking the 32-bit entry path. I opened the fol...

...mage; + goto bail; + } + + +//If we are here the child image has run/finished/returned +efi_console_restore(); + +return 0; + +bail: + printf("EFI Err: %s failed; EFI_STATUS=%d\n", action,status); + printf("Press any key...\n"); + efi_getchar(NULL); + return -1; + +} + + /* efi_boot_linux: * Boots the linux kernel using the image and parameters to boot with. * The EFI boot loader is reworked taking the cue from @@ -1200,6 +1310,8 @@ struct firmware efi_fw = { .get_serial_console_info = serialcfg, .adv_ops = &efi_adv_ops, .boot_linux = efi_boot_linux, + .boot_efi = efi...

...; +efi_console_restore(); > + > +return 0; > + > +bail: > + printf("EFI Err: %s failed; EFI_STATUS=%d\n", action,status); > + printf("Press any key...\n"); > + efi_getchar(NULL); > + return -1; > + > +} > + > + > /* efi_boot_linux: > * Boots the linux kernel using the image and parameters to boot with. > * The EFI boot loader is reworked taking the cue from Body. Style changes warranted. > @@ -1200,6 +1310,8 @@ struct firmware efi_fw = { > .get_serial_console_info = serialcfg, > .adv_ops...

Op 2013-07-11 om 16:17 schreef Matt Fleming: > On Wed, 10 Jul, at 03:44:57PM, Andreas Heinlein wrote: > > > > Any further info I can give you to debug this? Are there any > > specific requirements for the kernel? > > You could try running, > > debug.c32 -e efi_boot_linux handover_boot > > before executing your kernel. Euh how? Where? In a syslinux config file? At the `boot:` prompt? Please provide an example. Regards Geert Stappers In an attempt to grasp the Syslinux dynamic debugger

...Wed, 10 Jul, at 03:44:57PM, Andreas Heinlein wrote: >> > > >> > > Any further info I can give you to debug this? Are there any >> > > specific requirements for the kernel? >> > >> > You could try running, >> > >> > debug.c32 -e efi_boot_linux handover_boot >> > >> > before executing your kernel. >> >> >> Euh how? Where? >> >> In a syslinux config file? >> At the `boot:` prompt? >> >> Please provide an example. > > It needs a lot of work but an example is here, >...

...error is likely being triggered by the recent kernel changes. For x86-64 we now try to boot a Linux kernel via the 32-bit entry point. It's possible that code doesn't work correctly with vmware. Could you grab -pre10 and change the APPEND argument for your debug.c32 line to, APPEND -e efi_boot_linux handover_boot valid_pecoff_image which should hopefully print some info from the kernel boot paths. -- Matt Fleming, Intel Open Source Technology Center

I just released 6.02-pre2 which includes support for booting 32-bit kernels from efi64. I know a number of people wanted this feature, so hopefully it will be tested in various environments. One thing to note is that it is not possible to boot a 32-bit kernel from efi64 via the EFI handover protocol (or from firmware via the EFI boot stub), but the kernel loader in Syslinux is smart enough to

...opriate for the architecture. The code came from klibc. com32/lib has i386 and x86_64 sub directories implementing the code. Architecture dependency in LZO data compression library in subdirectory core/lzo/ is taken care to be able to build fo i386 for x86_64. EFI boot loader in efi_boot_linux() now supports booting i386 and x86_64 linux kernels. Main x86_64 changes are in a) setting up high part of EFI system table and memmap b) loader signature c) setting up jump vector to hand off to kernel. The ELF module load and the utility library routines fully support lookup, resol...

...e --init +#) if [ -d "$objdir/gnu-efi" ];then cd "$objdir/gnu-efi" diff -uprN a/efi/main.c b/efi/main.c --- a/efi/main.c 2014-10-06 10:27:44.000000000 -0600 +++ b/efi/main.c 2015-03-13 12:56:38.747049818 -0600 @@ -1202,6 +1202,8 @@ struct firmware efi_fw = { .boot_linux = efi_boot_linux, .vesa = &efi_vesa_ops, .mem = &efi_mem_ops, + .image = NULL, + .table = NULL }; static inline void syslinux_register_efi(void) @@ -1265,6 +1267,8 @@ EFI_STATUS efi_main(EFI_HANDLE image, EF InitializeLib(image, table); image_handle = image; + efi_fw.image = (void*) image; +...

...opriate for the architecture. The code came from klibc. com32/lib has i386 and x86_64 sub directories implementing the code. Architecture dependency in LZO data compression library in subdirectory core/lzo/ is taken care to be able to build fo i386 for x86_64. EFI boot loader in efi_boot_linux() now supports booting i386 and x86_64 linux kernels. Main x86_64 changes are in a) setting up high part of EFI system table and memmap b) loader signature c) setting up jump vector to hand off to kernel. The ELF module load and the utility library routines fully support lookup, resol...