Do you have any need for a custom kernel? What isn't working with the one you installed in the snapshot?
On Mon, Dec 9, 2013 at 3:07 PM, jordon <open...@sirjorj.com> wrote: >> On Dec 9, 2013, at 11:40, Remco <re...@d-compu.dyndns.org> wrote: >> >> jordon wrote: >> >>> Every time I have installed the arm7 port on my BBB, fetched latest, and >>> built, I end up with a device with no network connectivity. Any input on >>> how to build this would be most welcome. An updated snapshot would be >>> welcome as well! >>> >>> Jordon >> >> You may be running into this: >> http://www.openbsd.org/faq/current.html#20131031 >> >> 2013/10/31 - new routing message version >> To convert the route expire time to 64 bit, it was necessary to change the >> routing message structure. Make sure that you boot a new kernel before >> replacing the user land programs. >> A small compatibility layer allows to configure addresses with old ifconfig >> and new kernel. Old route get also works in this setup. Old dhclient with new >> kernel assigns the address but hangs. Make sure to reboot your machine >> sucessfully during transition. >> >> >> I'm experiencing the dhclient hang, after DHCPACK, since I didn't update >> userland (yet). Cancelling (^C) it during boot and statically configuring the >> network interface seems to work though. > > I don't think that's it. After building and installing kernel and userland > from latest source, and rebooting, there is no longer a network device in > ifconfig. The Ethernet device is gone. > > I could try it again this evening, or at least start - it takes a couple days > to build the userland. You're saying reboot after installing new kernel but > before building new userland?
