Bluetooth does not work in Fedora 31

Hello I have HP ENVY 17-j111sl Notebook PC and Fedora 31 installed with kernel 5.5.17-200.fc31.x86_64. Bluetooth never worked since day 1. However it seems that the device is recognised and have no problems at all. So I don’t understand what could be wrong. The only key combination present on the keyboard is the wireless one… Fn+F12. Nothing else, not even a separated button below or on the notebook sides.

xxxxxxxx  compose]$ dmesg | grep Blue
[27290.195493] Bluetooth: Core ver 2.22
[27290.195583] Bluetooth: HCI device and connection manager initialized
[27290.195586] Bluetooth: HCI socket layer initialized
[27290.195588] Bluetooth: L2CAP socket layer initialized
[27290.195590] Bluetooth: SCO socket layer initialized
xxxxxxxxxxxx compose]$ rfkill list
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
xxxxxxxxxxxxx compose]$ dmesg | grep RT
[    0.022918] ACPI: BGRT 0x000000009CFC9000 000038 (v01 HPQOEM 1966     00000001 HP   00040000)
[    0.288401] PM: RTC time: 07:46:55, date: 2020-06-29
[    1.454283] rtc_cmos 00:02: RTC can wake from S4
[    3.013757] r8169 0000:0f:00.0 eth0: RTL8168g/8111g, a0:48:1c:eb:af:28, XID 4c0, IRQ 32
[    5.744606] systemd[1]: RTC configured in localtime, applying delta of 120 minutes to system time.
[    8.882835] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected
xxxxxxxxxxxx compose]$ dmesg | grep firmware
[    0.273714] Spectre V2 : Enabling Restricted Speculation for firmware calls
[   18.167315] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin'
[   18.317450] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37

1 Like
  1. check - bluetooth system install

    dnf install bluez

    [root@can simmon]# rpm -qa|grep bluez

  2. system enable for bluetooth

    a. check bluetooth daemon

    [root@can simmon]# ps -aux|grep bluetoothd
    root 848 0.0 0.0 8472 3388 ? Ss 6월28 0:00 /usr/libexec/bluetooth/bluetoothd
    root 32817 0.0 0.0 216216 2772 pts/2 S+ 02:03 0:00 grep --color=auto bluetooth

b, run setup, and also enable bluetooth.service

c. try bluetooth device connectivity in setup

What kind of setup tool is this?


We can specify the service status in ntsysv, setup, which checks the service setup status.



Package bluez-5.54-1.fc31.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
[xxxxxxxx ~] rpm -qa|grep bluez bluez-cups-5.54-1.fc31.x86_64 bluez-obexd-5.54-1.fc31.x86_64 bluez-5.54-1.fc31.x86_64 bluez-libs-5.54-1.fc31.x86_64 [xxxxxx ~] ps -aux|grep bluetoothd
xxxxx 3785 0.0 0.0 216120 832 pts/0 S+ 10:38 0:00 grep --color=auto bluetoothd

I don’t know how to check bluetooth connectivity from setup… .I’ll find out and revert. Meanwhile many thanks for your time!

1 Like

Bluetooth is not enabled on your device.

ps -aux|grep bluetoothd
xxxxx 3785 0.0 0.0 216120 832 pts/0 S+ 10:38 0:00 grep --color=auto bluetoothd

On my laptop, I have a function key for hardware operation, and please find out if there is an activation key for each device. Basically, it is in the form of an operation, but the Bluetooth daemon may not work in an inactive state.

After that, you can find the Bluetooth device in Settings and proceed with the synchronization process through the pairing process. If the Bluetooth operation is activated in Settings, you can check the setting status.

If you want to check the sound and operation characteristics through the Bluetooth device, activate the Bluetooth device on your phone. Afterwards, check the status of the Bluetooth sync in Fedora’s notebook settings to hear it louder from the notebook speaker. enjoy the music!!

You don’t have to install that tool. Just use the build-in capabilities of systemctl, which is an important and powerful tool to manage and troubleshoot services

Status of the bluetooth service:

systemctl status bluetooth.service

start the service

systemctl start bluetooth.service

activate the service upon every boot

systemctl enable bluetooth.service

stop the service

systemctl stop bluetooth.service
1 Like

ntsysv…I need.

There is no problem in operating with systemctl, but I think it is very useful to easily apply and understand the actual service status and operation.

It is necessary to install the Bluetooth driver in the server distribution. Considering which distribution the interrogator installed, the driver installation and verification process and processor verification are necessary.
I installed KDE on the server distribution and informed the operation status.


does that list your bluetooth adapter (in case it is a USB one, you need lsusb)?

I have to disagree. ntsysv does not tell you anything about the actual status. systemctl status foo (ex. systemctl status firewalld) provides detailed status information.

As a system reference, I think it’s perfectly good, but of course, it’s not a real-time service, but it provides great information that can be referenced after booting, as well as giving overall information.

It is just like that.

technical check link for you.