John Dowd <jdowds...@gmail.com> writes: > I can now manually configure the wireless interface but I need to come up > automatically during boot and start the dhcp client. I can see that the > kernel > does boot and somewhere during init the interface is brought up. However, > somewhere later during the init the wireless interface is being > shutdown.
You certainly want to consult http://wiki.openmoko.org/wiki/FSO_Resources wikipage; it's frameworkd syncing resources on startup and thus turning everything off. > If I go into the Setup application I can see that the wireless > option is turned off. If I turn it back on it then the interface > does come up. However, it is not persistent across boots. How do I > turn off the current system setting of turning off the wireless > interface? I have a "wlan" script in the "/etc/init.d" directory and > once I manually bring up the wireless interface I can run it and it > does configure the interface properly. Start your script after frameworkd and use fsoraw accordingly. > Also, I'm running into the same problem with the busybox udhcpc application > that I've seen before. It does not see the DCHPOFFER from the AP. It ignores > it and continues to issue the DCHPDISCOVER. There was a application dhclient > that ran on the OM2009 distro. Is there anything available here on the > unstable SHR? If dhclient is not in the feeds, i'm sure one of SHR folks (dos1, you ;) ) can add it. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com _______________________________________________ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community