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
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
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.
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.
no joy so far. There is only the F12 key that is lit already and it has the Wireless symbol on it. From what I’ve acknowledged this adapter is converged… so both Wireless/Bluetooth. The service is loaded but “dead” inactive… I’ll see to borrow a dongle bluetooth some day… for now I give up…
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Docs: man:bluetoothd(8)
lug 06 08:58:40 Mel0 systemd[1]: Condition check resulted in Bluetooth service being skipped.
lug 06 15:58:35 Mel0 systemd[1]: Condition check resulted in Bluetooth service being skipped.
lug 06 15:58:48 Mel0 systemd[1]: Condition check resulted in Bluetooth service being skipped.
systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2020-07-07 09:11:55 CEST; 5min ago
Docs: man:bluetoothd(8)
Main PID: 4721 (bluetoothd)
Status: “Running”
Tasks: 1 (limit: 14239)
Memory: 2.2M
CGroup: /system.slice/bluetooth.service
└─4721 /usr/libexec/bluetooth/bluetoothd
lug 07 09:11:55 [xxxxxxxx systemd[1]: Starting Bluetooth service…
lug 07 09:11:55 [xxxxxxxx bluetoothd[4721]: Bluetooth daemon 5.54
lug 07 09:11:55 [xxxxxxxx systemd[1]: Started Bluetooth service.
lug 07 09:11:55 [xxxxxxxx bluetoothd[4721]: Starting SDP server
lug 07 09:11:55 [xxxxxxxx bluetoothd[4721]: Bluetooth management interface 1.14 initialized
however, it still does not work:
sudo modprobe btusb
[sudo] password for [xxxxxxxx:
[xxxxxxxx ~]$ systemctl restart bluetooth.service
[xxxxxxxx ~]$ ps -aux|grep bluetoothd
root 4721 0.0 0.0 8380 4852 ? Ss 09:11 0:00 /usr/libexec/bluetooth/bluetoothd
[xxxxxxxx 4943 0.0 0.0 216120 908 pts/0 S+ 09:12 0:00 grep --color=auto bluetoothd
[xxxxxxxx~]$ bluetoothctl
Agent registered
[bluetooth]# agent KeyboardOnly
Agent is already registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# power on
No default controller available
It’s like there is a conflict. Maybe the same fact that the device is converged is causing a conflict. Now I’m working but later I’ll turn off the wireless and see if bluetooth works
looking at the lspci -k output I get something interesting:
07:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
DeviceName: Ralink RT3290LE 802.11bgn 1x1 Wi-Fi Adapter
Subsystem: Hewlett-Packard Company Ralink RT3290LE 802.11bgn 1x1 Wi-Fi and Bluetooth 4.0 Combo Adapter Kernel driver in use: rt2800pci Kernel modules: rt2800pci
07:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth
Subsystem: Hewlett-Packard Company Ralink RT3290LE 802.11bgn 1x1 Wi-Fi and Bluetooth 4.0 Combo Adapter
I found out that driver for the Ralink RT3290LE is quite old and out of support. I don’t feel like sticking it into a kernel 5.5… I don’t know if my assumption is correct?
