Snapcraft: 96boards fixes

Bug #1665650 reported by Paolo Pisati
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
Fix Released
Medium
Paolo Pisati

Bug Description

The 96boards example doesn't produce a kernel snap that boots on the Dragonboard410c, and these are the required changes to get a working kernel snap:

CONFIG_MMC*: to avoid hanging during boot when initrd can't find a valid /dev/disk... paritition

CONFIG_EXT4: this is self explanatory

CONFIG_BLK_DEV_LOOP: to avoid a "can't mount loop device: no space left on device" error on boot

And while here, unpack firmware.tar to /firmware.

Tested on my dragonbroard, generating a new image from scratch.

Revision history for this message
Sergio Schvezov (sergiusens) wrote :
Changed in snapcraft:
status: New → Fix Committed
importance: Undecided → Medium
assignee: nobody → Paolo Pisati (p-pisati)
milestone: none → 2.28
Changed in snapcraft:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.