Bluetooth disabled on KDE when I start the day

honestly, this happens to me from time to time with my bluetooth headset.

I just remove the file .config/bluedevilglobalrc and all is good again next time

3 Likes

removed it, rebooted it, nothing =( I’m doomed to use sudo modprobe -r btusb && sleep 10 && sudo modprobe btusb for the rest of my life.

I would still suggest trying out the “normal” dr460nized version who knows maybe it’s a preinstalled software that’s causing this issue?

or, if all fails you can make this a systemd command.

1 Like

Weird… it does happen to fix things for me, but might be another issue.

As an offtopic, to test these things, its always best to reboot, remove the file before logging in on KDE and then proceed. That is because by removing the “broken file”, the process that is using it might still “repeat on writing a broken file”.

Well… this is just trying wild guesses, but you can also try the “blueman” bluetooth app. Its pretty good when I am using window managers only (sway, hyprland, wayfire)

Btw… browsing the web for [ 9.470926] Bluetooth: hci0: Opcode 0x c03 failed: -110 … reveals a lot of results

1 Like

I hadn’t paid much attention to this earlier… but now that you mentioned, I thought I’d check dmesg again after interface say it’s working:

sudo dmesg | grep -Ei 'blue|firm'
[sudo] senha para johnny:       
[    0.000000] [Firmware Bug]: TPM Final Events table invalid
[    0.253233] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    5.151957] systemd[1]: TPM2 PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
[    7.628921] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[    7.757467] Bluetooth: Core ver 2.22
[    7.757495] NET: Registered PF_BLUETOOTH protocol family
[    7.757496] Bluetooth: HCI device and connection manager initialized
[    7.757498] Bluetooth: HCI socket layer initialized
[    7.757500] Bluetooth: L2CAP socket layer initialized
[    7.757503] Bluetooth: SCO socket layer initialized
[    7.868592] ath10k_pci 0000:3d:00.0: firmware ver WLAN.RM.4.4.1-00288- api 6 features wowlan,ignore-otp,mfp crc32 bf907c7c
[    8.441330] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[   10.494787] Bluetooth: hci0: Opcode 0x c03 failed: -110
[   10.780927] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   10.780931] Bluetooth: BNEP filters: protocol multicast
[   10.780935] Bluetooth: BNEP socket layer initialized
[  105.241192] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[  105.297105] Bluetooth: hci0: unexpected event for opcode 0x0c03
[  105.299075] Bluetooth: hci0: unexpected event for opcode 0x1003
[  105.356294] Bluetooth: MGMT ver 1.22
[  105.404032] Bluetooth: RFCOMM TTY layer initialized
[  105.404053] Bluetooth: RFCOMM socket layer initialized
[  105.404062] Bluetooth: RFCOMM ver 1.11

but filtering even more…

sudo dmesg | grep -Ei 'blue|firm' | grep hci0
[    8.441330] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[   10.494787] Bluetooth: hci0: Opcode 0x c03 failed: -110
[  105.241192] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[  105.297105] Bluetooth: hci0: unexpected event for opcode 0x0c03
[  105.299075] Bluetooth: hci0: unexpected event for opcode 0x1003

I’ll try looking into it this afternoon…

–edit

so I THOUGHT Bluetooth was working, right? Because it then said that device was enabled, yadda yadda. Then I tried connecting my bluetooth headphone to it.

And failed.

It says “connected” on the main settings screen, but the phone says it’s not. Besides the error on the wizard window, there’s no audio BT device, either.

image

so I guess I really need to dig on that error.

–edit

