Bluetooth issues after sleep (loose my adapter)

connordillon96 · 1 November 2020 21:53

Of course

    [connor@StarReach ~]$ lsusb -tv 
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 5: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M
        ID 04f3:0c4b Elan Microelectronics Corp. 
    |__ Port 6: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M
        ID 04ca:7070 Lite-On Technology Corp. 
    |__ Port 6: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M
        ID 04ca:7070 Lite-On Technology Corp. 
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub

The_Quantum_Alpha · 1 November 2020 21:58

I wonder which one of these are the Bluetooth adapter… I assume bus one , as i sort of recognize the vendor…

May you try sudo usb_modeswitch -R -v 1d6b -p 0002 , please?

connordillon96 · 1 November 2020 22:00

You would know better than me

[connor@StarReach ~]$ sudo usb_modeswitch -R -v 1d6b -p 0002
Look for default devices ...
 Found devices in default mode (2)
Access device 001 on bus 001
Get the current device configuration ...
Current configuration number is 1
Use interface number 0
 with class 9
Warning: no switching method given. See documentation
Reset USB device ...........Reset USB device failed with error -99 Reset USB device failed with error -99-> Run lsusb to note any changes. Bye!

[connor@StarReach ~]$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera
Bus 003 Device 003: ID 04f3:0c4b Elan Microelectronics Corp. ELAN:Fingerprint
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[connor@StarReach ~]$

The_Quantum_Alpha · 1 November 2020 22:01

Kernel 5.9, may I ask?

connordillon96 · 1 November 2020 22:04

I am running

Linux StarReach 5.9.1-1-MANJARO #1 SMP PREEMPT Sat Oct 17 11:44:44 UTC 2020 x86_64 GNU/Linux

The_Quantum_Alpha · 1 November 2020 22:09

Oh, indeed, the kernel 5.9 Bluetooth stack tries to use link-layer privacy on BLE connections…

Please try to run sudo rfkill unblock bluetooth , see if it works…

Else, enter sudo -i in the terminal , then enter cd /var/lib/bluetooth/ , then provide me the output of ls, please!

connordillon96 · 1 November 2020 22:12

rfkill unblock bluetooth Never did anything
The command just reports the one

94:E7:0B:C9:8D:7A

Thanks for the help btw

The_Quantum_Alpha · 1 November 2020 22:13

Sweet! still in the terminal, may now enter cd /var/lib/bluetooth/94:E7:0B:C9:8D:7A, then provide me once again the output of ls!

connordillon96 · 1 November 2020 22:15

It returns:

cache FB:2C:98:B7:B4:3C settings

The_Quantum_Alpha · 1 November 2020 22:23

Great! Now, once again still in the terminal, enter nano /var/lib/bluetooth/94:E7:0B:C9:8D:7A/FB:2C:98:B7:B4:3C/info , then remove the lines that looks like this:

[IdentityResolvingKey]
Key=...

After that, press ctrl + s to save, then ctrl + x to exit.

Then enter nano /etc/bluetooth/main.conf and set:

[Policy]
AutoEnable=true

After that, press ctrl + s to save, then ctrl + x to exit. Then you may type in exit to exit from sudo.

Then, you may execute pulseaudio --k , followed by sudo systemctl restart bluetooth.service to then execute pulseaudio --start.

cscs · 1 November 2020 22:26

This wont work … it needs sudo.
But really should use sudoedit … and I assume the env var is not set (or set to vi), so to be sure:

SUDO_EDITOR=nano sudoedit /var/lib/bluetooth/94:E7:0B:C9:8D:7A/FB:2C:98:B7:B4:3C/info

The_Quantum_Alpha · 1 November 2020 22:27

He is still in the su environment!

connordillon96 · 1 November 2020 22:28

I ran through it all with adapter is still MIA, one command seemed not to work though.

    [connor@StarReach 94:E7:0B:C9:8D:7A]$ pulseaudio --k  
    E: [pulseaudio] main.c: Failed to kill daemon: No such process

The_Quantum_Alpha · 1 November 2020 22:29

Oh, you need to exit from sudo!

connordillon96 · 1 November 2020 22:31

ah!
All commands went through no issues, adapter is still missing

The_Quantum_Alpha · 1 November 2020 22:34

May I please ask what sudo lsmod | grep bluetooth returns, as well as sudo dmesg | grep Bluetooth and sudo rfkill list plus mkinitcpio -M ?

connordillon96 · 1 November 2020 22:37

sudo lsmod | grep bluetooth returns:

sudo dmesg | grep Bluetooth returns:

