Ver 2.9.4 iso clean install Trouble when disabling EOE

I upgraded to ver 2.9.8 and I did disable eoe procedure again.
But then I cound not move EtherCAT servo motor (YASKAWA). ( I could not reset error )

I have attached files about dmesg and procedure to disable eoe.

Please help me solve this problem.
 

This was a complete new install from ISO, wasn't it?
Did you install the r8168-dkms driver again?
 

I used previous PC,
1. Installed by 2.9.4 iso , 
2. Upgraded 2.9.5
3. EOE recompile, r8168-dkms
4. Worked.
5. Upgraded 2.9.8
6. Some command(attached previous)
5. This trouble.

Speaking of r8168,already installed in this PC. But
What should I write in 
 /etc/ethercat.conf,DEVICE_MODULES="generic"?
Is "generic' Ok?

Some of settings may have been initialized by upgrade... I attached what I did after upgrade.

I found some post about upgrade trouble EtherCAT, 
forum.linuxcnc.org/ethercat/45336-etherc...tep?start=180#293489
Should I go back to previous version ?  (But 2.9.5 have some bugs for Jog movement )

I can also reinstall using 2.9.8 iso from the begining next time with another PC.
 

I think after you upgrade your linuxcnc, you might want to build a compatible version of linuxcnc-ethercat
and check your settings
with your hardware generic is inevitable, it is not supported, performance will not be guaranteed. I should look at getting hardware that already has support from IGH
like intel igc or intel igb
but I never got eoe to work, so you are already ahead of me on that front, so I might be just blabbering nonsense...

generic is the right choise.
There used to be a performance difference between generic and say the igb driver.
But not anymore, I always use generic even if I could use igb or igc.

I upgraded to 2.9.8 on a test system and initially saw the same problem you have.
Then I rebooted and made too many things to remember and then it worked again.
So I can only recommend to reboot and cycle the power of the ethercat units.
If that doesn't work, go back to 2.9.5 or try 2.9.8 iso.
Your settings from before is fine.
 

Thank you so much.

Now I installed LinuxCNC to PC (HP Elite 800 G4 with Intel LAN) using 2.9.4 iso,
I did recompile EOE disable along to the procedure, I did not upgrade,

but I could not improve my bad situation in using Yaskawa Drive.

I found ...something strange.
Ethercat service starts automatically,and ethercat slaves works after reboot.( "ehtercat slaves " shows all servo drives )

But I have to do this command to execute LinuxCNC everytime after reboot.

chmod 666 /dev/EtherCAT0

but If I did this, LinuxCNC doesnot handle Yaskawa servo propery (A12).

And also, in Network Connection (in "TASKBAR on the top of Desktop") I could see a NIC Interface that I'm using for "EtherCAT".( see attachment jpeg image)

What am I missing ? What should I check ? 

Halfway down in this post rodw describes how to add a udev rule for /dev/EtherCAT0
forum.linuxcnc.org/ethercat/45336-etherc...-how-to-step-by-step

For the interface, there are many ways. I have the following in /etc/network/interfaces for my ethercat interface
It brings the enp2s0 interface up, without IP address

Check what's in syslog (sudo dmesg) if there are more problem

Thank you so much, Mr Hakan.
I set udev rule, and then I don't need to type "chmod 666 /dev/EtherCAT0" anymore to exec LinuxCNC.

I'm using  PC,  HP Elite800 G4 which have Intel NIC , And I clean installed for 3 times. (In BIOS I disabled SecureBoot )

But all results was same.
Ethercat is unstable. (Alarm A12 flicking,  I can't do anything.  But I could reset if A12 happend before with EoE disabled master, and I could Jog, Run GCode with Yaskawa servo with DELL OLD PC)

I have attached dmesg file.

By the way, which LinuxCNC version (iso?) are good for EtherCAT( Especially DisablingEOE) ?


 

I am getting out of ideas.

It's a new computer so if you haven't done so already, you can check overall latency withand make sure the min and max are below +- 20 microseconds or so.

If that doesn't give anything I think you should go back to the working setup you had
with a laptop. If I understood right that setup worked, with the Realtek dkms driver.
Follow your own notes in this thread.

Ethercat master is always distributed as a package separate from linuxcnc due to licensing constraints.
So there is no better or worse linuxcnc version, they are all the same what concerns ethercat and locally compiled master.