looking at this, I thought broadcom-bt driver would solve my problem. Octopi shows only one broadcom-bt-firmware-git. I install it… I reboot it… and still nothing =(

the hunt goes on…

–edit

just noticed I completely forgot to take/post the dmesg of a fresh boot, BEFORE the “modprobe fix”…

sudo dmesg | grep 'blue|firm'
[sudo] senha para johnny:       
[    5.583307] systemd[1]: TPM2 PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
[    8.595465] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[    8.843850] ath10k_pci 0000:3d:00.0: firmware ver WLAN.RM.4.4.1-00288- api 6 features wowlan,ignore-otp,mfp crc32 bf907c7c

no signs of anything bluetooth O.o and I don’t have that blacklist_btusb.cnf or restart-bt.service files… :thinking:

–edit

one more link, one more failure to solve it…

https://bbs.archlinux.org/viewtopic.php?id=249867

time for drastic measures: using the BIOS support assist feature to test if bluetooth is ok - it happened twice already that I had to raise issues with Dell to replace, because wifi was working but bluetooth was dead, and I just thought of that now. - yeah, not that, everything’s fine.

–edit

let’s see if this does the trick, just loaded it into the USB drive. brb.

–edit

booting from live non-gaming dr460nized, I don’t see the hci0 errors on dmesg anymore… but still says BT disabled.

transcription

sudo dmesg | grep -Ei 'blue|firm'
[    0.000000] [Firmware Bug]: TPM Final Events table invalid
[    0.250653] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    9.182359] systemd[1]: TPM2 PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
[   12.729848] Bluetooth: Core ver 2.22
[   12.729864] NET: Registered PF_BLUETOOTH protocol family
[   12.729866] Bluetooth: HCI device and connection manager initialized
[   12.729869] Bluetooth: HCI socket layer initialized
[   12.729871] Bluetooth: L2CAP socket layer initialized
[   12.729874] Bluetooth: SCO socket layer initialized
[   13.127117] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[   14.157992] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[   14.369894] ath10k_pci 0000:3d:00.0: firmware ver WLAN.RM.4.4.1-00288- api 6 features wowlan,ignore-otp,mfp crc32 bf907c7c
[   15.165754] Bluetooth: hci0: Opcode 0x c03 failed: -110
[   16.910068] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   16.910071] Bluetooth: BNEP filters: protocol multicast
[   16.910073] Bluetooth: BNEP socket layer initialized

And there it is, alright… Opcode 0x c03 failed.

After sudo modprobe -r btusb && sleep 10 && sudo modprobe btusb, it showed up again:

[  579.972482] usbcore: deregistering interface driver btusb
[  590.270021] usbcore: registered new interface driver btusb
[  590.270464] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[  590.326972] Bluetooth: hci0: unexpected event for opcode 0x0c03
[  590.328947] Bluetooth: hci0: unexpected event for opcode 0x1003
[  590.386549] Bluetooth: MGMT ver 1.22
[  590.458839] Bluetooth: RFCOMM TTY layer initialized
[  590.458848] Bluetooth: RFCOMM socket layer initialized
[  590.458852] Bluetooth: RFCOMM ver 1.11

Weirdly, the settings still show as if BT is now working, even with that error:

which I know will lead to faulty pairing, but let’s try again anyway…

again, no new messages on dmesg, and at first it seems like it’s working…

but then, it fails the wizard, and still no messages on dmesg? wonder if there’s anywhere else I could check… I’m gonna try to grab a hold of the older dr460nized version, see if that live USB gives this problem also… uh… there is no archive of previous releases, right? :man_facepalming:

–edit

