Hi Paolo,

Thank you for your reply.

> On Thu, Feb 09, 2017 at 06:13:15AM +0000, Sunny Bhayani wrote:
> >
> > > the work is going on here:
> > >
> > > https://github.com/snapcore/snapcraft/pull/1115
> >
> > Is there a way, that we can come to know about an official fix, apart from 
> > the
> > above link that you mentioned.
> If you don't want to wait for a release, you can clone the snapcraft
> repository[1] and apply the above fix locally:
> git clone https://github.com/snapcore/snapcraft.git

We are able to apply your fix locally, and now we are getting the /lib/firmware
and /lib/modules with the required files.

We are able to make our Wifi work by doing insmod wcn36xx.ko, and doing the
echo start > /sys/kernel/debug/remoteproc/remoteproc2/state.

We have a question regarding the above step. In the Dragonboard prebuilt rootfs,
there are scripts which actually inserts the Wifi module during boot. Those
scripts are located at /lib/systemd/system/wcnss-start.service.

These scripts actually start the wifi interface.

But in our case, we have to manually do this. So how can we add new scripts to
the RootFS in our case as compared to the prebuilt Dragonboard binary ?

One more observation is, that due to the above scripts present in the prebuilt
Dragonboard binary, during the first boot console config, we get to configure
the wifi interface along with the eth0 interface, which is also missing in our

> > Also, how did the build for the Dragonboard410C succeed for the pre-built
> > Ubuntu Core OS image ?
> >
> > Since that is working properly, /lib/modules have the kernel modules and
> > /lib/firmware has the firmware binaries.
> >
> > Also, the wifi interface (wlan0) is working.
> >
> > Sorry, but I was just curious to know this.
> The kernel snaps for the dragonboard (and the raspberry and pc), are generated
> from the deb packages in our archive, using this script:
> https://code.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-snap/+git/xenial
> Starting from the snapdragon branch, the snapcraft.yaml there invokes the
> Makefile in the master branch.
> This was done to use the x86 signed kernels (required for trusted boot), and 
> the same mechanism
> was reused for arm.
> But for development, snapcratf and the kernel plugin are the way to go.
> 1: https://github.com/snapcore/snapcraft

So we understand the snapcraft and kernel plugin should be used for development.
But by applying the patches (fix) that you gave, we still are not able to do
"snap list" and "snap install hello-world".

It would be really great if you can help for both the RootFS (scripts) and the
snap list / install issues.


 eInfochips Business Disclaimer: This e-mail message and all attachments 
transmitted with it are intended solely for the use of the addressee and may 
contain legally privileged and confidential information. If the reader of this 
message is not the intended recipient, or an employee or agent responsible for 
delivering this message to the intended recipient, you are hereby notified that 
any dissemination, distribution, copying, or other use of this message or its 
attachments is strictly prohibited. If you have received this message in error, 
please notify the sender immediately by replying to this message and please 
delete it from your computer. Any views expressed in this message are those of 
the individual sender unless otherwise stated. Company has taken enough 
precautions to prevent the spread of viruses. However the company accepts no 
liability for any damage caused by any virus transmitted by this email. 
Snapcraft mailing list
Modify settings or unsubscribe at: 

Reply via email to