- Posts: 12169
- Thank you received: 4153
Thanks I've passed that on. He'll probably call himself frk (Francesco)I'm also on the discord, and I am fluent in Italian
discord.gg/WwMfD9v9M
If your Italian friend wants to hop in, I'll be glad to help him out.
Please Log in or Create an account to join the conversation.
I don't really see any difference between 12 & 13 (everything is 13 here). From earlier feedback on the preempt_rt email group, The preempt_rt network latency issues were most likely introduced in kernel 5.9 and Debian 11 had 5.10 but because Linuxcnc never released anything on 11, the issues did not appear until Debian 12 which I used from the original beta release.I've used debian 10 11 and 13
I skipped debian 12 this is for internal timing release reasons, not because 12 had anything wrong with it. I did not notice on my hardware considerable differences between debian releases.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
You can use a udev rule to do this. we use one for ethercat to use as an example. You might be able to extend the ethercat script to add ethtool commands for:With ec_igb or ec_igc native driver: interrupt moderation is irrelevant, they use polling not interrupt.
With ec_generic: interrupt moderation is active and you should disable it with
ethtool -C <iface> adaptive-rx off rx-usecs 0 tx-usecs 0
probably as soon as possible on boot, before ethercat starts.
To know which drive you are using, check your erhercat.conf file
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.