bad news. awful news. tested through several other distros - Fedora, Arcolinux, popOS, openSuse. In all of them, the same error on dmesg on boot =( only thing I didn’t test was… reinstalling windows O.o

1 Like

Trying once again to gather all the information I can from the system about this:

 ╭─johnny@johnny in ~ took 15ms
 ╰─λ lsmod | grep blue
bluetooth            1155072  15 btrtl,btmtk,btintel,btbcm,bnep,btusb
ecdh_generic           16384  1 bluetooth
crc16                  12288  1 bluetooth
rfkill                 40960  10 bluetooth,dell_laptop,cfg80211

 ╭─johnny@johnny in ~ took 8s
 ╰─λ systool -v -m btusb
Module = "btusb"

  Attributes:
    coresize            = "86016"
    initsize            = "0"
    initstate           = "live"
    refcnt              = "0"
    srcversion          = "67C9DE037CE6B9213EFED7A"
    taint               = ""
    uevent              = <store method only>
    version             = "0.8"

  Parameters:
    disable_scofix      = "N"
    enable_autosuspend  = "Y"
    force_scofix        = "N"
    reset               = "Y"

  Sections:


 ╭─johnny@johnny in ~ took 2m35s
 ╰─λ modprobe -c | grep btusb
options btusb reset=1
alias of:N*T*Cusb1286,204e btusb
alias of:N*T*Cusb1286,204eC* btusb
alias of:N*T*Cusb4ca,301a btusb
alias of:N*T*Cusb4ca,301aC* btusb
alias of:N*T*Cusbcf3,e300 btusb
alias of:N*T*Cusbcf3,e300C* btusb
alias usb:v*p*d*dc*dsc*dp*icE0isc01ip01in* btusb
alias usb:v*p*d*dcE0dsc01dp01ic*isc*ip*in* btusb
alias usb:v*p*d*dcE0dsc01dp04ic*isc*ip*in* btusb
alias usb:v044Ep3001d*dc*dsc*dp*ic*isc*ip*in* btusb
alias usb:v044Ep3002d*dc*dsc*dp*ic*isc*ip*in* btusb
alias usb:v0489p*d*dc*dsc*dp*icFFisc01ip01in* btusb
alias usb:v04BFp030Ad*dc*dsc*dp*ic*isc*ip*in* btusb
alias usb:v04CAp*d*dc*dsc*dp*icFFisc01ip01in* btusb
alias usb:v050Dp*d*dc*dsc*dp*icFFisc01ip01in* btusb
alias usb:v057Cp3800d*dc*dsc*dp*ic*isc*ip*in* btusb
alias usb:v05ACp*d*dc*dsc*dp*icFFisc01ip01in* btusb
alias usb:v05ACp8213d*dc*dsc*dp*ic*isc*ip*in* btusb
alias usb:v05ACp8215d*dc*dsc*dp*ic*isc*ip*in* btusb
alias usb:v05ACp8218d*dc*dsc*dp*ic*isc*ip*in* btusb
alias usb:v05ACp821Ad*dc*dsc*dp*ic*isc*ip*in* btusb
alias usb:v05ACp821Bd*dc*dsc*dp*ic*isc*ip*in* btusb
alias usb:v05ACp821Fd*dc*dsc*dp*ic*isc*ip*in* btusb
alias usb:v05ACp8281d*dc*dsc*dp*ic*isc*ip*in* btusb
alias usb:v0930p*d*dc*dsc*dp*icFFisc01ip01in* btusb
alias usb:v0A5Cp*d*dc*dsc*dp*icFFisc01ip01in* btusb
alias usb:v0A5Cp21E1d*dc*dsc*dp*ic*isc*ip*in* btusb
alias usb:v0B05p*d*dc*dsc*dp*icFFisc01ip01in* btusb
alias usb:v0BB4p*d*dc*dsc*dp*icFFisc01ip01in* btusb
alias usb:v0BDBp1002d*dc*dsc*dp*ic*isc*ip*in* btusb
alias usb:v0C10p0000d*dc*dsc*dp*ic*isc*ip*in* btusb
alias usb:v0E8Dp763Fd*dc*dsc*dp*ic*isc*ip*in* btusb
alias usb:v105Bp*d*dc*dsc*dp*icFFisc01ip01in* btusb
alias usb:v13D3p*d*dc*dsc*dp*icFFisc01ip01in* btusb
alias usb:v19FFp0239d*dc*dsc*dp*ic*isc*ip*in* btusb
alias usb:v413Cp*d*dc*dsc*dp*icFFisc01ip01in* btusb
alias usb:v8087p0A5Ad*dc*dsc*dp*ic*isc*ip*in* btusb

 ╭─johnny@johnny in ~ took 22s
 ╰─λ modprobe --show-depends btusb
insmod /lib/modules/6.5.9-zen2-1-zen/kernel/lib/crc16.ko.zst 
insmod /lib/modules/6.5.9-zen2-1-zen/kernel/net/rfkill/rfkill.ko.zst 
insmod /lib/modules/6.5.9-zen2-1-zen/kernel/crypto/ecdh_generic.ko.zst 
insmod /lib/modules/6.5.9-zen2-1-zen/kernel/net/bluetooth/bluetooth.ko.zst 
insmod /lib/modules/6.5.9-zen2-1-zen/kernel/drivers/bluetooth/btmtk.ko.zst 
insmod /lib/modules/6.5.9-zen2-1-zen/kernel/drivers/bluetooth/btintel.ko.zst 
insmod /lib/modules/6.5.9-zen2-1-zen/kernel/drivers/bluetooth/btbcm.ko.zst 
insmod /lib/modules/6.5.9-zen2-1-zen/kernel/drivers/bluetooth/btrtl.ko.zst 
insmod /lib/modules/6.5.9-zen2-1-zen/kernel/drivers/bluetooth/btusb.ko.zst reset=1 

 ╭─johnny@johnny in ~ took 12s
 ╰─λ modinfo btusb
filename:       /lib/modules/6.5.9-zen2-1-zen/kernel/drivers/bluetooth/btusb.ko.zst
license:        GPL
version:        0.8
description:    Generic Bluetooth USB driver ver 0.8
author:         Marcel Holtmann <[email protected]>
srcversion:     67C9DE037CE6B9213EFED7A
alias:          usb:v8087p0A5Ad*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0930p*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v413Cp*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v13D3p*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v050Dp*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v0B05p*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v0A5Cp*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v04CAp*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v0489p*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v0BB4p*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v105Bp*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v19FFp0239d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0C10p0000d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0BDBp1002d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v044Ep3002d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v044Ep3001d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v04BFp030Ad*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v057Cp3800d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v05ACp8281d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v05ACp821Ad*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v05ACp821Fd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v05ACp821Bd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v05ACp8218d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v05ACp8215d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v05ACp8213d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0A5Cp21E1d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0E8Dp763Fd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v05ACp*d*dc*dsc*dp*icFFisc01ip01in*
alias:          usb:v*p*d*dc*dsc*dp*icE0isc01ip01in*
alias:          usb:v*p*d*dcE0dsc01dp04ic*isc*ip*in*
alias:          usb:v*p*d*dcE0dsc01dp01ic*isc*ip*in*
alias:          of:N*T*Cusb4ca,301aC*
alias:          of:N*T*Cusb4ca,301a
alias:          of:N*T*Cusbcf3,e300C*
alias:          of:N*T*Cusbcf3,e300
alias:          of:N*T*Cusb1286,204eC*
alias:          of:N*T*Cusb1286,204e
depends:        bluetooth,btmtk,btrtl,btintel,btbcm
retpoline:      Y
intree:         Y
name:           btusb
vermagic:       6.5.9-zen2-1-zen SMP preempt mod_unload 
sig_id:         PKCS#7
signer:         Build time autogenerated kernel key
sig_key:        40:C8:77:40:AF:87:8D:A4:AE:0A:91:1C:9A:5D:A0:62:EF:12:F3:28
sig_hashalgo:   sha512
signature:      30:65:02:30:33:F9:0A:33:9B:78:DD:8C:BC:A8:30:B9:0A:DA:A2:70:
		F4:99:C8:D4:09:BD:7E:1B:85:0A:8A:B3:13:20:9B:C6:85:1E:F2:12:
		81:BB:71:28:8D:D7:B2:63:4A:5D:6A:CC:02:31:00:FC:E6:FC:10:B9:
		CD:85:C8:89:82:63:C2:0C:4D:FF:29:D0:1D:1A:63:EA:C1:96:B2:E2:
		5B:D9:25:42:6E:0E:CE:29:E7:D8:F4:6E:31:4D:93:67:62:B5:BF:9A:
		D8:9B:FA
parm:           disable_scofix:Disable fixup of wrong SCO buffer size (bool)
parm:           force_scofix:Force fixup of wrong SCO buffers size (bool)
parm:           enable_autosuspend:Enable USB autosuspend by default (bool)
parm:           reset:Send HCI reset command on initialization (bool)

 ╭─johnny@johnny in ~ took 1m3s
 ╰─λ lspci | grep -i network
3d:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32)

 ╭─johnny@johnny in ~ took 2m48s
 ╰─λ systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Sat 2023-11-04 09:51:13 -03; 16min ago
       Docs: man:bluetoothd(8)
   Main PID: 973 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18668)
     Memory: 3.3M
        CPU: 41ms
     CGroup: /system.slice/bluetooth.service
             └─973 /usr/lib/bluetooth/bluetoothd

