And yes, I checked Archwiki, followed the thread.
I am not sure, but I noticed that when I connect my bluetooth headphones or even turn on bluetooth on my laptop, wifi network went crazy. From no bandwith traffic at all, to slower wifi⦠weird
ā°āĪ» journalctl -b -p3 --no-hostname --no-pager
-- Journal begins at Fri 2020-12-11 20:53:46 CET, ends at Wed 2020-12-16 21:31:15 CET. --
pro 16 18:13:57 kernel: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
pro 16 18:13:58 systemd-udevd[330]: nvme0: /etc/udev/rules.d/60-ioschedulers.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.7/0000:03:00.0/nvme/nvme0/queue/scheduler}, ignoring: No such file or directory
pro 16 18:13:58 kernel: lis3lv02d: unknown sensor type 0x0
pro 16 18:13:58 systemd-udevd[346]: nvme0n1p3: /etc/udev/rules.d/60-ioschedulers.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.7/0000:03:00.0/nvme/nvme0/nvme0n1/nvme0n1p3/queue/scheduler}, ignoring: No such file or directory
pro 16 18:13:58 systemd-udevd[357]: nvme0n1p1: /etc/udev/rules.d/60-ioschedulers.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.7/0000:03:00.0/nvme/nvme0/nvme0n1/nvme0n1p1/queue/scheduler}, ignoring: No such file or directory
pro 16 18:13:58 systemd-udevd[360]: nvme0n1p2: /etc/udev/rules.d/60-ioschedulers.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.7/0000:03:00.0/nvme/nvme0/nvme0n1/nvme0n1p2/queue/scheduler}, ignoring: No such file or directory
pro 16 18:13:58 kernel: snd_pci_acp3x 0000:04:00.5: Invalid ACP audio mode : 1
pro 16 18:13:58 kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xd7d09000-0xd7d09fff flags 0x200] vs d7d09000 4000
pro 16 18:13:58 kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xd7d0d000-0xd7d0dfff flags 0x200] vs d7d0d000 4000
pro 16 18:13:58 kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
pro 16 18:13:58 systemd-udevd[350]: nvme0n1p1: /etc/udev/rules.d/60-ioschedulers.rules:2 Failed to write ATTR{/sys/devices/pci0000:00/0000:00:01.7/0000:03:00.0/nvme/nvme0/nvme0n1/nvme0n1p1/queue/scheduler}, ignoring: No such file or directory
pro 16 18:13:58 kernel: Error: Driver 'rtw_8822be' is already registered, aborting...
pro 16 18:13:58 kernel: kvm: disabled by bios
pro 16 18:13:58 kernel: kvm: disabled by bios
pro 16 18:13:58 systemd-tmpfiles[457]: Failed to write file "/sys/module/pcie_aspm/parameters/policy": Operation not permitted
pro 16 18:13:58 kernel: kvm: disabled by bios
pro 16 18:13:58 kernel: kvm: disabled by bios
pro 16 18:13:58 kernel: kvm: disabled by bios
pro 16 18:13:58 kernel: kvm: disabled by bios
pro 16 18:13:58 kernel: kvm: disabled by bios
pro 16 18:13:58 kernel: kvm: disabled by bios
pro 16 18:13:59 bluetoothd[480]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 00:16:94:41:F2:47: Protocol not available
pro 16 18:17:18 bluetoothd[480]: src/profile.c:record_cb() Unable to get Headset Voice gateway SDP record: Host is down
pro 16 20:44:36 kernel: Bluetooth: hci0: HCI reset during shutdown failed
pro 16 20:44:36 bluetoothd[480]: src/profile.c:ext_io_disconnected() Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
pro 16 21:29:57 kernel: debugfs: File 'force_bredr_smp' in directory 'hci0' already present!
pro 16 21:30:28 bluetoothd[480]: src/profile.c:ext_connect() Unable to get connect data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
āāmarko at marko-hpenvyx360convertible13ar0xxx in ā
ā°āĪ» journalctl -b --no-hostname --no-pager | grep -iwE "bt|bluetooth"
pro 16 18:13:58 kernel: usb 3-2: Product: Bluetooth Radio
pro 16 18:13:58 kernel: Bluetooth: Core ver 2.22
pro 16 18:13:58 kernel: Bluetooth: HCI device and connection manager initialized
pro 16 18:13:58 kernel: Bluetooth: HCI socket layer initialized
pro 16 18:13:58 kernel: Bluetooth: L2CAP socket layer initialized
pro 16 18:13:58 kernel: Bluetooth: SCO socket layer initialized
pro 16 18:13:58 kernel: Bluetooth: hci0: RTL: examining hci_ver=07 hci_rev=000b lmp_ver=07 lmp_subver=8822
pro 16 18:13:58 kernel: Bluetooth: hci0: RTL: rom_version status=0 version=2
pro 16 18:13:58 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_fw.bin
pro 16 18:13:58 kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8822b_config.bin
pro 16 18:13:58 kernel: Bluetooth: hci0: RTL: cfg_sz 14, total sz 20270
pro 16 18:13:58 systemd[1]: Started Bluetooth autoconnect service.
pro 16 18:13:58 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth-autoconnect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
pro 16 18:13:58 systemd[1]: Starting Bluetooth service...
pro 16 18:13:58 bluetoothd[480]: Bluetooth daemon 5.55
pro 16 18:13:58 systemd[1]: Started Bluetooth service.
pro 16 18:13:58 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
pro 16 18:13:58 systemd[1]: Reached target Bluetooth.
pro 16 18:13:58 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
pro 16 18:13:58 kernel: Bluetooth: BNEP filters: protocol multicast
pro 16 18:13:58 kernel: Bluetooth: BNEP socket layer initialized
pro 16 18:13:58 bluetoothd[480]: Bluetooth management interface 1.18 initialized
pro 16 18:13:59 NetworkManager[483]: <info> [1608138839.1075] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.26.4-1/libnm-device-plugin-bluetooth.so)
pro 16 18:13:59 kernel: Bluetooth: hci0: RTL: fw version 0xab6b705c
pro 16 18:13:59 bluetooth-autoconnect[479]: connecting to device /org/bluez/hci0/dev_00_16_94_41_F2_47
pro 16 18:13:59 bluetooth-autoconnect[479]: error connecting to device /org/bluez/hci0/dev_00_16_94_41_F2_47: Protocol not available
pro 16 18:17:12 systemd[2351]: Starting Bluetooth OBEX service...
pro 16 18:17:12 kded5[2671]: bluedevil: Bluetooth operational changed true
pro 16 18:17:12 systemd[2351]: Started Bluetooth OBEX service.
pro 16 18:17:12 kernel: Bluetooth: RFCOMM TTY layer initialized
pro 16 18:17:12 kernel: Bluetooth: RFCOMM socket layer initialized
pro 16 18:17:12 kernel: Bluetooth: RFCOMM ver 1.11
pro 16 18:17:12 systemd[2351]: Started Bluetooth autoconnect service for pulseaudio.
pro 16 18:17:13 bluetooth-autoconnect[2843]: connecting to device /org/bluez/hci0/dev_00_16_94_41_F2_47
pro 16 18:17:13 systemd[1]: Starting Bluetooth management mechanism...
pro 16 18:17:13 systemd[1]: Started Bluetooth management mechanism.
pro 16 18:17:18 bluetooth-autoconnect[2843]: error connecting to device /org/bluez/hci0/dev_00_16_94_41_F2_47: Host is down
pro 16 18:17:18 systemd[2351]: pulseaudio-bluetooth-autoconnect.service: Succeeded.
pro 16 20:28:18 systemd[2351]: Reached target Bluetooth.
pro 16 20:44:36 dbus-daemon[482]: [system] Rejected send message, 0 matched rules; type="method_return", sender=":1.41" (uid=1000 pid=2767 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.1" (uid=0 pid=480 comm="/usr/lib/bluetooth/bluetoothd ")
pro 16 20:44:36 kernel: Bluetooth: hci0: HCI reset during shutdown failed
pro 16 21:29:57 systemd[1]: Starting Bluetooth management mechanism...
pro 16 21:29:57 systemd[1]: Started Bluetooth management mechanism.
pro 16 21:29:57 bluetooth-autoconnect[479]: connecting to device /org/bluez/hci0/dev_00_16_94_41_F2_47
pro 16 21:30:22 bluetooth-autoconnect[479]: error connecting to device /org/bluez/hci0/dev_00_16_94_41_F2_47: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
In bluetooth headset wiki, there are several sections about possible issues and what you should do to troubleshoot properly.
Please do your best.
I cannot enter in your office area, yet, but I will try harder.