Bluetooth does not see the device

I’ve been trying to fix this bluetooth for a few days, but it doesn’t work. Bluetooth simply does not see any devices.
I’ve found some bugs, but I have no idea what to do next.


This is my plea for help. Help.

июл 20 17:44:05 fedora kernel: usb 3-2: Product: Bluetooth Radio
июл 20 17:44:10 fedora kernel: Bluetooth: Core ver 2.22
июл 20 17:44:10 fedora kernel: NET: Registered PF_BLUETOOTH protocol family
июл 20 17:44:10 fedora kernel: Bluetooth: HCI device and connection manager initialized
июл 20 17:44:10 fedora kernel: Bluetooth: HCI socket layer initialized
июл 20 17:44:10 fedora kernel: Bluetooth: L2CAP socket layer initialized
июл 20 17:44:10 fedora kernel: Bluetooth: SCO socket layer initialized
июл 20 17:44:11 fedora kernel: Bluetooth: hci0: Failed to read codec capabilities (-22)

The first step should be to post details of your hardware as text so others with the same problem can find it with a search engine. Please post (as text using the </> icon) the output from running inxi -Fzxx (using xx so we can see the
USB ID of the bluetooth radio).

The image you posted indicates a problem with the bluetooth firmware. Note that using journalctl gives more complete information than dmesg and can be used to compare changes from earlier boots. Do you boot other OS’s? Is the current install an upgrade or fresh install? Check for bluetooth settings in your BIOS.

When trying to solve issues like this you should make sure you have applied all updates to Fedora, and also vendor “BIOS” firmware updates. This way you won’t be chasing bugs that have been fixed, and people trying to help you will be using the same software.

Bluetooth:
  Device-1: IMC Networks Bluetooth Radio driver: btusb v: 0.8 type: USB
    rev: 1.0 speed: 12 Mb/s lanes: 1 bus-ID: 3-2:2 chip-ID: 13d3:3571
  Report: bt-adapter ID: hci0 rfk-id: 2 state: down
    bt-service: enabled,running rfk-block: hardware: no software: yes
    address: <filter>

