[Dragonboard410c] Ubuntu OS Build Issues, and Support

Tue Mar 7 11:05:36 UTC 2017

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
<sunny.bhayani at einfochips.com> wrote:
> Hi Ogra,
>
> Appreciate for your help.
>
>> hi,
>> Am Freitag, den 17.02.2017, 10:06 +0000 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 (plugin) of the
>> > snapcraft.yaml
>> > do we need to mention the kernel modules that needs to be auto-loaded
>> > during the
>> > kernel boot.
>> >
>> > We tried to add the kernel module in the snapcraft.yaml as below:
>> >
>> >   kernel-initrd-modules:
>> >              - squashfs
>> >              - wcn36xx
>>
>> this would just pull the module into the initrd which would be useless,
>> since we do not ship any userspace bits for WIFI support in there.
>> if you can modprobe it it is obviously already in the right place in
>> your /lib/modules dir on the booted system, so first of all remove it
>> from the list above. having it already loaded from the initrd on boot
>> might make it miss the right initialization since it wont find all the
>> userspace bits that it needs in the initrd.
>>
>> also make sure you have the firmware in the right place on the booted
>> rootfs, this is how it looks like on the official dragoboard image:
>>
>> http://paste.ubuntu.com/24012991/
>>
> Yes, we have the /lib/modules and /lib/firmware populated as you have
> mentioned
> above.
>
>> >
>> > 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 to
>> > mention the modules required to mount the rootfs.
>>
>> this means filesystem or disk controller modules (squashfs, ext4 (if
>> you do not compile it in), mmc support and the like), since your system
>> boots to a rootfs already you should not need anything more than you
>> currently have.
>>
>> > >
> Yes, agreed as you have mentioned above for the "kernel-initrd-modules".
>
>> >
>> > It would be great if you can please help us out on this front as well
>> > for the
>> > snap list / snap install for the Ubuntu OS.
>>
>> this definitely means that snapd did not start for some reason, like i
>> mentioned before this could be caused by the firstboot initialization
>> of the board having failed or by some missing feature that snapd
>> expects from your kernel.
>>
>> does sudo journalctl -u snapd.service reveal anything ?
>> do you find anything interesting in syslog in general ?
>>
> We are seeing error related to AppArmor patches in journalctl log.
> The log is at: http://pastebin.com/vG9DQfTf
>
>> >
>> >
>> > Yes. We are using a USB to Ethernet module on dragonboard to use the
>> > Ethernet.
>> >
>> did you check if  the behaviour of the WLAN device changes when booting
>> without the USB dongle attached ?
>>
> This we have not checked. Will update for this.
>
>> > While using the prebuilt image for Dragonboard, we are able to
>> > configure the
>> > access point for Wifi interface in the first boot screen, but then
>> > while doing
>> > ssh to the board, it is asking for password (during first boot). How
>> > can we
>> > resolve this ?
>> >
>>
>> did console-conf (the first boot configuration UI) actually finish the
>> user creation properly (did it tell you about it and give you info
>> about how to ssh into the board) without any errors ?
>>
>> /var/log/console-conf/subiquity-debug.log might be informative here.
>>
> The subiquity-debug.log is at: http://pastebin.com/39zsb4nE
>
> The AppArmor patches that we ported from the
> http://kernel.ubuntu.com/git/ppisati/ubuntu-vivid.git/tree/arch/arm/configs/snappy?h=snappy_v3.10
>
> are for the linux kernel 3.10.
>
> But the kernel that we are referring to is from 96boards - linux kernel 4.4.
>
> Moreover, the prebuilt image is also built for linux kernel 4.4.
>
> So do you have a kernel source for AppArmor patches which are ported on
> linux
> kernel 4.4 like the prebuilt Ubuntu Core Image for Dragonboard410c.
>
> Please provide the patchset link for the latest kernel.
>
> Awaiting your reply.
>
> Thanks,
> Sunny
>
> *************************************************************************************************************************************************************
> 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
> Snapcraft at lists.snapcraft.io
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/snapcraft
>