One message from journal which I don't know what actually means: "is interface usb0 up and configured?: Cannot assign requested address". Does that mean, that bbb-eMMC-flasher-eewiki-ext4.sh is called too early?
On Sunday, 16 April 2017 14:12:33 UTC+2, Igor Jędrzejczak wrote: > > Thank you Robert for a quick answer. Unfortunately disabling that script > didn't help and I still have to plug int eth cable in order to 'unlock' > ethernet over USB. > > I had an idea, that maybe setting eth to allow-hotplug instead of auto in > /etc/network/interfaces might help, but did only for one boot - later the > system needed 90s to shut down, and when booted again I couldn't connect > through USB anymore... > > When should I actually run bbb-eMMC-flasher-eewiki-ext4.sh? I tried: > - from rc.local with settings After=network.target > in /etc/systemd/system/rc-local.service and After=network-online.target in > /etc/systemd/system/rc-local.service.d/debian.conf > - from rc.local with settings After=network.target > in /etc/systemd/system/rc-local.service and After=network.target in > /etc/systemd/system/rc-local.service.d/debian.conf > - from rc.local with settings After=local-fs.target > in /etc/systemd/system/rc-local.service and After=local-fs.target.target in > /etc/systemd/system/rc-local.service.d/debian.conf > > How about setting usb0 to auto in /etc/network/interfaces? > > It seems to me, that either ssh or USB0 gets up only after plugging > ethernet cable... > > Journal output after disabling generic service: > https://pastebin.com/2hLpHTnW > > Regards > > On Sunday, 16 April 2017 03:51:44 UTC+2, Igor Jędrzejczak wrote: >> >> Hi, >> >> I'm having an issue with connection to my BBBI over USB. I have installed >> today a new system on the board - Ubuntu 16.04.2 with 4.9.21-ti-rt-r29 >> kernel. I've been following the steps from here: >> https://eewiki.net/display/linuxonarm/BeagleBone+Black >> >> Now, that my system is flashed to eMMC and (almost) ready to use, I have >> a strange issue with USB connection. When I plug in my USB cable and >> connect host PC with BBB, after ~30s of booting, my host finally gives me >> an announcement that new wired connection was made. Then when I try "ssh >> [email protected]" connection gets refused... Now the funny thing is >> that when I plug in an ethernet cable to BBB, after few seconds I can try >> again with "ssh [email protected]" and then it works - until the next >> boot... >> >> I have copied beaglebone-black-g-ether-load.sh script to my beaglebone >> and am calling it from /etc/rc.local (whose settings I have changed to be >> called after file system is initialized, not as it was set up previously >> after network interfaces are up - then I had even worse situation where I >> have been getting connection timeouts instead of refusal) >> >> I'm out of ideas... I'll appreciate every hint. Below some basic commands >> outputs: >> ubuntu@arm:~$ uname -a >> Linux arm 4.9.21-ti-rt-r29 #1 SMP PREEMPT RT Sat Apr 15 00:04:36 CEST >> 2017 armv7l armv7l armv7l GNU/Linux >> >> dmesg https://pastebin.com/FXEn1knE >> >> ifconfig https://pastebin.com/5NseyN1P >> >> journalctl https://pastebin.com/RhbFPdEa >> >> Regards >> > -- 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/1a7b1b44-4c3d-466a-826f-b92bbb2bf34b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