nov 04 09:51:13 johnny-g55590 bluetoothd[973]: Starting SDP server
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: src/plugin.c:plugin_init() System does not support csip plugin
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: src/plugin.c:plugin_init() System does not support micp plugin
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: src/plugin.c:plugin_init() System does not support vcp plugin
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: src/plugin.c:plugin_init() System does not support mcp plugin
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: src/plugin.c:plugin_init() System does not support bass plugin
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: src/plugin.c:plugin_init() System does not support bap plugin
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: Bluetooth management interface 1.22 initialized
nov 04 09:51:13 johnny-g55590 systemd[1]: Started Bluetooth service.

 ╭─johnny@johnny in ~ took 43s
 ╰─λ journalctl -b | grep -i blue
nov 04 09:51:09 johnny-g55590 kernel: Bluetooth: Core ver 2.22
nov 04 09:51:09 johnny-g55590 kernel: NET: Registered PF_BLUETOOTH protocol family
nov 04 09:51:09 johnny-g55590 kernel: Bluetooth: HCI device and connection manager initialized
nov 04 09:51:09 johnny-g55590 kernel: Bluetooth: HCI socket layer initialized
nov 04 09:51:09 johnny-g55590 kernel: Bluetooth: L2CAP socket layer initialized
nov 04 09:51:09 johnny-g55590 kernel: Bluetooth: SCO socket layer initialized
nov 04 09:51:09 johnny-g55590 kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
nov 04 09:51:11 johnny-g55590 kernel: Bluetooth: hci0: Opcode 0x c03 failed: -110
nov 04 09:51:13 johnny-g55590 systemd[1]: Starting Bluetooth service...
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: Bluetooth daemon 5.70
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: Starting SDP server
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: src/plugin.c:plugin_init() System does not support csip plugin
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: src/plugin.c:plugin_init() System does not support micp plugin
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: src/plugin.c:plugin_init() System does not support vcp plugin
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: src/plugin.c:plugin_init() System does not support mcp plugin
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: src/plugin.c:plugin_init() System does not support bass plugin
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: src/plugin.c:plugin_init() System does not support bap plugin
nov 04 09:51:13 johnny-g55590 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
nov 04 09:51:13 johnny-g55590 kernel: Bluetooth: BNEP filters: protocol multicast
nov 04 09:51:13 johnny-g55590 kernel: Bluetooth: BNEP socket layer initialized
nov 04 09:51:13 johnny-g55590 bluetoothd[973]: Bluetooth management interface 1.22 initialized
nov 04 09:51:13 johnny-g55590 dbus-daemon[974]: [system] Activating systemd to hand-off: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.3' (uid=0 pid=973 comm="/usr/lib/bluetooth/bluetoothd")
nov 04 09:51:13 johnny-g55590 systemd[1]: Started Bluetooth service.
nov 04 09:51:13 johnny-g55590 systemd[1]: Reached target Bluetooth Support.
nov 04 09:51:13 johnny-g55590 NetworkManager[1026]: <info>  [1699102273.9917] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.44.2-3/libnm-device-plugin-bluetooth.so)
nov 04 09:51:18 johnny-g55590 dbus-daemon[2552]: [session uid=1000 pid=2552] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.11' (uid=1000 pid=2771 comm="/usr/bin/kded5")
nov 04 09:51:18 johnny-g55590 systemd[2530]: Starting Bluetooth OBEX service...
nov 04 09:51:18 johnny-g55590 dbus-daemon[2552]: [session uid=1000 pid=2552] Successfully activated service 'org.bluez.obex'
nov 04 09:51:18 johnny-g55590 systemd[2530]: Started Bluetooth OBEX service.
nov 04 10:02:17 johnny-g55590 plasmashell[5465]: [5460:5460:1104/100217.220245:ERROR:device_event_log_impl.cc(225)] [10:02:17.220] Bluetooth: bluetooth_adapter_bluez.cc:1199 Failed to enable LL Privacy: org.freedesktop.DBus.Error.UnknownObject: Method "SetLLPrivacy" with signature "b" on interface "org.chromium.Bluetooth.Debug" doesn't exist
nov 04 10:43:58 johnny-g55590 systemd[1]: Stopped target Bluetooth Support.
nov 04 10:44:02 johnny-g55590 kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
nov 04 10:44:02 johnny-g55590 systemd[2530]: Reached target Bluetooth.
nov 04 10:44:02 johnny-g55590 systemd[1]: Reached target Bluetooth Support.
nov 04 10:44:04 johnny-g55590 kernel: Bluetooth: hci0: command 0x1003 tx timeout
nov 04 10:44:04 johnny-g55590 kernel: Bluetooth: hci0: Opcode 0x1003 failed: -110
nov 04 10:44:20 johnny-g55590 systemd[2530]: Stopped target Bluetooth.
nov 04 10:44:20 johnny-g55590 systemd[1]: Stopped target Bluetooth Support.
nov 04 10:44:23 johnny-g55590 kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
nov 04 10:44:23 johnny-g55590 systemd[1]: Reached target Bluetooth Support.
nov 04 10:44:23 johnny-g55590 systemd[2530]: Reached target Bluetooth.
nov 04 10:44:23 johnny-g55590 kernel: Bluetooth: hci0: unexpected event for opcode 0x0c03
nov 04 10:44:23 johnny-g55590 kernel: Bluetooth: hci0: unexpected event for opcode 0x1003
nov 04 10:44:23 johnny-g55590 kernel: Bluetooth: MGMT ver 1.22
nov 04 10:44:23 johnny-g55590 kernel: Bluetooth: RFCOMM TTY layer initialized
nov 04 10:44:23 johnny-g55590 kernel: Bluetooth: RFCOMM socket layer initialized
nov 04 10:44:23 johnny-g55590 kernel: Bluetooth: RFCOMM ver 1.11
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/ldac
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/aptx_hd
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_hd
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/aptx
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/aac
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aac
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/sbc
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/sbc
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/sbc_xq
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/sbc_xq
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_ll_1
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_ll_0
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/faststream
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/faststream_duplex
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/opus_05
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/opus_05
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/opus_05_duplex
nov 04 10:44:23 johnny-g55590 bluetoothd[973]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/opus_05_duplex

