Path: csiph.com!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!bofh.it!news.nic.it!robomod From: Vincent Blut Newsgroups: linux.debian.bugs.dist,linux.debian.kernel Subject: Bug#989777: Re: Severity: High / Debian 10 &amp;amp;amp; 11 with Kernel 5.10.x-amd64 =&amp;amp;gt; Intel AX210 Wifi &amp;amp;amp; Bluetooth not work Date: Thu, 14 Oct 2021 16:10:02 +0200 Message-ID: References: X-Original-To: phamiet@bluewin.ch, 989777@bugs.debian.org X-Mailbox-Line: From debian-bugs-dist-request@lists.debian.org Thu Oct 14 14:09:08 2021 Old-Return-Path: X-Spam-Flag: NO X-Spam-Score: -3.5 Reply-To: Vincent Blut , 989777@bugs.debian.org Resent-To: debian-bugs-dist@lists.debian.org Resent-Cc: Debian Kernel Team X-Debian-Pr-Message: followup 989777 X-Debian-Pr-Package: src:linux X-Debian-Pr-Source: linux MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="P0ddc9J37wBaUhsh" Content-Disposition: inline X-Debian-Message: from BTS X-Mailing-List: archive/latest/1683944 List-ID: List-URL: Approved: robomod@news.nic.it Lines: 152 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Thu, 14 Oct 2021 16:04:39 +0200 X-Original-Message-ID: X-Original-References: <63946487.15062.1623525062225@bluewin.ch> <756395894.17543.1634213510109@bluewin.ch> <63946487.15062.1623525062225@bluewin.ch> <756395894.17543.1634213510109@bluewin.ch> Xref: csiph.com linux.debian.bugs.dist:1075925 linux.debian.kernel:73295 --P0ddc9J37wBaUhsh Content-Type: text/plain; protected-headers=v1; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Date: Thu, 14 Oct 2021 16:04:39 +0200 From: Vincent Blut To: phamiet@bluewin.ch, 989777@bugs.debian.org Subject: Re: Bug#989777: Re: Severity: High / Debian 10 &amp;amp;amp; 11 with Kernel 5.10.x-amd64 =&amp;amp;gt; Intel AX210 Wifi &amp;amp;amp; Bluetooth not work Hi Philippe, Le 2021-10-14 14:11, phamiet@bluewin.ch a =C3=A9crit : > Hello Vincent, >=20 >=20 > Finally I had to force the installation of the firmware-iwlwifi 20210818-= 1 for it to work. >=20 > Configuring preferences.d (with files =3D> stable-prioritaire + testing-o= n-bullseye) and sources.list (see attached files) was not enough. By the w= ay in Debian 12.1 sources.list is unusually short, it does not contain the = "Bullseye base repository" or other directory, which can be very annoying f= or a beginner user... >=20 > After this manipulation the Bluetooth works +/-. When starting the OS for= the first time, Bluetooth is present and working, I can connect my Logitec= h MX Anywhere 2S mouse but it is impossible to connect a Logitech CRAFT key= board. Indeed, the Logitech CRAFT keyboard requires the entry of a series o= f numeric digits to confirm its connection with the OS, but no series of di= gits is provided by the OS to make this connection, so it fails... Installing the 'solaar' package should help you pair the keyboard with the receiver. =20 > After a simple start, the Bluetooth connection no longer works. If I try = to start blueman-manager manually I get the following error message : >=20 >=20 > philippe@laptop:~$ blueman-manager > blueman-manager version 2.1.4 starting > blueman-manager 13.43.01 ERROR Manager:118 on_dbus_name_appeared: Defa= ult adapter not found, trying first available. > blueman-manager 13.43.01 ERROR Manager:122 on_dbus_name_appeared: No a= dapter(s) found, exiting >=20 >=20 > root@laptop:~# blueman-manager > Unable to init server: Could not connect: Connection refused > Unable to init server: Impossible de se connecter=C2=A0: Connection refus= ed > Traceback (most recent call last): > File "/usr/bin/blueman-manager", line 44, in > manager =3D Blueman() > File "/usr/lib/python3/dist-packages/blueman/main/Manager.py", line 29,= in __init__ > super().__init__(title=3D_("Bluetooth Devices")) > File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 515, in= __init__ > raise RuntimeError( > RuntimeError: Gtk couldn't be initialized. Use Gtk.init_check() if you wa= nt to handle this case. >=20 >=20 > In this case if I run the command journalctl -k | grep -Ei 'bluetooth|iwl= wifi' I get : >=20 >=20 > root@laptop:~# journalctl -k | grep -Ei 'bluetooth|iwlwifi'=20 > oct 14 13:34:21 laptop kernel: iwlwifi 0000:3b:00.0: enabling device (000= 0 -> 0002) > oct 14 13:34:21 laptop kernel: iwlwifi 0000:3b:00.0: firmware: failed to = load iwlwifi-ty-a0-gf-a0-64.ucode (-2) > oct 14 13:34:21 laptop kernel: iwlwifi 0000:3b:00.0: Direct firmware load= for iwlwifi-ty-a0-gf-a0-64.ucode failed with error -2 > oct 14 13:34:21 laptop kernel: iwlwifi 0000:3b:00.0: firmware: direct-loa= ding firmware iwlwifi-ty-a0-gf-a0-63.ucode > oct 14 13:34:21 laptop kernel: iwlwifi 0000:3b:00.0: api flags index 2 la= rger than supported by driver > oct 14 13:34:21 laptop kernel: iwlwifi 0000:3b:00.0: TLV_FW_FSEQ_VERSION:= FSEQ Version: 0.0.2.25 > oct 14 13:34:21 laptop kernel: iwlwifi 0000:3b:00.0: loaded firmware vers= ion 63.c04f3485.0 ty-a0-gf-a0-63.ucode op_mode iwlmvm > oct 14 13:34:21 laptop kernel: iwlwifi 0000:3b:00.0: firmware: failed to = load iwl-debug-yoyo.bin (-2) > oct 14 13:34:21 laptop kernel: Bluetooth: Core ver 2.22 > oct 14 13:34:21 laptop kernel: NET: Registered PF_BLUETOOTH protocol fami= ly > oct 14 13:34:21 laptop kernel: Bluetooth: HCI device and connection manag= er initialized > oct 14 13:34:21 laptop kernel: Bluetooth: HCI socket layer initialized > oct 14 13:34:21 laptop kernel: Bluetooth: L2CAP socket layer initialized > oct 14 13:34:21 laptop kernel: Bluetooth: SCO socket layer initialized > oct 14 13:34:21 laptop kernel: Bluetooth: hci0: Firmware timestamp 2021.2= 8 buildtype 1 build 28502 > oct 14 13:34:21 laptop kernel: Bluetooth: hci0: No device address configu= red > oct 14 13:34:21 laptop kernel: bluetooth hci0: firmware: direct-loading f= irmware intel/ibt-0041-0041.sfi > oct 14 13:34:21 laptop kernel: Bluetooth: hci0: Found device firmware: in= tel/ibt-0041-0041.sfi > oct 14 13:34:21 laptop kernel: Bluetooth: hci0: Boot Address: 0x100800 > oct 14 13:34:21 laptop kernel: Bluetooth: hci0: Firmware Version: 86-28.21 > oct 14 13:34:21 laptop kernel: Bluetooth: hci0: Firmware already loaded > oct 14 13:34:21 laptop kernel: iwlwifi 0000:3b:00.0: Detected Intel(R) Wi= -Fi 6 AX210 160MHz, REV=3D0x420 > oct 14 13:34:22 laptop kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1= =2E3 > oct 14 13:34:22 laptop kernel: Bluetooth: BNEP filters: protocol multicast > oct 14 13:34:22 laptop kernel: Bluetooth: BNEP socket layer initialized > oct 14 13:34:22 laptop kernel: iwlwifi 0000:3b:00.0: firmware: direct-loa= ding firmware iwlwifi-ty-a0-gf-a0.pnvm > oct 14 13:34:22 laptop kernel: iwlwifi 0000:3b:00.0: loaded PNVM version = 0xd35929d8 > oct 14 13:34:22 laptop kernel: iwlwifi 0000:3b:00.0: Detected RF GF, rfid= =3D0x10d000 > oct 14 13:34:22 laptop kernel: iwlwifi 0000:3b:00.0: base HW address: 54:= 14:f3:52:7b:e1 > oct 14 13:34:22 laptop kernel: iwlwifi 0000:3b:00.0 wlp59s0: renamed from= wlan0 > oct 14 13:45:30 laptop kernel: iwlwifi 0000:3b:00.0: Got NSS =3D 4 - trim= ming to 2 >=20 >=20 > There is progress but it is not yet 100% functional... Indeed, there are some warm boot initialization issues since Linux 5.13. Are you able to reproduce the aforementioned issue when doing a cold boot? > Thank you for everything. >=20 > Bonne journ=C3=A9e. >=20 > Philippe Bonne journ=C3=A9e, Vincenc --P0ddc9J37wBaUhsh Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQSRJQjHKbAUfuoc+DAQn1qAt/bgAQUCYWg49wAKCRAQn1qAt/bg AW4RAQCn3vB/IlWAyYckZAu5LH4ljoANlDrOZ+SJXaCWMKHe2gEA5OClcyyY2ZjW QJc7tc6NX/a/6/QLH9u+85haB2e53ws= =njtQ -----END PGP SIGNATURE----- --P0ddc9J37wBaUhsh--