summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStefan Agner <stefan.agner@toradex.com>2015-11-14 01:46:39 +0100
committerStefan Agner <stefan.agner@toradex.com>2015-11-14 01:46:39 +0100
commit8b71694b0a9c4cd9f887d361994fb7f949cea43c (patch)
tree9efce93da64e40ae2a13cc1d5ba3d51b6b0c326f
parentac605527ac8f0cf5ad65a9038e3528fd043924b4 (diff)
libusbg: make sure USB RNDIS Gadget is started before networkd
Despite the reordering of when to load the USB Gadget configuration with commit fadb16f153aa ("libusbg: enable USB Gadgets after Connman to avoid interference") the network device ended up to be down after startup. It seems that there is a race condition in systemd-networkd which triggers especially in combination with USB Gadget, a issue on the systemd issue tracker has been created: https://github.com/systemd/systemd/issues/1784 There have been various changes related to link handling between systemd 219 and the latest version 227. It is possible that the issue is already solved. Until this has been resolved, explicitly load the USB Gadget before starting systemd-networkd seems to get around the issue.
-rw-r--r--recipes-support/libusbg/libusbg/usbg.service2
1 files changed, 1 insertions, 1 deletions
diff --git a/recipes-support/libusbg/libusbg/usbg.service b/recipes-support/libusbg/libusbg/usbg.service
index 4119ed4..19863d0 100644
--- a/recipes-support/libusbg/libusbg/usbg.service
+++ b/recipes-support/libusbg/libusbg/usbg.service
@@ -1,7 +1,7 @@
[Unit]
Description=Load default USB gadget schema g1.schema
ConditionPathExists=/etc/usbg/g1.schema
-After=connman.service
+Before=systemd-networkd.service
[Service]
Type=oneshot