journalctl marks the point at 10:44 where I manually removed && re-added btusb on modprobe. Because I was testing bluetoothctl list:

 ╭─johnny@johnny in ~ took 34m2s
 ╰─λ bluetoothctl list

 ╭─johnny@johnny in ~ as 🧙 took 1s
 ╰─λ sudo modprobe -r btusb

 ╭─johnny@johnny in ~ as 🧙 took 16s
 ╰─λ sudo modprobe btusb

 ╭─johnny@johnny in ~ as 🧙 took 2s
 ╰─λ bluetoothctl list
Controller A8:93:4A:34:60:EE johnny-g55590 [default]

Scan works…

 ╭─johnny@johnny in ~ as 🧙 took 4m55s
[🔴] × bluetoothctl scan bredr
Discovery started
[CHG] Controller A8:93:4A:34:60:EE Discovering: yes
[NEW] Device D8:08:31:16:59:27 Tab S6
[CHG] Device D8:08:31:16:59:27 RSSI: 0xffffffa0 (-96)
[CHG] Device D8:08:31:16:59:27 RSSI: 0xffffffda (-38)
[CHG] Device D8:08:31:16:59:27 UUIDs: 00001105-0000-1000-8000-00805f9b34fb
[CHG] Device D8:08:31:16:59:27 UUIDs: 0000110a-0000-1000-8000-00805f9b34fb
[CHG] Device D8:08:31:16:59:27 UUIDs: 0000110c-0000-1000-8000-00805f9b34fb
[CHG] Device D8:08:31:16:59:27 UUIDs: 0000110e-0000-1000-8000-00805f9b34fb
[CHG] Device D8:08:31:16:59:27 UUIDs: 00001112-0000-1000-8000-00805f9b34fb
[CHG] Device D8:08:31:16:59:27 UUIDs: 00001115-0000-1000-8000-00805f9b34fb
[CHG] Device D8:08:31:16:59:27 UUIDs: 00001116-0000-1000-8000-00805f9b34fb
[CHG] Device D8:08:31:16:59:27 UUIDs: 0000111f-0000-1000-8000-00805f9b34fb
[CHG] Device D8:08:31:16:59:27 UUIDs: 0000112f-0000-1000-8000-00805f9b34fb
[CHG] Device D8:08:31:16:59:27 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device D8:08:31:16:59:27 UUIDs: 00001132-0000-1000-8000-00805f9b34fb
[CHG] Device D8:08:31:16:59:27 UUIDs: a82efa21-ae5c-3dde-9bbc-f16da7b16c5a
[CHG] Device D8:08:31:16:59:27 UUIDs: 931c7e8a-540f-4686-b798-e8df0a2ad9f7
[CHG] Device D8:08:31:16:59:27 RSSI: 0xffffff9f (-97)
[CHG] Device D8:08:31:16:59:27 RSSI: 0xffffffd4 (-44)

