similar to: Debugging EFI boot

Hi guys, I'm trying to build HEAD on the firmware branch from git and I'm getting the following errors: make[3]: Entering directory `/home/voltagex/src/syslinux/efi64/efi' gcc -I/usr/include/efi -I/usr/include/efi/x86_64 -DEFI_FUNCTION_WRAPPER -fPIC -fshort-wchar -ffreestanding -Wall -I/home/voltagex/src/syslinux/com32/include -I/home/voltagex/src/syslinux/com32/include/sys

Hi, The latest from the firmware branch is failing to build EFI64 as of the time of this message make[3]: Entering directory `/home/voltagex/src/syslinux/efi64/efi' gcc -I/usr/include/efi -I/usr/include/efi/x86_64 -DEFI_FUNCTION_WRAPPER -fPIC -fshort-wchar -ffreestanding -Wall -I/home/voltagex/src/syslinux/com32/include -I/home/voltagex/src/syslinux/com32/include/sys

How to boot from syslinux 6.01 over PXE (syslinux.efi) into an EFI installed GPT system on a hdd? Via localboot 0 it doesn't work. (no output) Also via chain.c32 hd0 1 it doesn't work. Errormessage: Can not find MBR magic, treat hdd as raw disk. Stop booting.

From: Matt Fleming <matt.fleming at intel.com> For x86_64 versions of gnu-efi >= 3.0s GNU_EFI_USE_MS_ABI is enabled which turns on the Microsoft ABI, allowing the compiler to do all the work of interfacing with the EFI firmware instead of jumping through uefi_call_wrapper(). Add support to turn this on in the gnu-efi headers, otherwise we'll encounter undefined references to

Hello, I tried to boot the new syslinux.efi (32bit) from the released syslinux 6 via PXE. In a wireshark trace I can see that the syslinux.efi was loaded successfully via TFTP. Then the client try to load ldlinux.e32. I see the request and also the acknoledgement in the trace. After that the client try to load the file, but the source port is changed to tftp request port + 1. For example:

> Oh, I just remembered, the DNS resolving code isn't fully functional for > EFI. If you replace hostnames with IP addresses, do you see any > different behaviour? Of course, it's possible you're not getting that > far. > > Can you get to a Syslinux prompt with either of these devices? For > example, by using PROMPT 1 in your config file. > > -- > Matt

On Fri, 02 Aug, at 07:51:12PM, Jonas Keidel wrote: > So will the patch be applied in 6.02? It's in 6.02-pre16. -- Matt Fleming, Intel Open Source Technology Center

> Gesendet: Donnerstag, 27. Juni 2013 um 17:44 Uhr > OK, now that's just weird. You don't see any response whatsoever from > tapping at the keys? > > If you set a TIMEOUT, can you run a DEFAULT even though you cannot type? > That's one way to figure out whether the machine is dead at that point > or not. A useful DEFAULT might be reboot.c32, that way even if the

On Tue, 25 Jun, at 09:43:02PM, Matt Fleming wrote: > Aha, yes, you're right. I'll take a look at fixing this. Michael, could you try out Syslinux 6.01-pre2 and see if things are now working for you? -- Matt Fleming, Intel Open Source Technology Center

On 08/01/2013 01:13 AM, Matt Fleming wrote: > > I've got a patch to support LOCALBOOT -1 on EFI, which will boot the > next entry in the EFI Boot Manager (the thing configured with > efibootmgr), and which I'll commit shortly, but it doesn't support > LOCALBOOT 0. > > I'm not actually convinced that we should support LOCALBOOT 0 under EFI. > Even on BIOS,

Dear list, I would like to add and test EFI boot support for a live system. Since I use isolinux and syslinux for everything, I would be glad to have syslinux.efi as boot loader for EFI-only machines, so I can just keep all syslinux.cfg files, help files and boot screen as they are. I checked out version 6.00-pre git of syslinux (the "firmware" branch) and was able to compile efi32 and

Yes, I think so. The integer really means the same as EFI's ExitBootServices. Matt Fleming <matt at console-pimps.org> wrote: >On Fri, 02 Aug, at 07:50:57AM, H. Peter Anvin wrote: >> I don't know if there is a meaningful difference between "localboot >-1" >> and "localboot 0" on EFI... they are really two different ways to ask >> the BIOS

Hello! is it possible to boot a 32 Bit Kernel on 64 EFI firmware with Syslinux? I copied "efi64/efi/syslinux.efi", all files inside "efi64/com32/modules" and the file "ldlinux.e64" to my boot partition. with this configuration I am able to boot a 64 bit kernel. but not 32bit Kernel. does anyone knows how to do it? Best Regards

Am 01. Juli 2013 18:13:25 schrieb Matt Fleming <matt at console-pimps.org>: > > Does reverting to -pre4 make things work again? > > -- > Matt Fleming, Intel Open Source Technology Center Yes, with pre4 it work. But as I wrote the problem during searching for the configfile and hung from the program already exist. Gesendet mit AquaMail f?r Android http://www.aqua-mail.com

The following changes since commit c647008831aed653e54c4c8470e3a9db5d0a140a: efi/: Fix displayed version; add DATE (2013-10-20 10:45:53 -0400) are available in the git repository at: git://github.com/geneC/syslinux.git firmware for you to fetch changes up to c647008831aed653e54c4c8470e3a9db5d0a140a: efi/: Fix displayed version; add DATE (2013-10-20 10:45:53 -0400)

On Wed, Nov 20, 2013 at 8:20 AM, Matt Fleming <matt at console-pimps.org> wrote: > On Sun, 20 Oct, at 10:54:13AM, Gene Cumm wrote: >> The following changes since commit c647008831aed653e54c4c8470e3a9db5d0a140a: >> >> efi/: Fix displayed version; add DATE (2013-10-20 10:45:53 -0400) >> >> are available in the git repository at: >> >>

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:

On Thu, May 9, 2013 at 6:39 AM, syslinux-bot for Matt Fleming <matt.fleming at intel.com> wrote: > Commit-ID: fe283b78c973268f2d1f0309826ceeb5c9e8978d > Gitweb: http://www.syslinux.org/commit/fe283b78c973268f2d1f0309826ceeb5c9e8978d > Author: Matt Fleming <matt.fleming at intel.com> > AuthorDate: Fri, 22 Mar 2013 14:54:09 +0000 > Committer: Matt Fleming

On 05/10/2013 06:27 AM, syslinux-bot for Matt Fleming wrote: > > diff --git a/efi/main.c b/efi/main.c > index 31f0bff..27e7f8f 100644 > --- a/efi/main.c > +++ b/efi/main.c > @@ -1177,13 +1177,10 @@ static void efi_setcwd(CHAR16 *dp) > > EFI_STATUS efi_main(EFI_HANDLE image, EFI_SYSTEM_TABLE *table) > { > + EFI_PXE_BASE_CODE *pxe; > EFI_LOADED_IMAGE *info;

> OK, staring at this packet dump, I see that your firmware isn't setting > a default value for the IP TTL field, but seeing as the UEFI spec > doesn't require this, that's a Syslinux bug. Interestingly, the firmware > on my test machine does fill out the TTL field with a value of 64. > > -- > Matt Fleming, Intel Open Source Technology Center > Some