[Bug 2149913] Re: [SRU] Broken symbolic link to ../cypress/cyfmac43439-sdio.txt.zst

[Dave Jones]

** Also affects: linux-firmware-raspi (Ubuntu Resolute)
   Importance: Undecided
       Status: New

** Changed in: linux-firmware-raspi (Ubuntu Resolute)
       Status: New => Triaged

** Changed in: linux-firmware-raspi (Ubuntu Resolute)
   Importance: Undecided => High

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

** Changed in: linux-firmware-raspi (Ubuntu)
    Milestone: resolute-updates => None

** Changed in: linux-firmware-raspi (Ubuntu Resolute)
    Milestone: None => resolute-updates

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

Title:
  [SRU] Broken symbolic link to ../cypress/cyfmac43439-sdio.txt.zst

Status in linux-firmware-raspi package in Ubuntu:
  Triaged
Status in linux-firmware-raspi source package in Resolute:
  Triaged

Bug description:
  [ Impact ]

  The missing file contains configuration information for the WiFi chip
  used on certain versions of the Pi Zero 2W

  [ Test plan ]

  Given the Pi Zero 2W wifi is still capable of working without the
  specific .txt file (albeit less reliably) there's not much point
  testing that directly. Better to simply check that the symlink is no
  longer dead:

  * Flash a Ubuntu for Raspberry Pi to SD card
  * Boot it
  * file /usr/lib/firmware/brcm/brcmfmac43439-sdio.txt.zst
  * Observe symlink is broken
  * Enable proposed
  * sudo apt install -t resolute-proposed linux-firmware-raspi
  * file /usr/lib/firmware/brcm/brcmfmac43439-sdio.txt.zst
  * Check symlink is no longer reported as broken

  * Boot SD card on a Pi Zero 2W with the affected chipset
  * Configure wifi in /etc/netplan/50-cloud-init.yaml
  * sudo netplan apply
  * ping launchpad.net
  * Ensure wifi is still operational

  [ Where things can go wrong ]

  Obviously, messing with the firmware package carries the risk of
  breaking anything affected by that firmware.

  In this case, the change is to add a firmware configuration file for a
  wifi device only deployed on certain variants of the Pi Zero 2W, so we
  can limit hardware testing to that specific model. The major risk is
  breaking wifi functionality (the only network interface on this
  model), so the test plan covers ensuring that wifi can still come up
  and function with a simple ping command.

  [ Original description ]

  ubuntu at rpi-5b-8gb-rev1d0-f88b:~$ file /usr/lib/firmware/brcm/brcmfmac43439-sdio.txt.zst
  /usr/lib/firmware/brcm/brcmfmac43439-sdio.txt.zst: broken symbolic link to ../cypress/cyfmac43439-sdio.txt.zst

  ubuntu at rpi-5b-8gb-rev1d0-f88b:~$ ls -la /usr/lib/firmware/brcm/brcmfmac43439-sdio.txt.zst
  lrwxrwxrwx 1 root root 35 Mar 18 20:10 /usr/lib/firmware/brcm/brcmfmac43439-sdio.txt.zst -> ../cypress/cyfmac43439-sdio.txt.zst

  ubuntu at rpi-5b-8gb-rev1d0-f88b:~$ apt-cache policy linux-firmware-raspi
  linux-firmware-raspi:
    Installed: 14-0ubuntu1
    Candidate: 14-0ubuntu1
    Version table:
   *** 14-0ubuntu1 500
          500 http://ports.ubuntu.com/ubuntu-ports resolute/restricted arm64 Packages
          100 /var/lib/dpkg/status

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