Using bluetoothctl:

[bluetooth]# show
Controller A8:93:4A:34:60:EE (public)
	Name: johnny-g55590
	Alias: johnny-g55590
	Class: 0x007c010c (8126732)
	Powered: yes
	Discoverable: no
	DiscoverableTimeout: 0x000000b4 (180)
	Pairable: yes
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
	UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
	UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
	UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
	UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
	UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0546
	Discovering: no
	Roles: central
	Roles: peripheral

[bluetooth]# pair D8:08:31:16:59:27
Attempting to pair with D8:08:31:16:59:27
Request confirmation
[agent] Confirm passkey 945768 (yes/no): yes
Failed to pair: org.bluez.Error.AuthenticationFailed

but then, a bit after, I get the device prompt… then I lose it. The I get it again. It’s unstable as hell.

[Tab S6]#
[bluetooth]#
[Tab S6]#
hci0 new_settings: powered connectable bondable ssp br/edr secure-conn

But on my Tab S6, the info is that it wasn’t possible to pair and I should check the configurations in my device and try again.

and then…

[CHG] Device D8:08:31:16:59:27 Connected: no
[CHG] Device D8:08:31:16:59:27 Connected: yes
[CHG] Device D8:08:31:16:59:27 Connected: no
[CHG] Device D8:08:31:16:59:27 Connected: yes
hci0 new_settings: powered connectable bondable ssp br/edr secure-conn 
[CHG] Controller A8:93:4A:34:60:EE Discoverable: no
[CHG] Device D8:08:31:16:59:27 Connected: no
[CHG] Device D8:08:31:16:59:27 Connected: yes
[DEL] Device D8:08:31:16:59:27 Tab S6
[NEW] Device D8:08:31:16:59:27 Tab S6

