[syslinux] core_udp_sendto: no mapping

Gene Cumm
Sun, 10 Dec 2017 19:41:15 -0000

On Wed, Dec 6, 2017 at 6:49 AM, Gene Cumm <gene.cumm at gmail.com>
wrote:
> On Wed, Nov 29, 2017 at 6:30 AM, Gene Cumm <gene.cumm at gmail.com>
wrote:
>> On Tue, Nov 28, 2017 at 2:38 PM, Joakim Tjernlund

>>> Gene, I am curious, do you have an idea how to fix this?
>>
>> Yes, I have an idea but I need to add some debug code so I can
>> understand more how your particular machine is behaving.
>>
>> --
>> -Gene

> On Tue, Nov 28, 2017 at 6:45 AM, Joakim Tjernlund via Syslinux
> <syslinux at zytor.com> wrote:
>
>> But I have tried older versions too. Seems my Lenovo EFI is too
"modern" for syslinux
>> but I think Gene has an idea how to solve it.
>
> Too modern?  Nope, again, broken.  A PxeBc should be atop a MNPSb atop
> a Net.  (EDK shell uses the short names for the GUIDs; EDK2 shell uses
> longer names).  Yours has PxeBc atop a Net with MNPSb on another
> handle.  This is not the first and doubtfully the last we'll
> encounter.  UEFI-2.0 allows this but starting in UEFI-2.1, it MUST
> live atop an MNPSb.
>
> I'm still trying to build something that'll print the paths but
> strangely having issues.
>
> On Mon, Nov 27, 2017 at 6:39 PM, Joakim Tjernlund
> <Joakim.Tjernlund at infinera.com> wrote:
>
>> Fond an old boot logg:
>> [    0.000000] efi: EFI v2.50 by Lenovo
>> [    0.000000] efi:  SMBIOS=0x6f098000  SMBIOS 3.0=0x6f095000
ACPI=0x6fffe000  ACPI 2.0=0x6fffe014  MPS=0x6f468000  ESRT=0x6eb33000
MEMATTR=0x6976d018
>> [    0.000000] ACPI: UEFI 0x000000006FF53000 000042 (v01 LENOVO TP-N1W
00001200 PTEC 00000002)
>> [    0.000000] ACPI: UEFI 0x000000006FF39000 00013E (v01 LENOVO TP-N1W
00001200 PTEC 00000002)
>
> It sure doesn't look 2.5 compliant to me.  Merely adding the new stuff
> from a new UEFI spec version doesn't mean it's compliant with the
> current nor previous versions.  If I'm wrong, I'd love to hear
> especially from the author or someone with first-hand knowledge.
>
> --
> -Gene

Joakim, attached is a TGZ with some test binaries.  I'm assuming the
"imd" will print one device while "mnp" another.  This is
mostly to
firm up which devices it's actually trying to use.  Based on your
other results, this should help a little more to understand how the
code is reacting to your machine.  It won't give me an answer but just
lead me towards the next step.

--
-Gene
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sl604p1g9-x64.tgz
Type: application/x-gzip
Size: 162432 bytes
Desc: not available
URL:
<http://www.zytor.com/pipermail/syslinux/attachments/20171210/8fa047b4/attachment-0001.bin>