Ooops typo ip a to get ethercat nic name sudo apt install ethtool sudo ethtool -i enp0s2
Rod Webster *1300 896 832* +61 435 765 611 Vehicle Modifications Network www.vehiclemods.net.au On Wed, 14 Dec 2022 at 21:18, Rod Webster <r...@vehiclemods.net.au> wrote: > Nicklas, > Check the hardware this way. use ip a to get the nic name for the mesa > connection. Say enp0s2 > Then > sudo apt install ethtool -i enp0s2 will report driver and hardware. > The r8169 is the default driver. Others are r8168-dkms and r8125-dkms > Read the r8i68 driver notes. > https://packages.debian.org/bookworm/r8168-dkms > note to restore the original driver you need to apt purge the current > driver (remove won't work...) > I have one ethercat machine with 4 slaves on an Odroid H2+ with the 8125 > NIC and its been OK. > If installing the correct driver does not resolve it, try my kernel. It > needs some testing! > rough kernel build instructions are in the drive folder... > > Good luck. This has taken me months to work out.... > > Rod Webster > *1300 896 832* > +61 435 765 611 > Vehicle Modifications Network > www.vehiclemods.net.au > > > On Wed, 14 Dec 2022 at 20:48, Nicklas SB Karlsson <n...@nksb.eu> wrote: > >> ons 2022-12-14 klockan 05:15 +1000 skrev Rod Webster: >> > Since the 5.10 kernel (eg Bullseye) and above, there has been an >> > issue with >> > excessive network latency with the Debian RT kernel and Realtek >> > network >> > interfaces with Mesa ethernet cards. When it bites, it causes a >> > hm2_eth >> > "error finishing read" and disables the mesa card. By avoiding >> > realtek >> > NIC's a whole swathe of small portable industrial PC's can no longer >> > be >> > used with linuxcnc. A resolution for this issue needs to be found >> > before >> > 2.9 rolls out or there will be massive support issues. >> > >> >> > This issue is restricted to the debian environment. Installing a >> > compiled >> > kernel or running on a non-debian distribution solves the issue (I >> > tried >> > arch-linux) >> > >> > By default Debian uses the r8169 network driver for all realtek NIC's >> > but >> > provides a r8168-dkms driver which should solve the issue if >> > installed if >> > supported hardware is present. However, it appears that when this is >> > installed, the network latency is rarely resolved. I suspect it is >> > because >> > of a buggy driver in Debian. Some people (PCW, JT et al) have >> > resorted to >> > compiling the kernel from pristine sources. >> > >> > I have finally been able to compile a 6.1 version of the PREEMPT_RT >> > kernel >> > and headers which I have stored in Google Drive >> >> Have had problem with ethercat message disappear then more than a few >> cards are connected in series. Using lsmod I could see mdio_devres >> r8169 so maybe this also explain the problem with Ethercat. >> >> Have however not yet checked. >> >> Nicklas Karlsson >> >> >> >> _______________________________________________ >> Emc-developers mailing list >> Emc-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-developers >> > _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers