Syslinux - Jul 2013 - syslinux6 EFI fail to boot via pxe

> 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 bug
> is in the display code, you'll still notice your machine rebooting.
> 
> This is starting to sound like the core EFI code is hitting some nuance
> of your firmware, and it's not handling it correctly.
> 
> -- 
> Matt Fleming, Intel Open Source Technology Center
>
Hi Matt, 

I tried to test the 6.01-pre5 version, but after loading from ldlinux.e64
nothing happen in the trace.
If I test the efi32 in VMWare it comes up with a 'Firmware error' and
close the VMWare.

It seems that syslinux.efi from pre5 is broken

I now would perfrom the tests with pre4

On Mon, 01 Jul, at 04:30:19PM, Michael Szerencsits
wrote:
> I tried to test the 6.01-pre5 version, but after loading from
> ldlinux.e64 nothing happen in the trace.  If I test the efi32 in
> VMWare it comes up with a 'Firmware error' and close the VMWare.
> 
> It seems that syslinux.efi from pre5 is broken
> 
> I now would perfrom the tests with pre4
Does reverting to -pre4 make things work again?

-- 
Matt Fleming, Intel Open Source Technology Center

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