1. Forum
  2. Usenet
  3. LINUX.DEBIAN.KERNEL

  • Updating firmware-nonfree and open-athk9-htc-firmware in bullseye-backp

    From Ben Hutchings@21:1/5 to All on Sat Apr 22 17:00:01 2023
    Dear Backports Team,

    I have just uploaded two firmware packages to bullseye-backports:
    - firmware-nonfree
    - open-ath9k-htc-firmware

    The ath9k_htc firmware previously provided as a binary in firmware-
    nonfree -> firmware-atheros is now built from source by open-ath9k-htc- firmware -> firmware-ath9k-htc.

    firmware-ath9k-htc/bookworm has a *versioned* Breaks/Replaces against firmware-atheros, so keeping ath9k_htc in firmware-atheros for bullseye-backports could lead to a file conflict on upgrade. Therefore
    both packages need to be updated in bullseye-backports, and should be
    installed at the same time.

    Ben.

    --
    Ben Hutchings
    Theory and practice are closer in theory than in practice - John Levine

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAmRD8C8ACgkQ57/I7JWG EQkiExAAl0NBuzBwIJCUgOh+Xfw37flDSFjtLZXQZZPZZiX7UbsLRIWK8kdrv40J PJwaOIh6X9HbOO1tPdjIvhlzMA8mZFiroX2z62w3OPrKHlLqdNZFN5HiXGpG9lFj Qu5JiK9KpjbGT0dImk2T1V3KX/4jqMsDWg/X3hyarZQp5UgWUw8hjXIav79ZLaQ3 xF/HkTMtkeROwsh9jeCxbMgaBYaSoEOpUfE45T92PdjHZqmoz7MmJAO2imfz02Wq al9AFOkMsNlfRugJS3czYVhwd+8uJmVjYKDvDLyZFTxhlY8HdtxgTsezAFpqVdZc URcXsPLmo/hJ2N4SnD4xjGAyaDY2gZ7pZYmjOripf/3b+okNLzgeJsFR2cHIQQdm DG14oGOhHxPR+5aYjCbbLI+NwEaQAOUoXSYBMV3OFv7QIfWAt6vEwFS0QMumiCD7 +mXj/DlkqvXtt+/r1doen+poMYGQtUoHMkRbZBnkbqpyOFQO+5wpfI1GeAftc9YD +jRjwkKbBgge3EM0dDHbqakd89Cbc8CLFn7EvWoNI7NUZ1OTrYeYqyd1RN6ALEnz kRKVsI42h6sR/NqypCnsG0sqHmnFeLjmD3lLOdU3CTamtO0IAGJuUxQWtWaiyVoO JaBkyo5VvGu3d4PcVozPVpWy+eOfmNQUo1o6nIZWH40z38gEne0=
    =96WI
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Henrik Ahlgren@21:1/5 to Ben Hutchings on Sun Apr 23 12:30:01 2023
    On Sat, 2023-04-22 at 16:33 +0200, Ben Hutchings wrote:
    Dear Backports Team,

    I have just uploaded two firmware packages to bullseye-backports:
    - firmware-nonfree
    - open-ath9k-htc-firmware

    I've got a rather small /boot (235 MB, ext2), and trying to upgrade firmware-nonfree fills it up when initramfs-tools trigger generates initrd.img-5.10.0-21-amd64:

    Filesystem Size Used Avail Use% Mounted on
    /dev/nvme0n1p2 235M 227M 0 100% /boot

    The weird thing is that "du -hsx /boot" only reports 87M. There are no open deleted files according to lsof, and the situation remains even if I
    remount /boot. Furthermore, there are no errors during update-initramfs,
    and the generated initrd image seems fine (70593887 bytes).

    On another machine, update-initramfs just fails, and the disk does not fill
    up:

    update-initramfs: Generating /boot/initrd.img-5.10.0-21-amd64

    gzip: stdout: No space left on device
    E: mkinitramfs failure gzip 1
    update-initramfs: failed for /boot/initrd.img-5.10.0-21-amd64 with 1.
    dpkg: error processing package initramfs-tools (--configure):
    installed initramfs-tools package post-installation script subprocess returned error exit status 1
    Errors were encountered while processing:
    initramfs-tools
    needrestart is being skipped since dpkg has failed
    E: Sub-process /usr/bin/dpkg returned an error code (1)

    This machine has identical disk layout, but has less disk space remaining
    since it is still running the previous kernel version (5.10.0-20), and has
    two kernels installed under /boot. After the error, it reports the free
    disk space correctly (and the initrd.img remains untouched):

    Filesystem Size Used Avail Use% Mounted on
    /dev/sda2 235M 165M 58M 75% /boot

    I think I've seen this before a long time ago, and it was resolved by
    simply rebooting, but I'd like to understand why this happens and how to
    avoid it (other than increasing the size of /boot).

    Anyone else seen this?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)