search for: handover_boot

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

...> 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/Development/Debugging#...

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

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

...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://ww...

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

...nel 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 output: efi_boo...

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