Hi Philippe,
Le 2021-10-14 14:11, phamiet@bluewin.ch a écrit :
> Hello Vincent,
>
>
> Finally I had to force the installation of the firmware-iwlwifi 20210818-1 for it to work.
>
> Configuring preferences.d (with files => stable-prioritaire + testing-on-bullseye) and sources.list (see attached files) was not enough. By the way 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 for a beginner user...
>
> After this manipulation the Bluetooth works +/-. When starting the OS for the first time, Bluetooth is present and working, I can connect my Logitech MX Anywhere 2S mouse but it is impossible to connect a Logitech CRAFT keyboard. Indeed, the Logitech CRAFT keyboard requires the entry of a series of numeric digits to confirm its connection with the OS, but no series of digits 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.
> After a simple start, the Bluetooth connection no longer works. If I try to start blueman-manager manually I get the following error message :
>
>
> philippe@laptop:~$ blueman-manager
> blueman-manager version 2.1.4 starting
> blueman-manager 13.43.01 ERROR Manager:118 on_dbus_name_appeared: Default adapter not found, trying first available.
> blueman-manager 13.43.01 ERROR Manager:122 on_dbus_name_appeared: No adapter(s) found, exiting
>
>
> root@laptop:~# blueman-manager
> Unable to init server: Could not connect: Connection refused
> Unable to init server: Impossible de se connecter : Connection refused
> Traceback (most recent call last):
> File "/usr/bin/blueman-manager", line 44, in <module>
> manager = Blueman()
> File "/usr/lib/python3/dist-packages/blueman/main/Manager.py", line 29, in __init__
> super().__init__(title=_("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 want to handle this case.
>
>
> In this case if I run the command journalctl -k | grep -Ei 'bluetooth|iwlwifi' I get :
>
>
> root@laptop:~# journalctl -k | grep -Ei 'bluetooth|iwlwifi'
> oct 14 13:34:21 laptop kernel: iwlwifi 0000:3b:00.0: enabling device (0000 -> 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-loading firmware iwlwifi-ty-a0-gf-a0-63.ucode
> oct 14 13:34:21 laptop kernel: iwlwifi 0000:3b:00.0: api flags index 2 larger 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 version 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 family
> oct 14 13:34:21 laptop kernel: Bluetooth: HCI device and connection manager 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.28 buildtype 1 build 28502
> oct 14 13:34:21 laptop kernel: Bluetooth: hci0: No device address configured
> oct 14 13:34:21 laptop kernel: bluetooth hci0: firmware: direct-loading firmware intel/ibt-0041-0041.sfi
> oct 14 13:34:21 laptop kernel: Bluetooth: hci0: Found device firmware: intel/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=0x420
> oct 14 13:34:22 laptop kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> 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-loading 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=0x10d000
> 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 = 4 - trimming to 2
>
>
> 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.
>
> Bonne journée.
>
> Philippe
Bonne journée,
Vincenc
Attachment:
signature.asc
Description: PGP signature