[Sugar-devel] Wanting to know a bit of (NetworkManager) workflow upon resume-from-suspend

[Ajay Garg]

Thanks Martin and Jerry.

I followed the following steps ::

a)
Listed "lsinitrd /boot/initrd.img".
It did not show any "/etc/modprobe.d/libertas.conf".


b)
Extracted "/boot/initrd.img" into a temporary folder.
Obviously, no "/etc/modprobe.d/libertas.conf" was seen.


c)
Generated the required "/etc/modprobe.d/libertas.conf" with the content
"options libertas libertas_disablemesh=1" in the tmp folder.


d)
Re-compressed the temp-folder to "/boot/initrd.img".


e)
Listed "lsinitrd /boot/initrd.img".
This time, "/etc/modprobe.d/libertas.conf" was listed.


f)
Rebooted XO-1.


g)
Mesh-icons were still observed :(


h)
Note that I did this, without OOB (i.e. I was just wanting to test that
whether this would work at all).


I guess that there is something else we might be missing.


So, I think that the only solution left now, is to put the "rmmod/modprobe"
hack in olpc-configure.

Would it be an acceptable upstream solution (the change in olpc-utils) ?
Martin (Langhoff) / Daniel (Drake) ?



Looking forward to comments and replies.


Thanks and Regards,
Ajay

On Sun, May 13, 2012 at 3:10 AM, Jerry Vonau <jvonau at shaw.ca> wrote:

> On Sat, 2012-05-12 at 15:20 -0400, Martin Langhoff wrote:
> > On Sat, May 12, 2012 at 4:38 AM, Ajay Garg <ajay at activitycentral.com>
> wrote:
> > > I tried the "rmmod/modprobe" hack in "olpc-configure", and it worked
> > > (obviously because, this time the "/etc.modprobe.d/libertas.conf"
> could be
> > > fetched/read from persistent storage). Mesh-icons were no more visible
> in
> > > the neighborhood-view (both during reboot, and resume-from-suspend).
> > >
> > > But I too felt that this is more of a hack, and not a clean solution.
> >
> > Well, as you pointed out in later emails, the initramfs generation
> > will pick it up from there. I'd forgotten about that -- sorry.
> >
> > So what you want to do is get libertas.conf into some package
> > (olpc-utils) or install it from an OOB module -- the xo1 module is a
> > good candidate.
> >
> > In fact I'm liking the OOB module option. I think we would accept a
> > patch to OOB's xo1 module, where based on an option it creates this
> > file. Just have to make sure it's created before dracut is used to
> > generate the initramfs.
> >
>
> Hi Martin:
>
> Don't think OOB is used to generate the initramfs, from the kernel spec
> file:
>
> # set to 1 to build the initramfs during kernel-build time
> # set to 0 to build the initramfs during %post on the host
> %define buildinitramfs 1
>
> Doesn't that mean the kernel rpm provides pre-build initrd<version>.img
> and actrd<version>.img? Doesn't OOB just sign what is in the kernel rpm?
>
> Think you would need to re-create initrd.img as needed then place the
> revised initrd.img into the image via OOB, to be signed by OOB.
>
> Jerry
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20120513/f16b0aa8/attachment.html>