On Fri, Apr 22, 2016 at 6:23 PM, John Syne <[email protected]> wrote:
> Over the past couple of weeks, connman has been updated twice and in each > instance it breaks my BBB over NFS. > > Here is what happens: > > In my /lib/systemd/system/connman.service, I have a line: > > ExecStart=/usr/sbin/connman -n -I eth0 // Prevent connman from managing > eth0 > > which the upgrade changes to: > > ExecStart=/usr/sbin/connman -n > > and that breaks my apt-get upgrade while updating connman because I see: > > nfs: server 10.100.116.105 not responding, still trying > > My only option is to cycle the BBB power and then issue the following > command to complete the connman installation: > > dpkg —configure -a > > Now I am able to boot, but DNS won’t work (connman isn’t managing eth0) > > To fix this, I have to delete > > /usr/lib/tempfile.d/connman/resolv.conf > > and then create a file > > /var/run/connman/resolv.conf > > which /etc/resolv.conf is linked to. > > Is there a better way to deal with this issue? > Ah crap, that's me... Sorry about that.. Yeah, i need to detect eth0 is in connman.service and not remove it. Before i even think about pushing the next connman update.. We had a bug in connman where the wifi softap was no longer coming up.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYhc7QwChjNwF3j_vORo2Y6vvCvyA_HzRA7K7m4UsEn96A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
