Thanks Martin (a ton !!) On Wed, May 2, 2012 at 12:32 PM, Martin Langhoff <martin.langh...@gmail.com>wrote:
> On Wed, May 2, 2012 at 2:25 AM, Ajay Garg <ajaygargn...@gmail.com> wrote: > > I agree. But there is no working lower-level solution :\ > > Let's fix that. Great !!! > Messing with Sugar won't help you. > > Earlier in the thread someone pointed to you the scripts to trigger on > resume (by powerd). Do those work? Not work? What's the problem there? > The /etc/powerd/postresume.d/disable_mesh.sh doesn't work. My belief is that there is the same problem - race condition between the 'echo 0' script, and NetworkManager. This causes the NetworkManager to crash randomly. > > AIUI, if you > > - disable mesh on boot > Done. Added the 'echo 0' script in 'start()' method of NetworkManager, so that the effect takes place before NetworkManager starts up. Works like a charm. > - disable mesh on resume, from a powerd-triggered script > Does not work, as explained above. > - blacklist the MAC address so NM ignores it > > you win. Yes, every XO has a different MAC address, but you can read > that on first boot of the OS, and write the NM configuration. See the > olpc-configure script for examples. > Would be awesome. I believe this is the one and only complete solution possible :) Could you point me to the suitable (examples) link? I will be heartfully grateful. > > cheers, > > > > m > -- > martin.langh...@gmail.com > mar...@laptop.org -- Software Architect - OLPC > - ask interesting questions > - don't get distracted with shiny stuff - working code first > - http://wiki.laptop.org/go/User:Martinlanghoff > Regards, Ajay
_______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel