[Sugar-devel] Wanting to know a bit of (NetworkManager) workflow upon resume-from-suspend
ajay at activitycentral.com
Tue May 1 23:40:05 EDT 2012
I'll ask this straight ::
Is there an already tested-cum-recommended method, that could disable
mesh-network, both during reboots and resume-from-suspend?
Possible options (not tested by me) ::
A driver, encapsulating the patch at
(as per http://dev.laptop.org/pub/firmware/libertas/RELEASE_NOTES)
Query : How can I ascertain if this patch is present on a particular XO-1?
(For Reboot) ::
Add the bootstrap script 'echo 0 > "/sys/class/net/eth0/lbs_mesh"' in
(For Resume-Upon-Suspend) ::
Add the disable_mesh.sh script (at
Query : While the (For Reboot) case is guaranteed to work stably every
single time, can the same be said about (For Resume-Upon-Suspend) ?
c) Any other unknown in-the-dark hack.
On Tue, May 1, 2012 at 9:36 PM, Peter Robinson <pbrobinson at gmail.com> wrote:
> On Tue, May 1, 2012 at 3:55 PM, Ajay Garg <ajay at activitycentral.com>
> > which actually brings me back to my original question ::
> > """
> > Why is it so that putting the 'disable-mesh-script' in the 'start()'
> > of '/etc/init.d/Networkmanager' works (always) for (re)boot; but never
> > for resume-upon-suspend?
> > """
> Because on suspend/resume the NetworkManager service isn't
> started/restarted so the script in /etc/init.d isn't run where as on
> reboot it is. There's means though to run specific scripts on
> suspend/resume if that sort of thing is necessary.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Sugar-devel