[ippolit@fedora ~]$ journalctl
июл 18 20:22:24 fedora kernel: Linux version 6.2.9-300.fc38.x86_64 (mockbuild@3>
июл 18 20:22:24 fedora kernel: Command line: BOOT_IMAGE=(hd1,gpt2)/vmlinuz-6.2.>
июл 18 20:22:24 fedora kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 fl>
июл 18 20:22:24 fedora kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE re>
июл 18 20:22:24 fedora kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX re>
июл 18 20:22:24 fedora kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]>
июл 18 20:22:24 fedora kernel: x86/fpu: Enabled xstate features 0x7, context si>
июл 18 20:22:24 fedora kernel: signal: max sigframe size: 1776
июл 18 20:22:24 fedora kernel: BIOS-provided physical RAM map:
июл 18 20:22:24 fedora kernel: BIOS-e820: [mem 0x0000000000000000-0x00000000000>
июл 18 20:22:24 fedora kernel: BIOS-e820: [mem 0x00000000000a0000-0x00000000000>
июл 18 20:22:24 fedora kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000009b>
июл 18 20:22:24 fedora kernel: BIOS-e820: [mem 0x0000000009bff000-0x0000000009f>
июл 18 20:22:24 fedora kernel: BIOS-e820: [mem 0x000000000a000000-0x000000000a1>
июл 18 20:22:24 fedora kernel: BIOS-e820: [mem 0x000000000a200000-0x000000000a2>
июл 18 20:22:24 fedora kernel: BIOS-e820: [mem 0x000000000a20d000-0x00000000cb1>
июл 18 20:22:24 fedora kernel: BIOS-e820: [mem 0x00000000cb1e9000-0x00000000cc7>
июл 18 20:22:24 fedora kernel: BIOS-e820: [mem 0x00000000cc76b000-0x00000000cc7>
июл 18 20:22:24 fedora kernel: BIOS-e820: [mem 0x00000000cc7c2000-0x00000000cc9>
июл 18 20:22:24 fedora kernel: BIOS-e820: [mem 0x00000000cc975000-0x00000000cd1>
июл 18 20:22:24 fedora kernel: BIOS-e820: [mem 0x00000000cd1ff000-0x00000000cdf>
июл 18 20:22:24 fedora kernel: BIOS-e820: [mem 0x00000000ce000000-0x00000000cff>
июл 18 20:22:24 fedora kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7f>
lines 1-23

Sorry. I just recently started using linux and don’t know much about anything.

Now that we have the chip ID: the Linux Hardware Database has entries for your bluetooth adapater. It should be supported, but the “report” says it is “soft” blocked.

The image in your original post indcates that the "Direct firmware load failed. Please compare
the output of ls -l /usr/lib/firmware/rtw89/rtw8852b_fw.bin.xz with what I have:

% ls -l /usr/lib/firmware/rtw89/rtw8852b_fw.bin.xz
-rw-r--r--. 1 root root 161168 Jul  1 21:00 /usr/lib/firmware/rtw89/rtw8852b_fw.bin.xz

If yours is missing or older you need to install the current version. The relevant packages are:

linux-firmware-20230310-148.fc38.noarch
realtek-firmware-20230625-151.fc38.noarch

To see the satus of these packages:

% dnf info realtek-firmware-20230625-151.fc38.noarch
Last metadata expiration check: 0:38:04 ago on Thu Jul 20 09:44:30 2023.
Installed Packages
Name         : realtek-firmware
Version      : 20230625
Release      : 151.fc38
Architecture : noarch
Size         : 2.3 M
Source       : linux-firmware-20230625-151.fc38.src.rpm
Repository   : @System
From repo    : updates
Summary      : Firmware for Realtek WiFi/Bluetooth adapters
URL          : http://www.kernel.org/
License      : Redistributable, no modification permitted
Description  : Firmware for Realtek WiFi/Bluetooth adapters

It would also be useful to others who encounter the same issue to have the output of sudo journalctl -b -g bluetooth as searchable text – the image in your first post won’t be found with text searches.

They are in contradiction:

[ippolit@fedora ~]$ sudo dnf install linux-firmware-20230310-148.fc38.noarch realtek-firmware-20230625-151.fc38.noarch
Последняя проверка окончания срока действия метаданных: 0:48:40 назад, Чт 20 июл 2023 17:59:42.
Зависимости разрешены.
================================================================================
 Пакет                 Архитектура Версия                    Репозиторий  Размер
================================================================================
Установка:
 linux-firmware        noarch      20230310-148.fc38         fedora       122 M
 realtek-firmware      noarch      20230625-151.fc38         updates      2.3 M

Результат транзакции
================================================================================
Установка  2 Пакета

Общий размер: 124 M
Объем изменений: 130 M
Все правильно? [Д/н]: 
Загрузка пакетов:
[SKIPPED] linux-firmware-20230310-148.fc38.noarch.rpm: Already downloaded      
[SKIPPED] realtek-firmware-20230625-151.fc38.noarch.rpm: Already downloaded    
Проверка транзакции
Проверка транзакции успешно завершена.
Идет проверка транзакции
Ошибка: Ошибка при проверке транзакции:
  конфликт файла /usr/lib/firmware/rtl_bt/rtl8761b_fw.bin.xz при попытках установки linux-firmware-20230310-148.fc38.noarch и realtek-firmware-20230625-151.fc38.noarch
  конфликт файла /usr/lib/firmware/rtl_bt/rtl8761bu_fw.bin.xz при попытках установки linux-firmware-20230310-148.fc38.noarch и realtek-firmware-20230625-151.fc38.noarch
  конфликт файла /usr/lib/firmware/rtl_bt/rtl8852au_fw.bin.xz при попытках установки linux-firmware-20230310-148.fc38.noarch и realtek-firmware-20230625-151.fc38.noarch
  конфликт файла /usr/lib/firmware/rtl_bt/rtl8852bu_fw.bin.xz при попытках установки linux-firmware-20230310-148.fc38.noarch и realtek-firmware-20230625-151.fc38.noarch
  конфликт файла /usr/lib/firmware/rtl_bt/rtl8852cu_fw.bin.xz при попытках установки linux-firmware-20230310-148.fc38.noarch и realtek-firmware-20230625-151.fc38.noarch
  конфликт файла /usr/lib/firmware/rtlwifi/rtl8188eufw.bin.xz при попытках установки linux-firmware-20230310-148.fc38.noarch и realtek-firmware-20230625-151.fc38.noarch
  конфликт файла /usr/lib/firmware/rtw88/rtw8822c_fw.bin.xz при попытках установки linux-firmware-20230310-148.fc38.noarch и realtek-firmware-20230625-151.fc38.noarch
  конфликт файла /usr/lib/firmware/rtw89/rtw8852b_fw.bin.xz при попытках установки linux-firmware-20230310-148.fc38.noarch и realtek-firmware-20230625-151.fc38.noarch
  конфликт файла /usr/lib/firmware/rtw89/rtw8852c_fw.bin.xz при попытках установки linux-firmware-20230310-148.fc38.noarch и realtek-firmware-20230625-151.fc38.noarch

It turned out to install without specifying the version, but the error still remained.

[ippolit@fedora ~]$ dnf info realtek-firmware
Последняя проверка окончания срока действия метаданных: 0:55:29 назад, Чт 20 июл 2023 18:12:20.
Установленные пакеты
Имя          : realtek-firmware
Версия       : 20230625
Выпуск       : 151.fc38
Архитектура  : noarch
Размер       : 2.3 M
Источник     : linux-firmware-20230625-151.fc38.src.rpm
Репозиторий  : @System
Из репозитор : updates
Краткое опис : Firmware for Realtek WiFi/Bluetooth adapters
URL          : http://www.kernel.org/
Лицензия     : Redistributable, no modification permitted
Описание     : Firmware for Realtek WiFi/Bluetooth adapters

[ippolit@fedora ~]$ dnf info linux-firmware
Последняя проверка окончания срока действия метаданных: 0:56:07 назад, Чт 20 июл 2023 18:12:20.
Установленные пакеты
Имя          : linux-firmware
Версия       : 20230625
Выпуск       : 151.fc38
Архитектура  : noarch
Размер       : 95 M
Источник     : linux-firmware-20230625-151.fc38.src.rpm
Репозиторий  : @System
Из репозитор : updates
Краткое опис : Firmware files used by the Linux kernel
URL          : http://www.kernel.org/
Лицензия     : GPL+ and GPLv2+ and MIT and Redistributable, no modification permitted
Описание     : This package includes firmware files required for some devices to
             : operate.

journalctl:

[ippolit@fedora ~]$ sudo journalctl -b -g bluetooth
[sudo] пароль для ippolit: 
июл 20 19:02:51 fedora kernel: usb 3-2: Product: Bluetooth Radio
июл 20 19:02:57 fedora kernel: Bluetooth: Core ver 2.22
июл 20 19:02:57 fedora kernel: NET: Registered PF_BLUETOOTH protocol family
июл 20 19:02:57 fedora kernel: Bluetooth: HCI device and connection manager initialized
июл 20 19:02:57 fedora kernel: Bluetooth: HCI socket layer initialized
июл 20 19:02:57 fedora kernel: Bluetooth: L2CAP socket layer initialized
июл 20 19:02:57 fedora kernel: Bluetooth: SCO socket layer initialized
июл 20 19:02:57 fedora kernel: Bluetooth: hci0: Failed to read codec capabilities (-22)
июл 20 19:02:57 fedora systemd[1]: Starting bluetooth.service - Bluetooth service...
июл 20 19:02:57 fedora (uetoothd)[909]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
июл 20 19:02:57 fedora bluetoothd[909]: Bluetooth daemon 5.68
июл 20 19:02:58 fedora systemd[1]: Started bluetooth.service - Bluetooth service.
июл 20 19:02:58 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
июл 20 19:02:58 fedora kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
июл 20 19:02:58 fedora kernel: Bluetooth: BNEP filters: protocol multicast
июл 20 19:02:58 fedora kernel: Bluetooth: BNEP socket layer initialized
июл 20 19:02:58 fedora bluetoothd[909]: Bluetooth management interface 1.22 initialized
июл 20 19:02:58 fedora kernel: Bluetooth: MGMT ver 1.22
июл 20 19:02:58 fedora systemd[1]: Reached target bluetooth.target - Bluetooth Support.
июл 20 19:02:58 fedora NetworkManager[1052]: <info>  [1689868978.4606] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.42.8-1.fc38/libnm-device-plugin-bluetooth.so)
июл 20 19:03:12 fedora kernel: Bluetooth: RFCOMM TTY layer initialized
июл 20 19:03:12 fedora kernel: Bluetooth: RFCOMM socket layer initialized
июл 20 19:03:12 fedora kernel: Bluetooth: RFCOMM ver 1.11
июл 20 19:03:13 fedora pulseaudio[2212]: Could not find org.bluez.BatteryProviderManager1.RegisterBatteryProvider(), is bluetoothd started with experimental features enabled (-E flag)?
июл 20 19:03:23 fedora systemd[1825]: Started app-gnome-gnome\x2dbluetooth\x2dpanel-2959.scope - Application launched by gnome-shell.
июл 20 19:03:23 fedora systemd[1825]: Starting obex.service - Bluetooth OBEX service...
июл 20 19:03:23 fedora systemd[1825]: Started obex.service - Bluetooth OBEX service.
июл 20 19:04:19 fedora systemd[1825]: app-gnome-gnome\x2dbluetooth\x2dpanel-2959.scope: Consumed 4.559s CPU time.
июл 20 19:04:46 fedora sudo[3431]:  ippolit : TTY=pts/0 ; PWD=/home/ippolit ; USER=root ; COMMAND=/usr/bin/journalctl -b -g bluetooth
июл 20 19:12:39 fedora sudo[5743]:  ippolit : TTY=pts/0 ; PWD=/home/ippolit ; USER=root ; COMMAND=/usr/bin/journalctl -b -g bluetooth

Which error? I don’t see the Direct firmware load for rtw89/rtw8852b_fw.bin failed: -19 error.

I’m talking about this mistake:

Bluetooth: hci0: Failed to read codec capabilities (-22)

That just says bluetooth isn’t working. Failiure to load firmware will do that, now there appears to be something else preventing bluetooth from working. Sometimes you need a system -dependent trick to fully reset bluetooth devices (disable in BIOS, the reenable, etc.) after a firmware problem.

1 Like

I want to thank you. So, thank you so much! Today is a great day, today I got bluetooth. Thanks!

1 Like

Hello!

I had a similar problem with my Tuxedo InfinityBook Pro 14 Gen6 running Fedora 38, that would no longer be able to pair with my Logitech MX Ergo trackball, while still being able to pair with my Sony WH-1000XM5 headphones. The device would not appear in the list of pairable devices after it entered pairing mode and in the bluetoothctl console I set the adapter to power on and scan on.

How to debug Bluetooth problems - Fedora Project Wiki, Bluetooth - Gentoo Wiki and Bluetooth - ArchWiki did not help to resolve the problem.

As you suggested, I went into the laptop firmware / BIOS settings, disabled the built-in bluetooth adapter, rebooted, opened the firmware settings again, enabled the bluetooth adapter again, rebooted again, put the trackball device in pairing mode and it would now appear in the list of pairable devices.

Thank you!