Date: Mon, 24 Dec 2012 15:41:20 -0800 From: Stephen Hurd <shurd@sasktel.net> To: Brett Wynkoop <wynkoop@wynn.com> Cc: freebsd-arm@freebsd.org Subject: Re: Raspberry Pi EABI test image Message-ID: <50D8E820.3050400@sasktel.net> In-Reply-To: <20121224183119.73868caa@ivory.wynn.com> References: <20121224103825.086cd584@fubar.geek.nz> <50D79C5C.1000704@m5p.com> <20121224135512.30c84b7c@fubar.geek.nz> <50D87B88.6080504@m5p.com> <1356371614.1129.114.camel@revolution.hippie.lan> <9727806D-8356-4A98-B609-9B86BC42795F@bsdimp.com> <20121224181829.7a743510@ivory.wynn.com> <20121224183119.73868caa@ivory.wynn.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Brett Wynkoop wrote: > On Mon, 24 Dec 2012 18:18:29 -0500 > Brett Wynkoop <freebsd-arm@wynn.com> wrote: > >> On Mon, 24 Dec 2012 12:13:42 -0700 >> Warner Losh <imp@bsdimp.com> wrote: >> >>> Or alternatively, you can look at the early startup state of the ue0 >>> device and look for subtle differences between it and other >>> interfaces. For a short period of time it may throw some weird >>> error that dhclient isn't coping with. >>> >> I am not sure but the above might be a red herring. My interface on my >> BEAGLEBONE is cpsw0 and has the exact same issue. >> >> -Brett > Greeting- > > Just changed my devd_enable to yes and all works as I expected with > DHCP. My rc.conf set up with Tim's script had it off, > but /etc/defaults/rc.conf had it on. > > Tim if you are on the list you might want to change that in the script. Or just switch to SYNCDHCP. No reason to run devd to do something that can be handled just as well without the extra process.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50D8E820.3050400>