snapcraft.yaml: correct image format and dtb installation path
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-snapdragon (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Impact:
The snapcraft.yaml that we are shipping in Xenial has two errors:
1) it defaults to the snapcraft's arm64 kernel target (Image.gz) while the correct one should be Image
2) it doesn't copy the dtbs from the SOC specific location to the dtbs root
The first one was my mistake while merging the new snapcraft.yaml from -generic with the one in the -snapdragon branch, the second is a consequence of the gadget snap dropping the dtb (and as such ubuntu-image looking for it in the kernel snap).
Fix:
Apply the attached patches to snapcraft.yaml and generate a new kernel snap
How to test it:
Generate a new snapdragon image[1] and boot it up.
1: https:/
--
CVE References
tags: | added: patch |
Changed in linux-snapdragon (Ubuntu): | |
status: | New → Fix Committed |
tags: |
added: verification-done-xenial removed: verification-needed-xenial |
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- xenial' to 'verification- done-xenial' . If the problem still exists, change the tag 'verification- needed- xenial' to 'verification- failed- xenial' .
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!