Use the 5.3 kernel for the raspi3 bionic 18.04.4 images
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
livecd-rootfs (Ubuntu) |
Invalid
|
Critical
|
Unassigned | ||
Bionic |
Fix Released
|
Critical
|
Łukasz Zemczak |
Bug Description
[Impact]
Currently our bionic images only support the pi2, pi3 and cm3 families of devices. For 18.04.4 we would also like to enable support for the pi4 (available in eoan+). For this to work, kernel support is required - this can be achieved by either backporting all the needed pi4 patches to the 4.15 kernel *or* using the 5.3 raspi one from focal that has already been tested and working. We decided that using 5.3 is the smartest and safest bet, so for this to work we need to use a different kernel flavour - linux-raspi2-5.3.
This requires a change in livecd-rootfs to pull in the new kernel flavour for our raspi3 images.
[Test Case]
Build a raspi3 classic bionic image via cdimage with -proposed enabled. Confirm that linux-raspi2-5.3 is used instead of linux-raspi2.
[Regression Potential]
None really. The only thing that could go wrong is that the raspi3 images would be using the wrong kernel - but that would fail verification then.
no longer affects: | ubuntu-image |
Changed in livecd-rootfs (Ubuntu): | |
importance: | Undecided → Critical |
Changed in livecd-rootfs (Ubuntu Bionic): | |
importance: | Undecided → Critical |
Changed in livecd-rootfs (Ubuntu): | |
status: | New → Invalid |
Changed in livecd-rootfs (Ubuntu Bionic): | |
status: | New → In Progress |
assignee: | nobody → Łukasz Zemczak (sil2100) |
tags: | added: block-proposed-bionic |
tags: | removed: block-proposed-bionic |
Uploaded to the Unapproved queue. Hopefully this upload is all that's needed.