> 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 Fleming, Intel Open Source Technology Center >Change hostname to IP address, but same problem. Copy the default config to uuid of the system, same problem PROMPT 1 -> I see boot: but cannot do anything. If I press a key nothing happen
On Thu, 27 Jun, at 04:18:04PM, Michael Szerencsits wrote:> Change hostname to IP address, but same problem. > Copy the default config to uuid of the system, same problem > PROMPT 1 -> I see boot: but cannot do anything. If I press a key nothing happenOK, 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
Am 27. Juni 2013 17:44:58 schrieb Matt Fleming <matt at console-pimps.org>:> OK, now that's just weird. You don't see any response whatsoever from > tapping at the keys?That's correct. Nothing happen.> 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.Few seconds after the error "TFTP unknown protocol" is shown, the system reboot. That's without the TIMEOUT and DEFAULT set. But I think it's dead. I would test this tomorrow.> This is starting to sound like the core EFI code is hitting some nuance > of your firmware, and it's not handling it correctly.I agree, because the 32bit version has worked in VMWare (when I remember correct, also the boot text was shown) and the 64bit has worked on the Lenovo system.> -- > Matt Fleming, Intel Open Source Technology CenterRegards Michael Gesendet mit AquaMail f?r Android http://www.aqua-mail.com
> 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