Age | Commit message (Collapse) | Author |
|
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.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
It seems that Connman disables ALL interfaces on startup, even if
they are listed in NetworkInterfaceBlacklist. This leads to the
following situation:
networkd starts...
usb0 gets created...
networkd sets the device up (event triggered)
connman starts... and sets the device down!
networkd does not restart the device in this situation. To avoid
the situation, create the USB Gadget functions after connman. It
seems that if connman is up and running, it does not touch the
device anymore.
|
|
Add updated version of USB gadget library. Also add a systemd start-
script which loads the default schema located at /etc/usbg/g1.schema.
|