search for: efi_unsupport

.... When UseDefaultAddress is TRUE, it passes 0.0.0.0 for StationAddress and NetMask. core_udp_open calls core_udp_configure which calls efiip4configure (BIOS). BIOS validates SA and NM but special-cases both null to allow for proxy. BIOS tries to find the GUID to configure but fails and returns EFI_UNSUPPORTED error, EFIERR(3). Then core_udp_sendto attempts to send the packet even though it was never configured. It does not check for problems, instead relying on the core_udp_recv to timeout. It retries based on the timeout table but before completing all of the retries, the watchdog timer triggers...

...pture using the current commit (43f5efa) from Patrick's repo, .Syslinux.efi is downloaded, there is an ARP and then nothing hits the wire from the client. The internal failing scenario is core_udp_sendto in syslinux calls Udp4Configure BIOS command, (I will grab the packet.) BIOS returns an EFI_UNSUPPORTED (EFIERR (3)) error but tftp_open still tries to transmit a packet and waits for a reply (core_udp_recv). The loop timeout values are long enough that the watchdog eventually times out and reboots the client. In tftp.c (tftp_open) starting at line 240: sendreq: timeout = *timeout_ptr++;...

...ltAddress is TRUE, it passes 0.0.0.0 for StationAddress and > NetMask. core_udp_open calls core_udp_configure which calls efiip4configure > (BIOS). BIOS validates SA and NM but special-cases both null to allow for > proxy. BIOS tries to find the GUID to configure but fails and returns > EFI_UNSUPPORTED error, EFIERR(3). Ahh! I think I have a better solution then. A pedantic note: BIOS implies non-EFI mode. Firmware is a more correct term. What uEFI specification version does your system claim to be compliant with? I'd like to read over the spec for the call to verify things. > Then...

...ses 0.0.0.0 for StationAddress and > > NetMask. core_udp_open calls core_udp_configure which calls > efiip4configure > > (BIOS). BIOS validates SA and NM but special-cases both null to allow for > > proxy. BIOS tries to find the GUID to configure but fails and returns > > EFI_UNSUPPORTED error, EFIERR(3). > > Ahh! I think I have a better solution then. > > A pedantic note: BIOS implies non-EFI mode. Firmware is a more correct > term. > > What uEFI specification version does your system claim to be compliant > with? I'd like to read over the spec for...

...l from several different packets when needed. Failing scenario/behavior for problem 2: After syslinux.efi is downloaded and execution begins, no further Ethernet communication occurs. This is caused by incomplete packets that are dropped in the client instead of being sent. The return code is EFI_UNSUPPORTED but the error is ignored after the return from the UDP send command in BIOS. Should this be handled differently? Resolution for problem 2: This is my implementation. Hopefully it is a good start to help us get to the correct approach. In pxe.c, I populate DhcpAck packet with all of the corre...

...ets when needed. > > Failing scenario/behavior for problem 2: > > After syslinux.efi is downloaded and execution begins, no further Ethernet > communication occurs. This is caused by incomplete packets that are > dropped in the client instead of being sent. The return code is > EFI_UNSUPPORTED but the error is ignored after the return from the UDP > send command in BIOS. Should this be handled differently? > > Resolution for problem 2: > > This is my implementation. Hopefully it is a good start to help us get to > the correct approach. In pxe.c, I populate DhcpAck pac...

From: Sylvain Gault <sylvain.gault at gmail.com> I don't know if I should merge those trivial warning fix into one commit. I can reformat it as requested. Those are a few warning fixes for the efi part. The code involved has mainly been introduced in recent commits. Sylvain Gault (3): efi: fix warnings about argument types efi: fix pointer-type mismatch assigment warning efi: fix

...ng several packets cached... >>> Failing scenario/behavior for problem 2: After syslinux.efi is downloaded and execution begins, no further Ethernet communication occurs. This is caused by incomplete packets that are dropped in the client instead of being sent. The return code is EFI_UNSUPPORTED but the error is ignored after the return from the UDP send command in BIOS. Should this be handled differently? <<< Have you applied the patch mentioned on this thread??? Best, Patrick

from: Jeff Sloan <jeff_sloan at selinc.com> Based on commit: 9314e330 Setting UseDefaultAddress to TRUE uses invalid StationAddress and SubnetMask values. This is in a network with a local TFTP/MTFTP server. If the server is local, on the same subnet, UseDefaultAddress is set to false and the client ip and subnetmask are loaded, otherwise set UseDefaultAddress to TRUE. This is added to