connect dkms and ethercat systemd services

Author: jeonghanlee

README.md

@@ -43,15 +43,6 @@ And one can check the master status as follows:
 etherlabmaster (master)$ ethercat master
 ```
 
-## Notice
-
-Even if we buid the kernel DKMS, one needs the following commands after new Kernel install.
-
-```
-$ sudo dkms autoinstall
-$ sudo systemctl restart ethercat
-
-```
 
 ## Steps
 
@@ -73,15 +64,20 @@ Fixed scheduler settings in dc_user example; use CLOCK_MONOTONIC.
 ### make install
 * Ethercat program (configuration, lib, and others) installation
 
-### make modules_build
-* Kernel modules compiliation
+### make dkms_add
+* dkms add
+
+### make dkms_build
+* dkms build via dkms
+
 
-### make modules_install
-* Kernel modules installation
+### make dkms_install
+* Kernel modules installation via dkms
 
 ### make setup
 
 * Activate the EtherCAT master Network Port
+* Setup the dkms systemd service
 * Setup the ethercat systemd service
 * Put the UDEV rule to allow an user to access the ethercat master port
 * Create the symbolic link for the ethercat executable command

patch/Site/HISTORY.md

@@ -5,3 +5,12 @@ This patch allows us to use the installed etherlab master configuration in a loc
 
 * created by Jeong Han Lee, han.lee@esss.se
 * Thursday, May 24 11:51:52 CEST 2018
+
+
+# after_dkms_service_patch.p0.patch
+
+The dkms.service demon should be run before the ethercat.service will be started. 
+
+```
+etherlabmaster-code (master)$ hg diff script/ethercat.service.in > ../patch/Site/after_dkms_service_patch.p0.patch
+```

patch/Site/README.md

@@ -22,3 +22,5 @@ $hg diff script/ethercatctl.in > ../use_prefix_for_ethercat_conf_path.p0.patch
 ```
 And remove a/b in user_prefix_for_ethercat_conf_path.p0.patch manually.
 
+
+

patch/Site/after_dkms_service_patch.p0.patch

@@ -0,0 +1,16 @@
+diff -r 9e65f782e8a1 script/ethercat.service.in
+--- script/ethercat.service.in	Tue Feb 13 17:16:01 2018 +0100
++++ script/ethercat.service.in	Fri Jul 27 00:04:00 2018 +0200
+@@ -9,8 +9,10 @@
+ # Uncomment this, if the generic Ethernet driver is used. It assures, that the
+ # network interfaces are configured, before the master starts.
+ #
+-#Requires=network.service # Stop master, if network is stopped
+-#After=network.service # Start master, after network is ready
++# Stop ethercat.service, if dkms.service is stopped
++Requires=dkms.service
++# Start ethercat.service, after dkms.service is ready
++After=dkms.service
+ 
+ #
+ # Uncomment this, if a native Ethernet driver is used. It assures, that the

scripts/etherlab_setup.bash

@@ -18,8 +18,8 @@
 #
 # Author  : Jeong Han Lee
 # email   : jeonghan.lee@gmail.com
-# Date    : Thursday, July 26 01:15:45 CEST 2018
-# version : 0.0.5
+# Date    : Friday, July 27 00:06:10 CEST 2018
+# version : 0.0.6
 
 declare -gr SC_SCRIPT="$(realpath "$0")"
 declare -gr SC_SCRIPTNAME=${0##*/}
@@ -294,6 +294,11 @@ ${SUDO_CMD} -v
 activate_ethercat_master_network
 
 
+# Setup Systemd for the DKMS autoinstall
+# dkms.sevice will be started before ethercat.service be started.
+setup_dkms_systemd
+
+
 ## Setup Systemd for the etercat.service
 ## We can put all configuration files and scrpits in ${ETHERLAB_TARGET_PATH}
 ## However, we cannot put ${ECAT_MASTER_SYSTEMD} in any customzied path
@@ -306,9 +311,6 @@ put_udev_rule "${ECAT_KMOD_NAME}"
 
 trigger_udev_rule
 
-# Setup Systemd for the DKMS autoinstall
-# 
-setup_dkms_systemd
 
 
 ${SUDO_CMD} ln -sf ${ETHERLAB_TARGET_PATH}/bin/ethercat  /usr/bin/ethercat