Re: [edk2] EDK II Network Stack Issue
On 1/22/19 6:34 PM, Laszlo Ersek wrote: Okay, summary: - forget the MdePkg and StdLib DSC files, build only AppPkg (or whatever platform DSC it is that produces your UEFI application) - make sure PcdDebugPropertyMask has bitmask 0x06 set when you build AppPkg (or the appropriate platform DSC in question); either modify the same DSC for this, or use the --pcd command line switch - make sure PcdDebugPrintErrorLevel has all the DEBUG_* bits set from "StdLib/EfiSocketLib/Socket.h" that you care about; the methods for setting this PCD are identical to those seen in the previous point. Hope this helps, Laszlo Hello Laszlo, debug prints are working now - thanks for your advice! Greetings, Karin ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
Re: [edk2] EDK II Network Stack Issue
On 2019-01-10 13:40, Karin Willers wrote: On 2019-01-07 20:27, Laszlo Ersek wrote: On 01/04/19 15:02, Karin Willers wrote: G'Day! I'm trying to get networking under edk2 up and running. I tried AppPkg/Applications/Sockets/RawIp4Tx under OVMF. The raw packet is sent out on the network, but the application never returns from the socket close routine. I'm currently using UDK2017 with the latest security patches (downloaded December 18 2018). The network driver under OVMF is the e1000 driver. The effect that the socket close never returns is also visible when running RawIp4Tx on real hardware, so I think the behavior has nothing to do with OVMF or the UEFI itself. Does anyone see similar effects? Any hints on setting up networking under edk2 correctly? The socket (= libc-level networking) APIs are not the most robust ones in edk2, in my -- admittedly limited -- experience. I'd suggest using applications and shell commands that use UEFI protocols instead, for networking. (I understand that could be a challenge if you are porting a standard C program to UEFI.) Thanks Laszlo The reason for this undertaking initially was to compile a Python.efi that supports sockets. We wanted that to be able to run the Chipsec suite with external network test partners under UEFI. The Chipsec guys do provide pre-compiled Pyhon executables, but these do not include the network stack. I think, I have to debug the issue myself ... Greetings, Karin Could please someone shed some light on how to enable debug prints using UefiDebugLibConOut in EfiSocketLib/Socket.c. Enabling debug prints is, IMHO, not very intuitive in edk2 ... Thanks, Karin ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
Re: [edk2] EDK II Network Stack Issue
On 2019-01-07 20:27, Laszlo Ersek wrote: On 01/04/19 15:02, Karin Willers wrote: G'Day! I'm trying to get networking under edk2 up and running. I tried AppPkg/Applications/Sockets/RawIp4Tx under OVMF. The raw packet is sent out on the network, but the application never returns from the socket close routine. I'm currently using UDK2017 with the latest security patches (downloaded December 18 2018). The network driver under OVMF is the e1000 driver. The effect that the socket close never returns is also visible when running RawIp4Tx on real hardware, so I think the behavior has nothing to do with OVMF or the UEFI itself. Does anyone see similar effects? Any hints on setting up networking under edk2 correctly? The socket (= libc-level networking) APIs are not the most robust ones in edk2, in my -- admittedly limited -- experience. I'd suggest using applications and shell commands that use UEFI protocols instead, for networking. (I understand that could be a challenge if you are porting a standard C program to UEFI.) Thanks Laszlo The reason for this undertaking initially was to compile a Python.efi that supports sockets. We wanted that to be able to run the Chipsec suite with external network test partners under UEFI. The Chipsec guys do provide pre-compiled Pyhon executables, but these do not include the network stack. I think, I have to debug the issue myself ... Greetings, Karin ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
[edk2] EDK II Network Stack Issue
G'Day! I'm trying to get networking under edk2 up and running. I tried AppPkg/Applications/Sockets/RawIp4Tx under OVMF. The raw packet is sent out on the network, but the application never returns from the socket close routine. I'm currently using UDK2017 with the latest security patches (downloaded December 18 2018). The network driver under OVMF is the e1000 driver. The effect that the socket close never returns is also visible when running RawIp4Tx on real hardware, so I think the behavior has nothing to do with OVMF or the UEFI itself. Does anyone see similar effects? Any hints on setting up networking under edk2 correctly? Thanks, Karin ___ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
