Issues with Network Processor demo

[HelloKayT]

I'm trying to work through the 04_network_processor notebook on a PYNQ-Z1 board running the most recent version of the PYNQ image (v2.3).

I'm running into the some issues with the LinkManager cell. First, it appears that the commands cannot execute from within the notebook. When I sudo the commands individually in the terminal, I get the following error while loading the kernel module:
insmod: ERROR: could not insert module /usr/local/lib/python3.6/dist-packages/pynq_networking/kernel_module/pynqenet.ko: Invalid module format
and I see the following error in the output from dmesg:
pynqenet: disagrees about version of symbol module_layout

I believe these errors are due to a differing kernel version between what the PYNQ board is running (4.14) and what the module was compiled against (4.9). Would it be possible to get an upgraded module compiled against the 2.3, or upcoming 2.4 PYNQ image? (I'm working with @drichmond and he suggested as much)

[drichmond]

Hi @yunqu,

@HelloKayT met with @stephenneuendorffer at FPGA. He says that we just need the kernel image rebuilt.

Would you be able to provide this?

[yunqu]

@drichmond Any steps to do this?

[drichmond]

The process is briefly described here: https://github.com/Xilinx/PYNQ-Networking/tree/master/pynq_networking/kernel_module

…

On Mar 4, 2019, at 10:34 AM, Yun Rock Qu ***@***.***> wrote: @drichmond <https://github.com/drichmond> Any steps to do this? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#10 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGFUdJag1l_nP7bQhKele1PG-slvhQznks5vTWdTgaJpZM4bIKih>.

[yunqu]

This is assuming we had our old kernel building flow, while right now we are trying to do petalinux. I tried to do this before but I am not quite sure how to do it.

[drichmond]

Could we rebuild the kernel object on a board with a PYNQ 2.4 image? That seems like it would simplify the process

…

On Mar 4, 2019, at 10:42 AM, Yun Rock Qu ***@***.***> wrote: This is assuming we had our old kernel building flow, while right now we are trying to do petalinux. I tried to do this before but I am not quite sure how to do it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#10 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGFUdOHIfJBwVBzj8H587zoScTj5iYWyks5vTWkrgaJpZM4bIKih>.

[drichmond]

Though, I think we need the petalinux header files (which are not on the board)

…

On Mar 4, 2019, at 10:45 AM, Dustin Richmond ***@***.***> wrote: Could we rebuild the kernel object on a board with a PYNQ 2.4 image? That seems like it would simplify the process > On Mar 4, 2019, at 10:42 AM, Yun Rock Qu ***@***.*** ***@***.***>> wrote: > > This is assuming we had our old kernel building flow, while right now we are trying to do petalinux. I tried to do this before but I am not quite sure how to do it. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub <#10 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGFUdOHIfJBwVBzj8H587zoScTj5iYWyks5vTWkrgaJpZM4bIKih>. >

[yunqu]

Let me try this. Will get back to you later.

[drichmond]

Thanks Rock!

…

On Mar 4, 2019, at 11:17 AM, Yun Rock Qu ***@***.***> wrote: Let me try this. Will get back to you later. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#10 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGFUdD2rdchLEWkURQqQg-bCo65XiH7Nks5vTXFEgaJpZM4bIKih>.

[yunqu]

I think I have recompiled the ko file:
https://github.com/yunqu/PYNQ-Networking/tree/master

This branch has the compiled ko file, and the boot files. Not sure what else I need.

The kernel module does not seem to bring up br0 successfully.

Steps-
In your petalinux-project of your sdbuild/build/Pynq-Z1/petalinux_project directoy, run

petalinux-create -t modules -n pynqenet --enable
petalinux-build -c kernel
petalinux-build -c pynqenet -x do_install

ko file will be generated under sdbuild/build/Pynq-Z1/petalinux_project/build/tmp/work/plnx_zynq7-xilinx-linux-gnueabi/pynqenet/1.0-r0.

I also regenerated the BOOT.BIN and uImage, and replaced the original files in my boot partition.

[drichmond]

Thanks Rock! This seems to work. The kernel module installs on my board and I can see it with lsmod. However, there are some unrelated (and other unknown issues). For instance - The Python3.6 installation path has changed in PYNQ 2.3+. The library has hardcoded paths - The scapy library seems to be deprecated/renamed, and uses kamene instead (easy name switch) - The mosquitto library must be installed with apt I can run the 01, 02, 04, and 05 notebooks. I can’t run the 03 notebook (cell 5 fails with ICMP errors). I can send more detailed error messages if necessary. Dustin

…

On Mar 4, 2019, at 1:51 PM, Yun Rock Qu ***@***.***> wrote: I think I have recompiled the ko file: https://github.com/yunqu/PYNQ-Networking/tree/master <https://github.com/yunqu/PYNQ-Networking/tree/master> This branch has the compiled ko file, and the boot files. Not sure what else I need. The kernel module does not seem to bring up br0 successfully. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#10 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGFUdIqYGGRNvwXkA7ZND7LgLekb2q9vks5vTZVNgaJpZM4bIKih>.

[yunqu]

@drichmond Can you tell me what you did?

Feel free to pull request on my master branch so I can also replicate your progress.

You can open another thread if you think the error message is not related to this thread.

[drichmond]

Yeah, I’ll open a new PR later today.

…

On Mar 5, 2019, at 9:11 AM, Yun Rock Qu ***@***.***> wrote: @drichmond <https://github.com/drichmond> Can you tell me what you did? Feel free to pull request on my master branch so I can also replicate your progress. You can open another thread if you think the error message is not related to this thread. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#10 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGFUdNZq32gOVLCr9F5r8le3T6uQT34mks5vTqUkgaJpZM4bIKih>.