From: dtran11 <dt...@gm...> - 2011-10-12 17:25:47
|
I am seeing the same behavior. did you manage to fix this problem? I am using kernel 3.0-pm. I noticed that if you do a "iwlist wlan0 scan" first then it will work right after. Uriah Baalke wrote: > > I get this error for about the first 300 seconds after boot of my gumstix > overo fire: > > 30.890228] libertas: assoc: bss (null) not in scan results > > Does anyone know the wireless driver is not initializing during / right > after boot? > > -- > Uriah Baalke > Mechanical Engineering > University of Pennsylvania Class of 2011 > Cell: 267.253.1581 > Email: ur...@gm... > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/Libertas-driver-issues-tp31976308p32639991.html Sent from the Gumstix mailing list archive at Nabble.com. |