[Bug 2078525] Re: [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi

Mon Sep 23 18:25:48 UTC 2024

Hello FaZe, or anyone else affected,

Accepted flash-kernel into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/flash-
kernel/3.104ubuntu21 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-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. 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: flash-kernel (Ubuntu Jammy)
       Status: Confirmed => Fix Committed

** Tags added: verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to flash-kernel in Ubuntu.
https://bugs.launchpad.net/bugs/2078525

Title:
  [SRU] zero-2-w.dtb does not exist in arm64 variant of linux-raspi

Status in flash-kernel package in Ubuntu:
  Fix Released
Status in flash-kernel source package in Jammy:
  Fix Committed
Status in flash-kernel source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  This is affecting upgraders from jammy to noble on the Raspberry Pi
  Zero 2W. Specifically, flash-kernel is failing to find the expected
  dtb once the noble version of flash-kernel is in place, causing it to
  fail. This terminates the apt operation, breaking do-release-upgrade.

  [ Test Plan ]

  To be repeated on all supported models of Pi:

  * Install the -proposed version of flash-kernel
  * Run "sudo flash-kernel" and ensure operation completes successfully
  * On the Zero 2W specifically, ensure the *-zero-2-w.dtb or *-zero-2.dtb is reported in the first few lines of output (on the release version it will, erroneously, be the *-4-b.dtb instead)

  At least in Pi Zero 2W:
  * Run do-release-upgrade from Jammy (with 5.15 -raspi kernel) to Noble
    (or remove `zero-2-w.dtb` to simulate that scenario) with -proposed
    enabled in APT sources and APT pinning configured for flash-kernel
    from noble-proposed to be used, and ensure it finishes successfully.

  [ Regression Potential ]

  Minimal; the change uses a well-tested mechanism within flash-kernel
  to probe for the correct dtb. Moreover, the change has already
  undergone testing on all supported boards during the jammy .5 ISO
  tests (while doing the server tests, I added my flash-kernel PPA and
  re-ran the flash-kernel test), the oracular beta ISO tests, and random
  noble testing in between.

  Theoretically, regressions would impact `Raspberry Pi Zero 2 W Rev *` machines
  (as identified in the flash-kernel database entry relevant to this change), 
  which might not get flash-kernel running correctly if something fails 
  (and again, impact do-release-upgrade in such machines as reported in this bug).

  [ Original Description ]

  package plymouth 24.004.60-1ubuntu7 failed to install/upgrade:
  installed plymouth package post-installation script subprocess
  returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: plymouth 24.004.60-1ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-1061.64-raspi 5.15.160
  Uname: Linux 5.15.0-1061-raspi aarch64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: arm64
  BootLog:

  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial:

  CloudSubPlatform: config-disk (/dev/mmcblk0p1)
  Date: Fri Aug 30 23:05:22 2024
  ErrorMessage: installed plymouth package post-installation script subprocess returned error exit status 1
  ImageMediaBuild: 20230807.2
  Lspci:

  Lspci-vt:

  Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t: /:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=dwc2/1p, 480M
  ProcCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:D7:09:57 vc_mem.mem_base=0x1fa00000 vc_mem.mem_size=0x20000000  console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash cfg80211.ieee80211_regdom=UA
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbdepth=16 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:D7:09:57 vc_mem.mem_base=0x1fa00000 vc_mem.mem_size=0x20000000  console=ttyS0,115200 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 rootwait fixrtc quiet splash cfg80211.ieee80211_regdom=UA
  Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.6ubuntu6.1
   apt  2.7.14build2
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Title: package plymouth 24.004.60-1ubuntu7 failed to install/upgrade: installed plymouth package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to noble on 2024-08-30 (0 days ago)
  acpidump:

  mtime.conffile..etc.init.d.apport: 2024-07-22T17:59:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2078525/+subscriptions