search for: efi_no_media

...; core_tcp_connect: stalling on configure with no mapping > core_tcp_connect: stalling on configure with no mapping > core_tcp_connect: aborting on no mapping > tcp close failed: 17 > > So... this is EFI_NO_MAPPING. Is this very different from the > EFI_NO_MEDIA I get when booting via iPXE? > <<< > > very unlikely.... > A complete wireshark traffic capture would be handy. I will send you one directly. I can reveal now that it will not contain any packets after it has downloaded syslinux.efi. > Are you trying to retrieve anything...

...ct: stalling on configure with no mapping core_tcp_connect: stalling on configure with no mapping core_tcp_connect: stalling on configure with no mapping core_tcp_connect: aborting on no mapping tcp close failed: 17 So... this is EFI_NO_MAPPING. Is this very different from the EFI_NO_MEDIA I get when booting via iPXE? Testing with commit 8702009f yields worse results: >> Booting Embedded LOM 1 Port 1 : HP Ethernet 1Gb 4-port 331i Adapter - NIC (PXE IPv4) >> Booting PXE over IPv4. Station IP address is 10.141.166.254 Server IP address is 10.14...

...lling on configure with no mapping ? ???core_tcp_connect: stalling on configure with no mapping ? ???core_tcp_connect: stalling on configure with no mapping ? ???core_tcp_connect: aborting on no mapping ? ???tcp close failed: 17 So... this is EFI_NO_MAPPING. Is this very different from the EFI_NO_MEDIA I get when booting via iPXE? <<< very unlikely.... A complete wireshark traffic capture would be handy. Are you trying to retrieve anything using http? >>> Now I upgrade the System ROM to version 1.40 and the NIC Firmware to version 2.15.10. The results: Version 6.0.3 j...

>>> > >???So...this is EFI_NO_MAPPING. Is this very different from the >???EFI_NO_MEDIA I get when booting via iPXE? > <<< > > very unlikely.... <<< I really meant unlikely to be related issues... >>> > A complete wireshark traffic capture would be handy. I will send you one directly. I can reveal now that it will not contain any pac...

...made it very easy to chainload syslinux after ipxe. If dhcpd receives a 0x07, it will respond with ipxe.efi. This will then do a request again with the correct (0x09) architecture upon which dhcpd responds with syslinux.efi. My questions: What can be the cause of error 0x0C which translates to EFI_NO_MEDIA ? How can I enable debugging on the various components involved? If some you have iPXE + syslinux working with UEFI somehow, either through roms in qemu or by chainloading from snponly.efi, ipxe.efi or any other way, please tell me more about your setup? Can there be some mis-configuration som...