After I updated from an out dated Kernel to the latest Kernel my Graphics drivers for NVIDIA would not update so I uninstalled the drivers and installed the open source ones restarted my pc then reverted back to the proprietary ones where it then updated. Then I noticed my network drivers said they weren’t installed I reinstalled them and the Bluetooth hasn’t worked since. Whenever I try to enable it it disappears from the task bar, and I can’t connect anything. Most the tings I’ve tried to do haven’t worked so I tried trouble shooting it and this is what I got.
[catfish1243@CatishCreations ~]$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: active (running) since Sat 2024-05-18 22:40:47 PDT; 15h ago
Docs: man:bluetoothd(8)
Main PID: 1059 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 38250)
Memory: 2.0M (peak: 2.3M)
CPU: 26ms
CGroup: /system.slice/bluetooth.service
└─1059 /usr/lib/bluetooth/bluetoothd
May 18 22:40:47 CatishCreations bluetoothd[1059]: Starting SDP server
May 18 22:40:47 CatishCreations bluetoothd[1059]: src/plugin.c:init_plugin() System does not support bap plugin
May 18 22:40:47 CatishCreations bluetoothd[1059]: src/plugin.c:init_plugin() System does not support bass plugin
May 18 22:40:47 CatishCreations bluetoothd[1059]: src/plugin.c:init_plugin() System does not support mcp plugin
May 18 22:40:47 CatishCreations bluetoothd[1059]: src/plugin.c:init_plugin() System does not support vcp plugin
May 18 22:40:47 CatishCreations bluetoothd[1059]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
May 18 22:40:47 CatishCreations bluetoothd[1059]: src/plugin.c:init_plugin() System does not support micp plugin
May 18 22:40:47 CatishCreations bluetoothd[1059]: src/plugin.c:init_plugin() System does not support ccp plugin
May 18 22:40:47 CatishCreations bluetoothd[1059]: src/plugin.c:init_plugin() System does not support csip plugin
May 18 22:40:47 CatishCreations bluetoothd[1059]: Bluetooth management interface 1.22 initialized`
After that I tried a reinstalling blueman and a bunch of other files. Nothing worked so I checked the Journal and got this.
[catfish1243@CatishCreations ~]$ journalctl -p 3 -xb
May 18 22:40:42 CatishCreations kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP1.PTXH.RHUB.POT9], AE_NOT_FOUND (20230628/dswload2-162)
May 18 22:40:42 CatishCreations kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20230628/psobject-220)
May 18 22:40:44 CatishCreations (udev-worker)[420]: event10: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
May 18 22:40:44 CatishCreations kernel:
May 18 22:40:45 CatishCreations kernel: Bluetooth: hci0: Failed to load firmware file (-2)
May 18 22:40:45 CatishCreations kernel: Bluetooth: hci0: Failed to set up firmware (-2)
May 18 22:40:51 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 18 22:41:04 CatishCreations lightdm[1478]: gkr-pam: unable to locate daemon control file
May 18 22:47:10 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 19 12:54:27 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 19 12:59:34 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 19 13:54:36 CatishCreations (udev-worker)[38478]: event10: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument`
I don’t know how to fix this and I haven’t been able to find this same problem with a solution that worked.
Practically this means that the firmware file is not there which is needed to conrol the bluetooth device However… from the logs I cannot say anything further.
Found a post after looking specifically for posts about Bluetooth firmware issues after so here is some more relevant information.
[catfish1243@CatishCreations ~]$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
So what is soft blocking it? Sadly this post didn’t help me solve it, put it did help me trouble shoot it.
The only thing I see here is the activated software block… the hardware block would be a physical switch.
rfkill toggle bluetooth
# or
rfkill unblock bluetooth
Anything else works as expected. In Cinnamon there should be also an entry at the settings to enable/disable bluetooth what is the equivalent to rfkill.
Still not working. Mod edit: uploaded image(s) removed
Terminal Text Below
[catfish1243@CatishCreations ~]$ rfkill toggle bluetooth
[catfish1243@CatishCreations ~]$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
[catfish1243@CatishCreations ~]$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
[catfish1243@CatishCreations ~]$ rfkill unblock bluetooth
[catfish1243@CatishCreations ~]$ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
yeah now it is not blocked (deactivated). Check again the kernel message about bluetooth. see above (dmesg) I cannot believe that there is nothing, when the device is recognized in inxi.
May 18 22:40:42 CatishCreations kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP1.PTXH.RHUB.POT9], AE_NOT_FOUND (20230628/dswload2-162)
May 18 22:40:42 CatishCreations kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20230628/psobject-220)
May 18 22:40:44 CatishCreations (udev-worker)[420]: event10: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
May 18 22:40:44 CatishCreations kernel:
May 18 22:40:45 CatishCreations kernel: Bluetooth: hci0: Failed to load firmware file (-2)
May 18 22:40:45 CatishCreations kernel: Bluetooth: hci0: Failed to set up firmware (-2)
May 18 22:40:51 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 18 22:41:04 CatishCreations lightdm[1478]: gkr-pam: unable to locate daemon control file
May 18 22:47:10 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 19 12:54:27 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 19 12:59:34 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 19 13:54:36 CatishCreations (udev-worker)[38478]: event10: Failed to call EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
May 19 14:50:25 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 19 14:52:45 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 19 15:23:16 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 19 15:28:21 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 19 18:33:06 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 19 18:35:03 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 19 19:25:24 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 19 19:27:20 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 20 10:01:16 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 20 10:03:49 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 20 12:17:24 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 20 12:19:25 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 20 15:28:06 CatishCreations kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
May 20 16:19:33 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
May 20 16:19:57 CatishCreations wpa_supplicant[1192]: bgscan simple: Failed to enable signal strength monitoring
However… from the logs I cannot say anything further.
(dmesg) I cannot believe that there is nothing, when the device is recognized in inxi.