[connor@StarReach ~]$ sudo dmesg | grep Bluetooth
[    3.301974] Bluetooth: Core ver 2.22
[    3.301990] Bluetooth: HCI device and connection manager initialized
[    3.301992] Bluetooth: HCI socket layer initialized
[    3.301993] Bluetooth: L2CAP socket layer initialized
[    3.301995] Bluetooth: SCO socket layer initialized
[    3.310509] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 11 2017
[    3.311535] Bluetooth: hci0: Device revision is 2
[    3.311536] Bluetooth: hci0: Secure boot is enabled
[    3.311536] Bluetooth: hci0: OTP lock is enabled
[    3.311537] Bluetooth: hci0: API lock is enabled
[    3.311537] Bluetooth: hci0: Debug lock is disabled
[    3.311538] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    3.313791] Bluetooth: hci0: Found device firmware: intel/ibt-19-32-4.sfi
[    3.330428] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    3.330429] Bluetooth: BNEP filters: protocol multicast
[    3.330431] Bluetooth: BNEP socket layer initialized
[    4.935636] Bluetooth: hci0: Waiting for firmware download to complete
[    4.936632] Bluetooth: hci0: Firmware loaded in 1588304 usecs
[    4.936643] Bluetooth: hci0: Waiting for device to boot
[    4.951587] Bluetooth: hci0: Device booted in 14600 usecs
[    4.951810] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-32-4.ddc
[    4.953675] Bluetooth: hci0: Applying Intel DDC parameters completed
[    4.956690] Bluetooth: hci0: Firmware revision 0.0 build 121 week 36 2020
[   14.743868] Bluetooth: RFCOMM TTY layer initialized
[   14.743874] Bluetooth: RFCOMM socket layer initialized
[   14.743878] Bluetooth: RFCOMM ver 1.11
[   68.008772] Bluetooth: hci0: Timed out waiting for suspend events
[   68.008774] Bluetooth: hci0: command 0x0c05 tx timeout
[   68.008777] Bluetooth: hci0: Suspend timeout bit: 5
[   68.008780] Bluetooth: hci0: Suspend notifier action (4) failed: -110
[connor@StarReach ~]$

and finally:

==> Modules autodetected
8250_dw
ac
acpi_cpufreq
acpi_tad
aesni_intel
atkbd
battery
coretemp
crc32c_intel
crc32_pclmul
crct10dif_pclmul
ee1004
elan_i2c
evdev
ext4
fjes
ghash_clmulni_intel
hid_generic
hid_logitech_dj
hid_logitech_hidpp
i2c_designware_platform
i2c_hid
i2c_i801
i8042
i915
ideapad_laptop
idma64
input_leds
int3400_thermal
int3403_thermal
intel_cstate
intel_lpss_pci
intel_powerclamp
intel_rapl_common
intel_rapl_msr
intel_spi_pci
intel_uncore
intel_wmi_thunderbolt
iTCO_wdt
iwlwifi
joydev
kvm_intel
mac_hid
mei_hdcp
mei_me
mousedev
pcc_cpufreq
pcspkr
processor_thermal_device
r8169
rapl
rtc_cmos
rtsx_pci
rtsx_pci_sdmmc
serio_raw
snd_hda_codec_hdmi
snd_hda_codec_realtek
snd_hda_intel
snd_sof_pci
tpm_crb
tpm_tis
ucsi_acpi
usbhid
uvcvideo
wmi
wmi_bmof
x86_pkg_temp_thermal
xhci_pci

The_Quantum_Alpha · 1 November 2020 22:49

Hmm, have TLP installed?
Okay lets try with this one… sudo usb_modeswitch -R -v 04f3 -p 0c4b

And for now, lets try to kill bluetooth. Enter sudo systemctl disable bluetooth , then reboot to then re enable it sudo systemctl enable bluetooth … Its a firmware mismatch between two loaders…

connordillon96 · 1 November 2020 22:53

Er I think so.

Ran through it all, but the problem still persists after sleep

Look for default devices ...
 Found devices in default mode (1)
Access device 003 on bus 003
Get the current device configuration ...
Current configuration number is 1
Use interface number 0
 with class 255
Warning: no switching method given. See documentation
Reset USB device .
 Device was reset
-> Run lsusb to note any changes. Bye!

[connor@StarReach ~]$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 04ca:7070 Lite-On Technology Corp. Integrated Camera
Bus 003 Device 003: ID 04f3:0c4b Elan Microelectronics Corp. ELAN:Fingerprint
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The_Quantum_Alpha · 1 November 2020 22:57

Let’s try to sudo systemctl disable tlp

oh, have you restarted, may I ask?