linux-firmware fails to upgrade to 20220314.gitcd01f857-0ubuntu1

[NetBit73]

linux-firmware fails to upgrade with:

unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory

$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  linux-firmware
1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
Need to get 0 B/238 MB of archives.
After this operation, 24.9 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 272091 files and directories currently installed.)
Preparing to unpack .../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ...
Unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1) ...
dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack):
 unable to open '/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or directory
No apport report written because the error message indicates an issue on the local system
update-initramfs: Generating /boot/initrd.img-5.15.0-23-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgubuntu-swap_1)
I: Set the RESUME variable to override this.
update-initramfs: Generating /boot/initrd.img-5.15.0-22-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgubuntu-swap_1)
I: Set the RESUME variable to override this.
Errors were encountered while processing:
 /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

[Paul White (paulw2u)]

Unable to upgrade package:
20220302.gitee0667aa-0ubuntu1 => 20220314.gitcd01f857-0ubuntu1

[bsdz (blairuk)]

A potential (temporary) workaround is to remove the offending symlinks from package file as follows:

mkdir linux-firmware
cd linux-firmware
cp /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ./
ar xf linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb
zstd -d data.tar.zst
tar vf data.tar --delete ./lib/firmware/ath11k/WCN6855/hw2.1/
zstd -f data.tar
ar rcs linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb debian-binary control.tar.zst data.tar.zst
sudo dpkg -i linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb

One can then create the hw2.1 symlinks manually.

[Allan (allan-null)]

What I did to workaround the problem on my system is:

rm /lib/firmware/ath11k/WCN6855/hw2.1
cp -R lib/firmware/ath11k/WCN6855/hw2.0 /lib/firmware/ath11k/WCN6855/hw2.1

And then I tried to upgrade the packages again, which I did successfully.
I don't actually need those drivers, but I think that would be an okay workaround for those who need it.

[Erich Eickmeyer (eeickmeyer)]

Allan, bsdz: thanks for the workaround(s). However, workarounds don't get to the heart of fixing the problem, which is what bug reports are intended to do. Rest assured, the people that need to fix this are working on it, hence the triage and assignment, and I would expect this to be fixed very soon.

For those that would want to use this workaround, that would be done at their own risk, and those workarounds could be undone and unnecessitated by package updates. My best advice, especially if you're running Jammy, is to just wait it out and it will get fixed. These types of problems don't go unnoticed, and certainly don't stick around for long. :)

[Heinrich Schuchardt (xypron)]

A different file was reported for me:

Unpacking linux-firmware (20220314.gitcd01f857-0ubuntu1) over (20220302.gitee0667aa-0ubuntu1) ...
dpkg: error processing archive /var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb (--unpack):
 unable to install new version of '/lib/firmware/ath11k/WCN6855/hw2.1/amss.bin': No such file or directory
No apport report written because the error message indicates an issue on the local system

$ ls /lib/firmware/ath11k/WCN6855/ -la
total 12
drwxr-xr-x 3 root root 4096 Feb 18 17:28 .
drwxr-xr-x 6 root root 4096 Jan 11 13:31 ..
drwxr-xr-x 3 root root 4096 Mar 15 08:58 hw2.0
lrwxrwxrwx 1 root root 5 Feb 17 08:51 hw2.1 -> hw2.0

The problem could be resolved locally via
sudo rm /lib/firmware/ath11k/WCN6855 -rf

After upgrading the symbolic link is gone:

$ ls /lib/firmware/ath11k/WCN6855 -la
total 16
drwxr-xr-x 4 root root 4096 Mar 15 09:00 .
drwxr-xr-x 6 root root 4096 Mar 15 09:00 ..
drwxr-xr-x 2 root root 4096 Mar 15 09:00 hw2.0
drwxr-xr-x 2 root root 4096 Mar 15 09:00 hw2.1

[Juerg Haefliger (juergh)]

Fixed package available in jammy-proposed: 20220314.gitcd01f857-0ubuntu2.

[NetBit73 (mmach)]

It works for me.

[Achim Behrens (k1l)]

tried the fix from the new package manually (removing /lib/firmware/ath11k/WCN6855/hw2.1) and after that the update worked.

[Luis Alberto Pabón (copong)]

I can confirm "20220314.gitcd01f857-0ubuntu2" from proposed fixes the problem for me.

[Jonathan Kamens (jik)]