But on my tablet, it’s all the same. Bluetoothctl keeps showing that last in a loop. I then tried the connect command… and told my tablet to pair again. This time, the pin confirmation came not on the terminal, but on KDE’s interface. I confirmed. These showed up in terminal:

[Tab S6]# connect D8:08:31:16:59:27
Attempting to connect to D8:08:31:16:59:27
[CHG] Device D8:08:31:16:59:27 Bonded: yes
[CHG] Device D8:08:31:16:59:27 ServicesResolved: yes
[CHG] Device D8:08:31:16:59:27 Paired: yes
Failed to connect: org.bluez.Error.Failed br-connection-timeout
[Tab S6]# 

While the tablet too a long time, but now says it’s paired. Bluetooth interface agrees…

image

tried sending a file from the Tablet and… failure. Nothing shows up on the computer. From the computer to the Tab it also fails =(

Now the ctl shows a connection drop

[CHG] Device D8:08:31:16:59:27 RSSI: 0xffffffd0 (-48)
[CHG] Device D8:08:31:16:59:27 RSSI: 0xffffffd8 (-40)
[CHG] Device D8:08:31:16:59:27 ServicesResolved: no
[CHG] Device D8:08:31:16:59:27 Connected: no
[CHG] Device D8:08:31:16:59:27 RSSI: 0xffffffcc (-52)
[bluetooth]# 

no idea what else to try except for cracking this thing open, and checking the physical connection. Bad part is, if it is a replacement issue, I’ll have to get on Windows anyway to collect evidences for Dell support to replace it (yey warranty)

I too did a lsmod on my system and surprisingly I don’t have this module. Looking online

CRC is a way of detecting accidental changes in data storage or transmission. There are many variants of CRC and CRC16, in particular. This library calculates only CRC16 (16-bit codes) and the only supported variant at the moment is CRC-CCITT (XModem).

So this might be wishful thinking but might this be the reason of your issue? Only one way to find out,

sudo modprobe -r crc16

and check if anything at all changes?

Your BT adapter is an Atheros model, installing the Broadcom BT firmware will definitely not help, and may even prove counterproductive. I would highly suggest uninstalling the broadcom-bt-firmware-git package if you haven’t done so already.

Be sure all power saving options for both your wifi & BT are disabled in Linux (and Windows if installed).

At this point you may want to backup your bios settings, and then perform a full bios reset to the original factory settings.

You may also want to install fwupd and make sure your firmware is up to date.

Checking that your Wifi/BT hardware is installed properly in its socket and that all connections are secure is a good idea as well.

3 Likes

I’d wager that module had something to do with verifying integrity of data trafficked through Bluetooth, since CRC is the grandparent of hashes like SHA256

Did so already, right after the failed attempt.

No windows installed, and unless Garuda Congress with any power saving configuration, I didn’t mess with any.

Did that before starting everything, all up to date. Can’t copy paste from the computer right now because it’s all weirdly lagging the GUI. Like huge. Mouse movement is fine, but everything else down to keyboard strokes take a few seconds to register and happen.

Already tried rebooting to no success, alternate terminals f3 and F4 working without any lagging, though… CPU and GPU usage is normal, all temps under 45ºC

alright, new fresh install, everything is nice and smooth.

╭─johnny@johnny in ~ as 🧙 took 16ms
╰─λ sudo fwupdmgr update
Dispositivos com nenhuma atualização de firmware disponível:
• Internal SPI Controller
• PC SN520 NVMe WDC 256GB
• System Firmware
• TPM
• Thunderbolt host controller
• UEFI dbx
• WDC WD10SPZX-75Z10T3
No updatable devices

Not sure if that’s a good idea at this time, factory reset would probably reenable secure boot and other windows OEM shenanigans?

And then I just noticed that no wifi networks are being listed here… something similar happened a long time ago, and it was my wifi+bluetooth adapter that was dead and I had to have Dell replace it.
Problem is, they usually want Windows evidence before allowing the replacement. Crap.

Perhaps you may try with some Windows PE live disk for the evidence?

1 Like

Perhaps I could. But right after posting that I was chatting online with Dell support and their technician is coming here tomorrow morning with a new motherboard and wifi+bluetooth chip for testing and replacement if necessary. They think there could be a problem with the motherboard since it’s the 3rd or 4th time I need to replace the wifi+bluetooth chip O.o despite everything else running ok.

So now I wait around 14h to get this done and come back with news =p

1 Like

“Fastboot” or “fast startup” are typical culprits, both in the BIOS and within Windows. In the BIOS it is sometimes disguised as “Hardware Detection” which needs to be set to ‘Full’ or whatever corresponds.

In Windows, ensure the following is set, thusly:

image

Windows loves to ‘capture’ peripheral hardware.
:frowning:

1 Like

even if there is no Windows installed? I don’t have dual boot, and the drive where it is installed was formatted when I put Garuda, more than 6 months ago. During most of that time, Bluetooth has been working fine.

I don’t remember seeing any “Hardware detection” setting on that weird Dell BIOS

(looks like this:

source: Anleitung zum Zugriff, zur Navigation oder zum Update des BIOS oder UEFI | Dell Deutschland)

I have the same BIOS.

Click the POST Behavior and you will find an option “Fastboot” that regards hardware detection. It needs to be set to “Thorough.”

And unless your Dell came without an OS, it came with Windows. Dell’s BIOS factory setting defaults to “Auto” and that’s no good. Windows knows what it has; Linux does not.

Dell’s Tech Support is worthless when it comes to Linux… They don’t even know the above.

I’ve been through the same, damned thing and I do.

2 Likes

ahhh that one. It already is thorough, but thanks =)

