[Bug 1805668] Re: Building armhf and arm64 Raspberry Pi 3 images
Adam Smith
1805668 at bugs.launchpad.net
Fri Dec 21 09:17:19 UTC 2018
For completeness I'll point out some problems with flash-kernel.... The
3B+ is not supported (bug 1764491), nor is the CM3 or new 3A+. Whenever
a new revision of a board comes out it breaks.
The unforgiveable thing though is that the pi3 bootscript doesn't work (bug 1791466). This clearly has never been tested by those making the changes to the package. Ubuntu core doesn't use a bootscript with the pi3 which presumably is why this has never been picked up. The beta arm64 classic image contains a uboot.env (like ubuntu core), but this doesn't match what flash-kernel currently does for the pi3.
Finally, flash-kernel doesn't handle overlays which is a pretty big thing on the pi. For example, by default Ubuntu-core currently uses the vc4-fkms overlay.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to u-boot in Ubuntu.
https://bugs.launchpad.net/bugs/1805668
Title:
Building armhf and arm64 Raspberry Pi 3 images
Status in livecd-rootfs package in Ubuntu:
Fix Released
Status in raspi3-firmware package in Ubuntu:
Fix Released
Status in u-boot package in Ubuntu:
Fix Released
Status in livecd-rootfs source package in Bionic:
Fix Committed
Status in raspi3-firmware source package in Bionic:
Confirmed
Status in u-boot source package in Bionic:
Confirmed
Status in livecd-rootfs source package in Cosmic:
Won't Fix
Status in raspi3-firmware source package in Cosmic:
Confirmed
Status in u-boot source package in Cosmic:
Confirmed
Bug description:
[Impact]
One of our long-term goals is to support the same set of platforms for both classical Ubuntu and ubuntu-core. We currently provide official images for the Raspberry Pi 3 for both the core16 and core18 bases but do not provide the same for Ubuntu classic.
Since it's a 'feature' we're essentially lacking since long, we want to have the new device also supported in our current LTS (bionic).
[Fix]
For the classic raspi3 support we will be using the ubuntu-image classic image building tool which is specifically designed for creating preinstalled images. The support for that has already been SRUed in the latest ubuntu-image.
For the full image build support to be complete, the following list of changes need to be backported (SRUed) into the respective stable series:
* livecd-rootfs - all the changes regarding classic image build, gadget tree selection and raspi3 rootfs generation.
* u-boot - bionic will need to be updated to at least 2018.03+dfsg1-2ubuntu2.
* raspi3-firmware (bionic only) - needs to be updated to at least the version we have in cosmic. Without this change, the console is flooded with firmware error messages every 2 seconds.
(vorlon) this should be updated specifically to the version of raspi3-firmware that we are using in the gadget snap - currently 1.20180919 - and not to another.
[Test Case]
* Run a bionic livefs build of raspi3+armhf with proposed enabled (IMAGEFORMAT=ubuntu-image and PROJECT=ubuntu-cpc), make sure the build succeeds and that the resulting image boots on a raspi3.
* Run a bionic livefs build of raspi3+arm64 with proposed enabled (IMAGEFORMAT=ubuntu-image and PROJECT=ubuntu-cpc), make sure the build succeeds and that the resulting image boots on a raspi3.
* Make sure that none of the other bionic daily images fail to build
[Regression Potential]
There is some potential that an invalid backport of livecd-rootfs
functionality could result in the inability to create new ubuntu-core
images or any of the other existing flavors. But in case of such a
regression we would see it instantly after the package lands in
bionic-proposed as we are building daily images with -proposed
enabled. As for the other packages, there probably is some regression
potential, but since the versions are backports from disco/cosmic, the
risk is probably very small.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1805668/+subscriptions
More information about the foundations-bugs
mailing list