On Mon, Mar 20, 2017 at 8:44 PM, Jon Seymour <[email protected]> wrote:
> > William, > > I just tried the systemctl stop/start networking scenario again and found > that it does actually work in this case, so the problem I initially > reported does appear to be a startup race condition as you suggest. > > I'll investigate what can be done to fix a boot race along the lines you > suggest. Thanks for your help! > So I'm not exactly sure how to proceed myself, as far as putting your drivers into the initrd, I'd have to read up myself on that. Robert does have a script that updates the initrd, but I'm not clear on if this script would work for this specfic case. If you're good at reading bash scripts . . . root@beaglebone:~# ls /opt/scripts/tools/developers/ apt-proxy.sh rcnee-testing.sh update_bootloader.sh nfs-rsync.sh secondary_rootfs.sh update_initrd.sh If not, google should yield decent results. The file here is update_initrd.sh. Ideally, I think if you're always going to need this adapter, you'd probably want to build the driver statically into the kernel. Otherwise the best option would be inserting the driver into the initrd( initramfs ) image. But the easiest way, would probably be to write a systemd one shot timer that fires off at around maybe 30 seconds after boot. This requires writing the timer, writing an associated service, and a script that the service calls. enabling the timer, etc ,etc. -- 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/CALHSORqkf_WD7hDZLTOYCSAZEZnxWaE7o5Jasb2MSmPsO_ddGA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
