Bluetooth no longer working

Issues & Assistance
1 
❯ inxi -Faz                                                                                                                                                                                                     520 Mbps  ─╯
System:
  Kernel: 5.15.11-230-tkg-bmq x86_64 bits: 64 compiler: gcc v: 11.1.0
    parameters: intel_pstate=passive BOOT_IMAGE=/@/boot/vmlinuz-linux-tkg-bmq
    root=UUID=0971afba-13f1-4f58-9dc9-2efda4002dba rw rootflags=subvol=@
    quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    systemd.unified_cgroup_hierarchy=1 loglevel=3
  Desktop: KDE Plasma 5.23.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
    vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: System76 model: Thelio Major v: thelio-major-r2
    serial: <superuser required> UEFI: System76 v: F4c Z5 date: 06/30/2020
CPU:
  Info: model: AMD Ryzen Threadripper 3960X bits: 64 type: MT MCP arch: Zen 2
    family: 0x17 (23) model-id: 0x31 (49) stepping: 0 microcode: 0x8301025
  Topology: cpus: 1x cores: 24 tpc: 2 threads: 48 smt: enabled cache:
    L1: 1.5 MiB desc: d-24x32 KiB; i-24x32 KiB L2: 12 MiB desc: 24x512 KiB
    L3: 128 MiB desc: 8x16 MiB
  Speed (MHz): avg: 3641 high: 4128 min/max: 2200/4568 boost: enabled
    scaling: driver: acpi-cpufreq governor: performance cores: 1: 4110 2: 3786
    3: 3806 4: 3595 5: 3624 6: 3721 7: 3632 8: 3604 9: 3587 10: 3591 11: 3644
    12: 3581 13: 3593 14: 4128 15: 3374 16: 3595 17: 3591 18: 3589 19: 3581
    20: 3588 21: 3592 22: 3385 23: 3605 24: 3593 25: 3940 26: 3794 27: 3432
    28: 3913 29: 3759 30: 4030 31: 3594 32: 3449 33: 3503 34: 3597 35: 3586
    36: 3586 37: 3592 38: 3596 39: 3598 40: 3582 41: 3599 42: 3591 43: 3593
    44: 3591 45: 3587 46: 3596 47: 3584 48: 3593 bogomips: 364481
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl and seccomp
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional,
    STIBP: conditional, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU106 [GeForce RTX 2060 SUPER] vendor: eVga.com.
    driver: nvidia v: 495.46 alternate: nouveau,nvidia_drm bus-ID: 21:00.0
    chip-ID: 10de:1f06 class-ID: 0300
  Device-2: Logitech BRIO Ultra HD Webcam type: USB
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo bus-ID: 2-1:2
    chip-ID: 046d:085e class-ID: 0300 serial: <filter>
  Device-3: Elgato Systems Cam Link 4K type: USB
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo bus-ID: 2-2:3
    chip-ID: 0fd9:0066 class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org 1.21.1.3 compositor: kwin_x11 driver:
    loaded: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x2160 s-dpi: 162 s-size: 602x341mm (23.7x13.4")
    s-diag: 692mm (27.2")
  Monitor-1: HDMI-0 res: 3840x2160 hz: 60 dpi: 163
    size: 600x340mm (23.6x13.4") diag: 690mm (27.2")
  OpenGL: renderer: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2
    v: 4.6.0 NVIDIA 495.46 direct render: Yes
Audio:
  Device-1: NVIDIA TU106 High Definition Audio vendor: eVga.com.
    driver: snd_hda_intel v: kernel bus-ID: 21:00.1 chip-ID: 10de:10f9
    class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio driver: snd_hda_intel v: kernel
    bus-ID: 23:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Logitech BRIO Ultra HD Webcam type: USB
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo bus-ID: 2-1:2
    chip-ID: 046d:085e class-ID: 0300 serial: <filter>
  Device-4: Elgato Systems Cam Link 4K type: USB
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo bus-ID: 2-2:3
    chip-ID: 0fd9:0066 class-ID: 0102 serial: <filter>
  Device-5: Audio-Technica ATR2100x-USB Microphone type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-1:5 chip-ID: 0909:004d
    class-ID: 0300
  Device-6: C-Media Vanatoo T0 type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 7-2:12 chip-ID: 0d8c:0012
    class-ID: 0300
  Device-7: Giga-Byte USB Audio type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 7-5:5 chip-ID: 0414:a002
    class-ID: 0300
  Sound Server-1: ALSA v: k5.15.11-230-tkg-bmq running: yes
  Sound Server-2: JACK v: 1.9.20 running: no
  Sound Server-3: PulseAudio v: 15.0 running: yes
  Sound Server-4: PipeWire v: 0.3.43 running: yes
Network:
  Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel
    port: 9000 bus-ID: 43:00.0 chip-ID: 8086:1539 class-ID: 0200
  IF: enp67s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 44:00.0
    chip-ID: 8086:2723 class-ID: 0280
  IF: wlo2 state: up mac: <filter>
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 9-5:2 chip-ID: 8087:0029 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: N/A
Drives:
  Local Storage: total: 2.72 TiB used: 414.42 GiB (14.9%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung
    model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 2B2QEXM7 temp: 56.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:1 vendor: Samsung
    model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 2B2QEXM7 temp: 56.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 type: USB vendor: Patriot model: N/A
    size: 922.5 GiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: <filter> rev: PMAP scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 409.68 GiB (44.0%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:5
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 560 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:4
  ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 409.68 GiB (44.0%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:5
  ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 409.68 GiB (44.0%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:5
  ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 409.68 GiB (44.0%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:5
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 50 (default 100)
  ID-1: swap-1 type: zram size: 62.75 GiB used: 2.5 MiB (0.0%)
    priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 16.8 C mobo: N/A gpu: nvidia temp: 56 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 10%
Info:
  Processes: 828 Uptime: 9h 31m wakeups: 0 Memory: 62.75 GiB
  used: 19.6 GiB (31.2%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.1.0 Packages: 2142 pacman: 2134 lib: 577 flatpak: 0 snap: 8
  Shell: Zsh v: 5.8 running-in: konsole inxi: 3.3.11

Bluetooth has stopped working for me (no devices found) and I assume it may be the kernel.

dmesg | grep blue returns no results. Is there a know issue with this kernel and is the recommendation to switch to the LTS kernel. I've not switched kernels in Garuda, so not sure how 'easy' that is.

Thank you!

2

Kernels are scary enough without basic knowledge.

$ sudo pacman -S linux-lts linux-lts-headers

Then reboot and select the LTS kernel to boot into at the GRUB prompt..

Given it's Garuda, you may want to make that -Syu instead of just -S

3 Likes
3

Thanks. I'll do so and report back

2 Likes
4 
❯ inxi -Fad                                                                                                                                                                                                   173.3 Mbps  ─╯
System:
  Host: treytheliomajor Kernel: 5.15.15-1-lts x86_64 bits: 64 compiler: gcc
    v: 11.1.0 parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
    root=UUID=0971afba-13f1-4f58-9dc9-2efda4002dba rw rootflags=subvol=@
    quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    systemd.unified_cgroup_hierarchy=1 loglevel=3
  Desktop: KDE Plasma 5.23.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11
    vt: 1 dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: System76 model: Thelio Major v: thelio-major-r2
    serial: <superuser required> UEFI: System76 v: F4c Z5 date: 06/30/2020
CPU:
  Info: model: AMD Ryzen Threadripper 3960X bits: 64 type: MT MCP arch: Zen 2
    family: 0x17 (23) model-id: 0x31 (49) stepping: 0 microcode: 0x8301025
  Topology: cpus: 1x cores: 24 tpc: 2 threads: 48 smt: enabled cache:
    L1: 1.5 MiB desc: d-24x32 KiB; i-24x32 KiB L2: 12 MiB desc: 24x512 KiB
    L3: 128 MiB desc: 8x16 MiB
  Speed (MHz): avg: 3621 high: 4112 min/max: 2200/4568 boost: enabled
    scaling: driver: acpi-cpufreq governor: performance cores: 1: 3595 2: 3594
    3: 3594 4: 3593 5: 3591 6: 3593 7: 3593 8: 3594 9: 3593 10: 3588 11: 3585
    12: 3608 13: 3591 14: 3592 15: 3583 16: 3588 17: 3592 18: 3593 19: 3591
    20: 3596 21: 3593 22: 3586 23: 4112 24: 3593 25: 3587 26: 3766 27: 3593
    28: 3594 29: 3590 30: 3594 31: 3593 32: 3591 33: 3593 34: 3590 35: 4025
    36: 3879 37: 3593 38: 3593 39: 3601 40: 3592 41: 3586 42: 3592 43: 3595
    44: 3593 45: 3593 46: 3590 47: 3578 48: 3593 bogomips: 364130
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: spec_store_bypass
    mitigation: Speculative Store Bypass disabled via prctl and seccomp
  Type: spectre_v1
    mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional,
    STIBP: conditional, RSB filling
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU106 [GeForce RTX 2060 SUPER] vendor: eVga.com.
    driver: nvidia v: 495.46 alternate: nouveau,nvidia_drm bus-ID: 21:00.0
    chip-ID: 10de:1f06 class-ID: 0300
  Device-2: Logitech BRIO Ultra HD Webcam type: USB
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo bus-ID: 2-1:2
    chip-ID: 046d:085e class-ID: 0300 serial: 05817110
  Device-3: Elgato Systems Cam Link 4K type: USB
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo bus-ID: 2-2:3
    chip-ID: 0fd9:0066 class-ID: 0102 serial: 0004B5227A000
  Display: x11 server: X.Org 1.21.1.3 compositor: kwin_x11 driver:
    loaded: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x2160 s-dpi: 162 s-size: 602x341mm (23.7x13.4")
    s-diag: 692mm (27.2")
  Monitor-1: HDMI-0 res: 3840x2160 hz: 60 dpi: 163
    size: 600x340mm (23.6x13.4") diag: 690mm (27.2")
  OpenGL: renderer: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2
    v: 4.6.0 NVIDIA 495.46 direct render: Yes
Audio:
  Device-1: NVIDIA TU106 High Definition Audio vendor: eVga.com.
    driver: snd_hda_intel v: kernel bus-ID: 21:00.1 chip-ID: 10de:10f9
    class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio driver: snd_hda_intel v: kernel
    bus-ID: 23:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: Logitech BRIO Ultra HD Webcam type: USB
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo bus-ID: 2-1:2
    chip-ID: 046d:085e class-ID: 0300 serial: 05817110
  Device-4: Elgato Systems Cam Link 4K type: USB
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo bus-ID: 2-2:3
    chip-ID: 0fd9:0066 class-ID: 0102 serial: 0004B5227A000
  Device-5: Audio-Technica ATR2100x-USB Microphone type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-1:2 chip-ID: 0909:004d
    class-ID: 0300
  Device-6: C-Media Vanatoo T0 type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 7-2:3 chip-ID: 0d8c:0012
    class-ID: 0300
  Device-7: Giga-Byte USB Audio type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 7-5:5 chip-ID: 0414:a002
    class-ID: 0300
  Sound Server-1: ALSA v: k5.15.15-1-lts running: yes
  Sound Server-2: JACK v: 1.9.20 running: no
  Sound Server-3: PulseAudio v: 15.0 running: no
  Sound Server-4: PipeWire v: 0.3.43 running: yes
Network:
  Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel
    port: 9000 bus-ID: 43:00.0 chip-ID: 8086:1539 class-ID: 0200
  IF: enp67s0 state: down mac: b4:2e:99:fa:27:f1
  Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 44:00.0
    chip-ID: 8086:2723 class-ID: 0280
  IF: wlo2 state: up mac: ac:67:5d:fe:a3:80
Bluetooth:
  Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 9-5:2 chip-ID: 8087:0029 class-ID: e001
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: N/A
Drives:
  Local Storage: total: 2.72 TiB used: 438.9 GiB (15.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:1 vendor: Samsung
    model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
    serial: S59ANJ0N407863W rev: 2B2QEXM7 temp: 55.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung
    model: SSD 970 EVO Plus 1TB size: 931.51 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
    serial: S59ANJ0N407861F rev: 2B2QEXM7 temp: 54.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 type: USB vendor: Patriot model: N/A
    size: 922.5 GiB block-size: physical: 512 B logical: 512 B type: N/A
    serial: 070194316C276B10 rev: PMAP scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 410.27 GiB (44.1%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:3
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 560 KiB (0.2%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:2
  ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 410.27 GiB (44.1%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:3
  ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 410.27 GiB (44.1%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:3
  ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 410.27 GiB (44.1%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:3
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 62.73 GiB used: 512 KiB (0.0%)
    priority: 100 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 16.8 C mobo: N/A gpu: nvidia temp: 58 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 5%
Info:
  Processes: 738 Uptime: 57m wakeups: 0 Memory: 62.73 GiB
  used: 9.72 GiB (15.5%) Init: systemd v: 250 tool: systemctl Compilers:
  gcc: 11.1.0 Packages: 2149 pacman: 2141 lib: 577 flatpak: 0 snap: 8
  Shell: Zsh v: 5.8 running-in: konsole inxi: 3.3.11

I have installed the LTS kernel now and still having issues with bluetooth. In System Settings -> Bluetooth it shows Bluetooth is disabled but clicking the button to enable it has no effect.

However, I AM getting dmsg output now

❯ sudo dmesg | grep blue                                                                                                                                                                                      585.1 Mbps  ─╯
[   11.980509] audit: type=1130 audit(1642536960.498:71): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth-autoconnect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[   12.026669] audit: type=1130 audit(1642536960.538:73): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=bluetooth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Thanks for any troubleshooting guidance with this.

5

So let’s make sure Bluetooth is not blocked for some reason. Please post the terminal output of the command…
$ rfkill list Let’s just make that plain…

rfkill list

It’s easier to understand. Also…there doesn’t happen to be a key or keyboard combination on your machine that turns Bluetooth on/off by any chance?

1 Like
6

Thank you.

❯ rfkill list                                                                                                                                                                                                 526.6 Mbps  ─╯
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy2: Wireless LAN
        Soft blocked: no
        Hard blocked: no

No such key on the keyboard that I'm aware of...

7

OK, so let's play around a bit. Let's turn Bluetooth off, then back on again. This is probably easiest.

rfkill block bluetooth

then...

rfkill unblock bluetooth

Please be sure to reboot afterwards.

EDIT: I'm getting out of my depth with Bluetooth. Fortunately, we have forum members with some amount of expertise with things that fly over the air waves. It's isn't polite to ping Moderators, but I think it might be proper to ping someone who may know some stuff, that being @tbg.

There are others but I confuse their names and forums.
:wink:

8

Please post:

sudo dmesg | grep -Ei 'blue|firm'

sudo bluetoothctl

systemctl status bluetooth

sudo modprobe -r btusb && sleep 10 && sudo modprobe btusb

I would also suggest testing out the linux-mainline kernel.

2 Likes
9

I'm not an expert on anything, but I do know that there is a known 5.15 bug affecting Intel bluetooth radios. The "fix" is the radio appears to come back up normally after a cold boot (not reboot--full shutdown, wait a few seconds, then boot back up). Hopefully they will have a patch soon, my laptop has the same problem!

10

@BluishHumility are you dual booting Windows? or is this strictly an Intel bug.

Have you tested any of the newer or developmental firmware packages. If not, I would suggest at least testing the linux-firmware-git package.

11

Ew, no! :laughing:

It is a multi-boot laptop, but only LInux distros. The bug looks like it is specific to Intel radios and the 5.15 kernel.

Some folks are having success patching specific modules (see this Arch thread), but I’m not about to start recommending that to people because it doesn’t look like a solid fix at this point.

Here’s the bugzilla link, with some more details about the module replacement fix for the brave: 215167 – Bluetooth: hci0: command 0xfc05 tx timeout

It has been known for a while and they are definitely working on it, so I’m planning on just waiting for the patch at this point.

Edit:

What’s this now?

2 Likes
12

That will give you the newer firmware updates that are coming. Often the newer firmware can be found and downloaded directly from the Intel site. Sometimes the newest developmental versions can be found from Google, (as they develop for the Android platform which is of course basically Linux).

The linux-mainline kernel has the newest kernel hardware updates, so it is also the first to receive fixes.

The OP's Bluetooth adapter is registering as "up", is yours also up, but just won't connect.

2 Likes
13

Please don't hijack @T-Fen 's thread. I'm also interested in the solution.
:slight_smile:

Oh, and thank you very much for stepping in @tbg and @BluishHumility . :smiley:

14

It could be a bit of a hijack, but the kernel and firmware suggestions/solutions should apply to both issue regardless, as they are always worth testing out.

I hate Bluetooth, but I was bored so I figured why not assist for a bit @Bro.

1 Like
15

I can install and run a simple 10-base-T /100-base-T ethernet, and for true client-server installations I could set it up and knew every one of NetWare's 5,000 damn acronyms, but things that fly over the airwaves mystify me. Nowadays my desk sits 3 feet from my router. Ethernet all the way, baby!
:rofl:

Thanks. :smiley:

16 
 sudo dmesg | grep -Ei 'blue|firm'                                                                                                                                                                             585 Mbps  ─╯
[    1.890099] acpi PNP0A08:03: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-7f] only partially covers this bridge
[    7.716496] iwlwifi 0000:44:00.0: Direct firmware load for iwlwifi-cc-a0-66.ucode failed with error -2
[    7.716509] iwlwifi 0000:44:00.0: Direct firmware load for iwlwifi-cc-a0-65.ucode failed with error -2
[    7.716520] iwlwifi 0000:44:00.0: Direct firmware load for iwlwifi-cc-a0-64.ucode failed with error -2
[    7.718821] Bluetooth: Core ver 2.22
[    7.718843] NET: Registered PF_BLUETOOTH protocol family
[    7.718844] Bluetooth: HCI device and connection manager initialized
[    7.718850] Bluetooth: HCI socket layer initialized
[    7.718852] Bluetooth: L2CAP socket layer initialized
[    7.718854] Bluetooth: SCO socket layer initialized
[    7.721758] iwlwifi 0000:44:00.0: loaded firmware version 63.c04f3485.0 cc-a0-63.ucode op_mode iwlmvm
[    9.830052] Bluetooth: hci0: Reading Intel version command failed (-110)
[    9.830053] Bluetooth: hci0: command 0xfc05 tx timeout
[   12.227620] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   12.227623] Bluetooth: BNEP filters: protocol multicast
[   12.227627] Bluetooth: BNEP socket layer initialized

and

❯ sudo bluetoothctl                                                                                                                                                                                             585 Mbps  ─╯
Agent registered
[bluetooth]#

and

❯ systemctl status bluetooth                                                                                                                                                                                    585 Mbps  ─╯
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Tue 2022-01-18 14:54:32 MST; 3h 42min ago
       Docs: man:bluetoothd(8)
   Main PID: 1114 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 76926)
     Memory: 2.8M
        CPU: 19ms
     CGroup: /system.slice/bluetooth.service
             └─1114 /usr/lib/bluetooth/bluetoothd

Jan 18 14:54:32 treytheliomajor systemd[1]: Starting Bluetooth service...
Jan 18 14:54:32 treytheliomajor bluetoothd[1114]: Bluetooth daemon 5.63
Jan 18 14:54:32 treytheliomajor systemd[1]: Started Bluetooth service.
Jan 18 14:54:32 treytheliomajor bluetoothd[1114]: Starting SDP server
Jan 18 14:54:32 treytheliomajor bluetoothd[1114]: Bluetooth management interface 1.21 initialized

and

❯ sudo modprobe -r btusb && sleep 10 && sudo modprobe btusb

The last commands returns nothing in the terminal

17

No, it won’t unless there is a problem reloading the bluetooth driver. That command is simply to see if it triggers a change in the bluetooth status and sometimes things start working again.

Have you tried the LTS kernel as suggested?

If that brings no improvement then try the linux-mainline kernel. You do not need to uninstall the LTS kernel if it runs OK on ypur computer. It is a good idea to keep the LTS kernel installed as a backup.

Also, be sure to install the linux-firmware-git package.

18

Yes, I'm on the LTS kernel right now...

Linux treytheliomajor 5.15.15-1-lts #1 SMP Sun, 16 Jan 2022 09:28:22 +0000 x86_64 GNU/Linux
19

You need to report in depth on everything you test. Is bluetooth exactly the same on LTS. If so, test the mainline kernel and linux-firmware-git.

20

Hi-

Just so there is no confusion/misunderstanding, I mentioned that I had installed and was subsequently running the LTS kernel in the 4th post of this thread.

I will try the mainline kernel along with linux-firmware-git and report back