Hi everyone. I solved the "why won't the ESSID" connect due to "user error". One of the letters in our ESSID was capitalized... hah.
Actually I do have one other incredibly frustrating problem. The following works as defined by "the blue wifi LED stays on":iwconfig wlan0 essid anyBut half the time it picks the wrong network. I can't force it to pick our network for the life of meiwconfig wlan0 essid myhomenetnever works. Flashes the blue LED but then it ends up staying off.When the first command randomly picks our network, everything works fine (until it auto-powers off). But it is really frustrating if it picks the wrong network, it's like there is nothing i can do to get it to work correctly(by the way I'm using the wiki wifi tutorial, disabled bluetooth, uninstalled the network manager.Linux overo 2.6.34 #1 Wed Oct 20 10:22:48 PDT 2010 armv7l GNU/LinuxBlaine
On Mon, Dec 12, 2011 at 5:15 PM, Blaine <email@example.com> wrote:Hi everyone. I'll keep it quick. Unlike most overo issues, when my wifi is working it works fine (I think). I can ping google and for now that's all that matters.I can see the little blue LED on my board. When I connect to an access point successfully, it flashes and then stays on. After 2-3 minutes it turns off, and I have no network connectivity even though it think I do (with iwconfig, etc.). No dmesg statement, nothin'. I have to bring it down, bring it back up, and do the "iwconfig wlan0 essid on" to get it back up. Light comes back on and I'm good to go.If I hold a ping command like "ping google.com" there are no problems and it will stay on continuously until 2-3 minutes after stopping the ping.
I remember that the LCD display has a power saving mode that we never figured out how to disable. Is this related? All I want is stable wifi that doesn't turn off. I can't figure out what is causing this behavior. Suggestions are greatly appreciated.Blaine