Re: [Dragonboard410c] Ubuntu OS Build Issues, and Support

2017-03-20 Thread Oliver Grawert
hi, Am Montag, den 20.03.2017, 06:04 + schrieb Sunny Bhayani: > Hi Oliver, > > Thank you for your reply. > > > hi, > > the image has not properly being initialized ... else you would > only > > get the reboot notifications after the first upgrade of the core > snap > > (i.e. your root

Re: [Dragonboard410c] Ubuntu OS Build Issues, and Support

2017-03-16 Thread John Lenton
Hi Sunny, I don't understand what's going on with your system: * snapd is running out of memory. snapd should be using about 20MB of resident memory. How much was it trying to use when it ran out? How much is available? What does dmesg say about this crash? * snapd on a core system that doesn't

Re: [Dragonboard410c] Ubuntu OS Build Issues, and Support

2017-03-07 Thread John Lenton
note that in that log, snapd isn't running because snapd[2217]: fatal error: runtime: out of memory On 22 February 2017 at 07:52, Sunny Bhayani wrote: > Hi Ogra, > > Appreciate for your help. > >> hi, >> Am Freitag, den 17.02.2017, 10:06 + schrieb Sunny

Re: [Dragonboard410c] Ubuntu OS Build Issues, and Support

2017-03-06 Thread Paolo Pisati
Here is the Xenial kernel src tree, checkout the snapdragon branch: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/ it already contains a snapcraft.yaml so you can generate a working kernel snap (though the firmware files are missing here). On Sat, Mar 4, 2017 at

Re: [Dragonboard410c] Ubuntu OS Build Issues, and Support

2017-02-22 Thread Paolo Pisati
On Wed, Feb 22, 2017 at 10:19:25AM +0100, Oliver Grawert wrote: > > The AppArmor patches that we ported from the  > > http://kernel.ubuntu.com/git/ppisati/ubuntu-vivid.git/tree/arch/arm/c > > onfigs/snappy?h=snappy_v3.10 > > > > are for the linux kernel 3.10. > > > > But the kernel that we are

Re: [Dragonboard410c] Ubuntu OS Build Issues, and Support

2017-02-22 Thread Oliver Grawert
hi, Am Mittwoch, den 22.02.2017, 07:52 + schrieb Sunny Bhayani: >  > > >  > > > Also, we went through the kernel-initrd-modules description: > > > https://snapcraft.io/docs/reference/plugins/kernel > > >  > > > and there it is mentioned that the "kernel-initrd-modules" plugin > is > > > used

Re: [Dragonboard410c] Ubuntu OS Build Issues, and Support

2017-02-17 Thread Oliver Grawert
hi, Am Freitag, den 17.02.2017, 10:06 + schrieb Sunny Bhayani: >  > > You are correct that in the prebuilt image (Ubuntu OS) for > Dragonboard, the Wifi  > module is auto-loaded during boot. But in our case, this does not > happen. > > So can you please let us know, that in what part

Re: [Dragonboard410c] Ubuntu OS Build Issues, and Support

2017-02-16 Thread Oliver Grawert
hi, Am Donnerstag, den 16.02.2017, 10:16 + schrieb Sunny Bhayani: >  > 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

Re: [Dragonboard410c] Ubuntu OS Build Issues, and Support

2017-02-09 Thread Paolo Pisati
On Thu, Feb 09, 2017 at 06:13:15AM +, 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

Re: [Dragonboard410c] Ubuntu OS Build Issues, and Support

2017-02-08 Thread Oliver Grawert
hi, Am Mittwoch, den 08.02.2017, 15:40 +0100 schrieb Paolo Pisati: > On Wed, Feb 08, 2017 at 01:07:34PM +0100, Oliver Grawert wrote: > > > > > > yes, i belive the snapcraft team together with the kernel team are > > working on a fix for this [1], the snapcraft kernel plugin seems to > > put > >

Re: [Dragonboard410c] Ubuntu OS Build Issues, and Support

2017-02-08 Thread Paolo Pisati
On Wed, Feb 08, 2017 at 01:07:34PM +0100, Oliver Grawert wrote: > > yes, i belive the snapcraft team together with the kernel team are > working on a fix for this [1], the snapcraft kernel plugin seems to put > the modules and firmware in a /lib subdir in the snap package which is > wrong [2] and