Comment 11 for bug 1691729

The workaround (in Comment #4) is not working for me. I'm running on a Raspberry Pi 3 Model B. I've been working on this for several days and trying different variations in the order I do things (rebooting or not after upgrade, etc.), and eventually I always end up with a SD image that will not boot. Which makes sense, I guess, since this involves a firmware image.

Here's what I get when I try the workaround:

  ubuntu@ubuntu:~$ sudo dpkg-divert --divert /lib/firmware/brcm/brcmfmac43430-sdio-2.bin --package linux-firmware-raspi2 --rename --add /lib/firmware/brcm/brcmfmac43430-sdio.bin
  sudo: unable to resolve host ubuntu
  Adding 'diversion of /lib/firmware/brcm/brcmfmac43430-sdio.bin to /lib/firmware/brcm/brcmfmac43430-sdio-2.bin by linux-firmware-raspi2'
  Ignoring request to rename file '/lib/firmware/brcm/brcmfmac43430-sdio.bin' owned by diverting package 'linux-firmware-raspi2'

Things still work OK at that point, and I can reboot. But the very next time I run 'sudo apt-get upgrade' the process runs a long time (updating all kinds of things that were not being upgraded before I typed in the workaround), and when it is finally done, the Pi will no longer boot up after a reboot.

I'm guessing that the reason it fails for me is that "Ignoring request to rename file" message (which I've not seen anyone else mention). But I have no idea what to do about it.