Bug#940813: firmware-iwlwifi: iwlwifi-9000-pu-b0-jf-b0-46.ucode is broken
Package: firmware-iwlwifi
Version: 20190717-2
Followup-For: Bug #940813
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hey!
I was running in this problem (as well as some unreliability with the
Bluetooth). Instead of downgrading to -41, I have updated the -46 to
the version in linux-firmware.git. There has been one additional
version (and more for Bluetooth):
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/iwlwifi-9000-pu-b0-jf-b0-46.ucode
- -- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (101, 'experimental-debug'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.4.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
firmware-iwlwifi depends on no packages.
firmware-iwlwifi recommends no packages.
Versions of packages firmware-iwlwifi suggests:
ii initramfs-tools 0.135
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAl4eLQsSHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX5QUYP/0CPAAZKVJPFnA2uKctgfLbiM4A5Sub7
AzLzTkeUjSajrZT8t001HZN/XYreXcfA5GhDHm9BgJ2Xh5/1qThmfe8+l0ZOEss2
gLG0DC+QMx49OUddCX09U36N8Fml3fCMbO2RU2XIWmyjZou/s7Mxv5P9C+04uO/b
OEtiFF1UX/cCgW9uezND2nqNQh+hRtEELnzdCb2F8ymWWA5f7zJsmiTBf1RVgDB0
pZ4TlzIRPcrTELxelkz+jkuqAHANxbJKwWIDFsJ58EbIp6hHSQTC4s+rL1ErEipA
NkPxoBe5a3QPQ3zJ1XzB9Z7X7w4mSRdDLP22BocFHDeREhFQ0hoVgL2T0SkxPzAe
9M638NMiQUvtKh4fsj55Y7iF77x31/jvqoCvh+52aj1DHdzfOZI7SkNtl9uzLmEg
Np96couiDk3wHrAmWyrzti1VEu/vHTHD25T0pGdNZ7n8ec8b7v0ArYp2rGMAf7zp
Uki+98Qit7w/uf0MiwaKsXIm+eHttCdjdQL2j7qmXsDDpmgGTzum0nhyGlgA60O8
uTIwfvx7fKoVae7rntyZas2Dn//oDrG8UrSUkYaS2bgIxo1FZ2IRN8XSBPjVfQjn
sUopj4RcosxM+nLN7M284qD2fp+tunpYFJ1vyatvnBptmAAwVLkTn2gH9sYDtEzZ
lXbPmor0thvQ
=fKGB
-----END PGP SIGNATURE-----
Reply to: