[Bug 1989713] Re: [SRU] CM4 NVMe boot fails due to old start4.elf / fixup4.dat

[Dave Jones]

** Changed in: linux-firmware-raspi (Ubuntu Jammy)
     Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: linux-firmware-raspi (Ubuntu Kinetic)
     Assignee: (unassigned) => Dave Jones (waveform)

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

Title:
  [SRU] CM4 NVMe boot fails due to old start4.elf / fixup4.dat

Status in linux-firmware-raspi package in Ubuntu:
  Confirmed
Status in linux-firmware-raspi2 package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in linux-firmware-raspi source package in Jammy:
  Confirmed
Status in linux-firmware-raspi2 source package in Jammy:
  Invalid
Status in linux-raspi source package in Jammy:
  Invalid
Status in linux-firmware-raspi source package in Kinetic:
  Confirmed
Status in linux-firmware-raspi2 source package in Kinetic:
  Invalid
Status in linux-raspi source package in Kinetic:
  Invalid
Status in linux-firmware-raspi source package in Lunar:
  Confirmed
Status in linux-firmware-raspi2 source package in Lunar:
  Invalid
Status in linux-raspi source package in Lunar:
  Invalid

Bug description:
  [ Impact ]

  CM4 users wishing to boot directly from NVMe find the initramfs is
  reported as corrupted. This is due to a bug in the boot firmware
  reported upstream as:

  https://github.com/raspberrypi/firmware/issues/1731
  https://github.com/raspberrypi/firmware/issues/1746

  These issues were fixed upstream but Ubuntu now needs an updated
  linux-firmware-raspi package incorporating the fixed boot firmware
  (and ideally this should land prior to 22.04.2 to ensure the updated
  firmware can go into the images for that release).

  [ Test Plan ]

  * sudo add-apt-repository ppa:waveform/firmware

  * sudo apt install linux-firmware-raspi

  * sudo reboot

  * Verify that the system boots successfully

  * Run through the full battery of ISO tests for the relevant image.
  Specifically, Ubuntu Desktop arm64+raspi, Ubuntu Server arm64+raspi,
  and Ubuntu Server armhf+raspi under:

    - Kinetic dailies:
  http://iso.qa.ubuntu.com/qatracker/milestones/433/builds

    - Jammy dailies:
  http://iso.qa.ubuntu.com/qatracker/milestones/429/builds

  [ Regression Potential ]

  The updated package replaces the tertiary boot firmware. An obvious
  regression potential is therefore that one or more Pi models fail to
  boot. However, in addition we've encountered other issues which
  ultimately boiled down to boot firmware in the past (the boot firmware
  is also responsible for patching the device-tree). Hence the test plan
  needs to be comprehensive and should be tested on as many models of Pi
  as is reasonably possible.

  Several kind users have already tested the back-ported firmware on the
  CM4 with NVMe boot (see comments 7 and 8), and I've tested on Pi 3 and
  4 models under armhf and arm64 kernels, hence I'm quietly confident
  but I haven't run the full gamut of ISO tests yet. Still, SRU
  verification should include all supported models, and ISO tests to
  guard against regressions due to interactions with differing kernel
  versions on the SRU'd releases.

  [ Original Description ]

  Hi there,

  there is the issue connected with "Initramfs unpacking failed:
  Decoding failed" error during Ubuntu boot. See
  https://github.com/raspberrypi/firmware/issues/1746 and
  https://github.com/raspberrypi/firmware/issues/1731. The Raspberry Pi
  have the update for start4.elf / fixup4.dat with fix it. Could you
  please include update for these files in new ubuntu release ASAP?

  Thanks in advance!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi/+bug/1989713/+subscriptions