Displaying 2 results from an estimated 2 matches for "efi_already_start".
Did you mean:
efi_already_started
2019 Oct 07
3
syslinux.efi and vendor-class-identifier
Ady Ady via Syslinux wrote:
>
>> However, I have just tested the exact same boot procedure using a Dell
>> laptop (Latitude 7480) - and it all worked without a problem - that is,
>> syslinux.efi and ldlinux.e64 were downloaded without a problem - and
>> from a tcpdump, there was *no* DHCP transaction between downloading
>> syslinux.efi and ldlinux.e64
>>
2019 Oct 08
0
syslinux.efi and vendor-class-identifier
...mapping
> core_udp_sendto: aborting on no mapping
> disable UseDefaultAddress
> core_udp_sendto: udp->Configure() unsuccessful (20)
So the 3rd/4th line would have been printed within ~1 second after the
"My IP is" statement. At least we have a value for the error
"EFI_ALREADY_STARTED". I'f I'm reading the protocol book right, we
already have an open handle and it's refusing as a result. I'd guess
when we attempt to use "UseDefaultAddress", it triggers the DHCP
Discover.
As a side note, some installers support booting in BIOS mode with the
CSM...