Re: Re: Re: Severity: High / Debian 10 & 11 with Kernel 5.10.x-amd64 => Intel AX210 Wifi & Bluetooth not work
Salut Vincent,
Thanks for these informations.
Does this mean that I have a chance of seeing a patch arrive on Debian's 5.10 LTS kernel ?
Or is it better for me that I migrate to Ubuntu while waiting for the availability of a kernel 5.11 or higher in the Backports directory ?
I'm not really a fan of Ubuntu and even less of its Snap packages for Chromium and other softwares.
What bothers me the most in this story is that Intel guarantees us on its website compatibility with Kernel 5.10, which is why I bought this material and in the end it is not ;-( If j had known I would have chosen another material...
I wish you a great weekend.
Meilleures salutations.
Philippe
----Message d'origine----
De : vincent.debian@free.fr
Date : 17/06/2021 - 22:15 (E)
À : phamiet@bluewin.ch
Cc : andreimpopescu@gmail.com, 989777@bugs.debian.org, linux@packages.debian.org
Objet : Re: Re: Severity: High / Debian 10 & 11 with Kernel 5.10.x-amd64 => Intel AX210 Wifi & Bluetooth not work
Salut Philippe,
Le 2021-06-14 23:09, phamiet@bluewin.ch a écrit :
> The boot is difficult, I have a recurring error message that turns in a loop.
>
> journalctl -k | grep -Ei "iwl|bluetooth :
>
>
> root@portable-1:~# journalctl -k | grep -Ei "iwl|bluetooth"
> jun 14 22:48:11 portable-1 kernel: iwlwifi 0000:3b:00.0: enabling device (0000 -> 0002)
> jun 14 22:48:11 portable-1 kernel: iwlwifi 0000:3b:00.0: firmware: direct-loading firmware iwlwifi-ty-a0-gf-a0-59.ucode
> jun 14 22:48:11 portable-1 kernel: iwlwifi 0000:3b:00.0: api flags index 2 larger than supported by driver
> jun 14 22:48:11 portable-1 kernel: iwlwifi 0000:3b:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28
> jun 14 22:48:11 portable-1 kernel: iwlwifi 0000:3b:00.0: loaded firmware version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm
> jun 14 22:48:11 portable-1 kernel: iwlwifi 0000:3b:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
> jun 14 22:48:12 portable-1 kernel: iwlwifi 0000:3b:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
> jun 14 22:48:12 portable-1 kernel: Bluetooth: Core ver 2.22
> jun 14 22:48:12 portable-1 kernel: Bluetooth: HCI device and connection manager initialized
> jun 14 22:48:12 portable-1 kernel: Bluetooth: HCI socket layer initialized
> jun 14 22:48:12 portable-1 kernel: Bluetooth: L2CAP socket layer initialized
> jun 14 22:48:12 portable-1 kernel: Bluetooth: SCO socket layer initialized
> jun 14 22:48:12 portable-1 kernel: iwlwifi 0000:3b:00.0: firmware: failed to load iwlwifi-ty-a0-gf-a0.pnvm (-2)
> jun 14 22:48:12 portable-1 kernel: iwlwifi 0000:3b:00.0: base HW address: 54:14:f3:52:7b:e1
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Reading Intel version information failed (-22)
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Intel Read version failed (-22)
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Intel reset sent to retry FW download
> jun 14 22:48:12 portable-1 kernel: iwlwifi 0000:3b:00.0 wlp59s0: renamed from wlan0
> jun 14 22:48:12 portable-1 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> jun 14 22:48:12 portable-1 kernel: Bluetooth: BNEP filters: protocol multicast
> jun 14 22:48:12 portable-1 kernel: Bluetooth: BNEP socket layer initialized
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Reading Intel version information failed (-22)
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Intel Read version failed (-22)
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Intel reset sent to retry FW download
> jun 14 22:48:13 portable-1 kernel: Bluetooth: hci0: Reading Intel version information failed (-22)
> jun 14 22:48:13 portable-1 kernel: Bluetooth: hci0: Intel Read version failed (-22)
> jun 14 22:48:13 portable-1 kernel: Bluetooth: hci0: Intel reset sent to retry FW download
>
>
> systemctl status bluetooth.service :
>
>
> root@portable-1:~# systemctl status bluetooth.service
> ● bluetooth.service - Bluetooth service
> Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
> Active: active (running) since Mon 2021-06-14 22:48:12 CEST; 10min ago
> Docs: man:bluetoothd(8)
> Main PID: 649 (bluetoothd)
> Status: "Running"
> Tasks: 1 (limit: 38030)
> Memory: 2.6M
> CPU: 266ms
> CGroup: /system.slice/bluetooth.service
> └─649 /usr/libexec/bluetooth/bluetoothd
>
> jun 14 22:48:12 portable-1 bluetoothd[649]: src/main.c:parse_controller_config() Key file does not have key “LEScanIntervalConnect” in >
> jun 14 22:48:12 portable-1 bluetoothd[649]: src/main.c:parse_controller_config() Key file does not have key “LEScanWindowConnect” in gr>
> jun 14 22:48:12 portable-1 bluetoothd[649]: src/main.c:parse_controller_config() Key file does not have key “LEMinConnectionInterval” i>
> jun 14 22:48:12 portable-1 bluetoothd[649]: src/main.c:parse_controller_config() Key file does not have key “LEMaxConnectionInterval” i>
> jun 14 22:48:12 portable-1 bluetoothd[649]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionLatency” in gr>
> jun 14 22:48:12 portable-1 bluetoothd[649]: src/main.c:parse_controller_config() Key file does not have key “LEConnectionSupervisionTim>
> jun 14 22:48:12 portable-1 bluetoothd[649]: src/main.c:parse_controller_config() Key file does not have key “LEAutoconnecttimeout” in g>
> jun 14 22:48:12 portable-1 systemd[1]: Started Bluetooth service.
> jun 14 22:48:12 portable-1 bluetoothd[649]: Starting SDP server
> jun 14 22:48:12 portable-1 bluetoothd[649]: Bluetooth management interface 1.18 initialized
> lines 1-22/22 (END)
>
>
> If I can be useful for make a test on my system, do not hesitate to ask me it.
Thanks for the logs, Phillipe. From the information I gathered, it seems
Linux 5.11 is required to get bluetooth work on this adapter.
Before rebasing on Linux 5.11 for the 21.04 release, Ubuntu devs had to backport
some patches [1] to v5.10 to enable support for new Intel Typhoon Peak Bluetooth
(USB ID 8087:0032).
> Meilleures salutations.
>
> Philippe
Bonne soirée,
Vincent
[1] https://patchwork.kernel.org/project/bluetooth/list/?series=387475&archive=both
Reply to: