>> Update to newer builds. They contain some udev magic to start things
>> automatically (for open networks anyway).
I wonder if there isn't another timing/race issue lurking here.
After boot, if WiFi is up and connected to an AP (or ad-hoc net), I issue:
iwconfig wlan0 essid "1234" mode ad-hoc
I will often times find no essid upon subsequent "iwconfig" commands.
If I issue the "iwconfig wlan0 essid "1234" mode ad-hoc" a second time,
it works, and the overo joins the ad-hoc network.
It seems pretty consistent that it takes two calls to iwconfig to get the
part in the right state.
I'm running the 200907261233 image
View this message in context: http://www.nabble.com/bitbake-errors-tp23753929p24900405.html
Sent from the Gumstix mailing list archive at Nabble.com.