[Bug 2065051] Re: [SRU] Migrate Pi users to KMS

[Timo Aaltonen]

Hello Dave, or anyone else affected,

Accepted ubuntu-release-upgrader into noble-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:24.04.18
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubuntu-release-upgrader (Ubuntu Noble)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-noble

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2065051

Title:
  [SRU] Migrate Pi users to KMS

Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Committed
Status in ubuntu-release-upgrader source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  In switching Pi Server users over to the KMS overlay (as resolution to
  LP: #2038924) we need an additional quirk for upgraders to migrate
  config.txt (this will be similar, but not identical, to the one for
  LP: #1923673).

  If we do not migrate such users, the immediate impact is that Pi 5
  users will have no sound output on server images (the Pi 5 only has
  HDMI audio output, no auxiliary jack). Potentially more problematic in
  the long-run, though, is that we will wind up with users on different
  graphical stacks (the KMS stack, which is the only upstream supported
  stack going forward, and the legacy framebuffer method).

  [ Test Case ]

  * Flash Ubuntu jammy to SD card and boot on Pi 4
  * Check /boot/firmware/config.txt does not contain dtoverlay=vc4-kms-v3d (it should not on Pi server images)
  * sudo do-release-upgrade
  * Proceed through upgrade and reboot
  * Ensure system reboots successfully
  * After reboot, check /boot/firmware/config.txt contains dtoverlay=vc4-kms-v3d
  * Shutdown, move SD card to Pi 5 and boot it
  * Check /proc/asound/cards contains entries for vc4hdmi

  [ Regression Potential ]

  The use of the KMS overlay itself is not concerning; we already use it
  on the Pi desktop images, and have for several cycles now with no
  serious issues, so the regression potential there is minimal.

  However, the quirk does manipulate the bootloader's config.txt on the
  boot partition, which always carries the potential of leaving a system
  unbootable. To guard against this, tests are included with the quirk
  which check for several scenarios including a config.txt which has
  already been migrated to the KMS overlay manually by the user (there
  are various reasons to do this, including running kmscon), as well as
  the typical expected case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2065051/+subscriptions