Works for me as well.
(Does Ubuntu have some sort of karma system similar to Fedora's, i.e., is there another web site somewhere we should be going to to indicate that the fix works for us?)

[bernstein (bernstein)]

thanks Allan! For me a simple :

  rm /lib/firmware/ath11k/WCN6855/hw2.1

is all that was needed before restarting the update process.

The result is that before the failed upgrade it looked like this :

  lrwxrwxrwx 1 root root 5 Feb 17 08:51 hw2.1 -> hw2.0

and after the successful upgrade it now looks like this :

  drwxr-xr-x 2 root root 6 Mär 15 15:34 .
  lrwxrwxrwx 1 root root 17 Mär 14 11:40 amss.bin -> ../hw2.0/amss.bin
  lrwxrwxrwx 1 root root 20 Mär 14 11:40 board-2.bin -> ../hw2.0/board-2.bin
  lrwxrwxrwx 1 root root 15 Mär 14 11:40 m3.bin -> ../hw2.0/m3.bin
  lrwxrwxrwx 1 root root 18 Mär 14 11:40 regdb.bin -> ../hw2.0/regdb.bin

which at first glance is the same

[Sesto (sepische)]

Thanks bernstein also I have solved with yours:
sudo rm
/lib/firmware/ath11k/WCN6855/hw2.1
after:
sudo apt-get update && sudo
apt-get dist-upgrade -y

Il 15.03.2022 16:11 bernstein ha scritto:

>
thanks Allan! For me a simple :
>
> rm
/lib/firmware/ath11k/WCN6855/hw2.1
>
> is all that was needed before
restarting the update process.
>
> The result is that before the failed
upgrade it looked like this :
>
> lrwxrwxrwx 1 root root 5 Feb 17 08:51
hw2.1 -> hw2.0
>
> and after the successful upgrade it now looks like
this :
>
> drwxr-xr-x 2 root root 6 Mär 15 15:34 .
> lrwxrwxrwx 1 root
root 17 Mär 14 11:40 amss.bin -> ../hw2.0/amss.bin
> lrwxrwxrwx 1 root
root 20 Mär 14 11:40 board-2.bin -> ../hw2.0/board-2.bin
> lrwxrwxrwx 1
root root 15 Mär 14 11:40 m3.bin -> ../hw2.0/m3.bin
> lrwxrwxrwx 1 root
root 18 Mär 14 11:40 regdb.bin -> ../hw2.0/regdb.bin
>
> which at first
glance is the same
>
> --
> You received this bug notification because
you are subscribed to a
> duplicate bug report (1964926).
>
https://bugs.launchpad.net/bugs/1964814 [1]
>
> Title:
> linux-firmware
fails to upgrade to 20220314.gitcd01f857-0ubuntu1
>
> Status in
linux-firmware package in Ubuntu:
> Fix Committed
> Status in
linux-firmware source package in Jammy:
> Fix Committed
>
> Bug
description:
> linux-firmware fails to upgrade with:
>
> unable to open
'/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-
> new': No such file
or directory
>
> $ sudo apt dist-upgrade
> Reading package lists...
Done
> Building dependency tree... Done
> Reading state information...
Done
> Calculating upgrade... Done
> The following packages will be
upgraded:
> linux-firmware
> 1 to upgrade, 0 to newly install, 0 to
remove and 0 not to upgrade.
> Need to get 0 B/238 MB of archives.
>
After this operation, 24.9 MB of additional disk space will be used.
>
Do you want to continue? [Y/n] y
> (Reading database ... 272091 files
and directories currently installed.)
> Preparing to unpack
.../linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb ...
> Unpacking
linux-firmware (20220314.gitcd01f857-0ubuntu1) over
(20220302.gitee0667aa-0ubuntu1) ...
> dpkg: error processing archive
/var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb
(--unpack):
> unable to open
'/lib/firmware/ath11k/WCN6855/hw2.0/regdb.bin.dpkg-new': No such file or
directory
> No apport report written because the error message indicates
an issue on the local system
> update-initramfs: Generating
/boot/initrd.img-5.15.0-23-generic
> I: The initramfs will attempt to
resume from /dev/dm-2
> I: (/dev/mapper/vgubuntu-swap_1)
> I: Set the
RESUME variable to override this.
> update-initramfs: Generating
/boot/initrd.img-5.15.0-22-generic
> I: The initramfs will attempt to
resume from /dev/dm-2
> I: (/dev/mapper/vgubuntu-swap_1)
> I: Set the
RESUME variable to override this.
> Errors were encountered while
processing:
>
/var/cache/apt/archives/linux-firmware_20220314.gitcd01f857-0ubuntu1_all.deb
>
E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> To manage
notifications about this bug go to:
>
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1964814/+subscriptions
[2]

Voucher M...