true, the support guy on chat actually tried, their remote support actually works natively on Linux, but sadly he didn’t know what to do =p the technician should be getting here any time now to replace stuff anyway ¯_(ツ)_/¯

1 Like

Other than Linux, I’ve had good support from Dell. Except my 2014 Dell laptop w/touch screen. When the screen hinge broke in less than a year, I found out that Dell explicitly did cover those specific screens. But other than my first two IBM PCs back in the 80s, we’ve always bought Dells and probably always will.

I’ll never forget them talking/walking my secretary through replacing an HDD back in the 90s. Over the phone. She hated computers and wanted nothing to do with them other than pounding their keyboards. I would have said it was an impossibility, but there it was. :wink:

Hey, good luck! :smiley:

2 Likes

Confirmed hardware issue. Bluetooth+Wifi chip was replaced and everything works fine and dandy now =D

although… that’s weird: I got to connect my Echo Dot via bluetooth, but it doesn’t show up among the audio devices?

image

4 Likes

Did they replace your mobo?

This sounds like something is seriously out of whack with your laptop. There’s no way a new premium laptop should be burning through components like that. I would be more than a little concerned for the longevity of my laptop if I’d already had that many warranty replacements.

depends on your definition of new. I think I bought it almost 4 years ago… but yeah, I already used their warranty to replace this wifi+bt chip some 3 or 4 times, and this last one they said that there could be something wrong with my mobo and they’d be replacing it then. So far, so good.

Also, none of the problems I’ve had with it were huge (minor pains in the ass, getting by a few days without BT), so I’m not that much worried?

1 Like