Bluetooth Connectivity Problem

[J_New]

I can't get bluetooth to recognize any of my devices. I've read on other forums that the best way to fix this is to uninstall everything bluetooth and then reinstall, but I'm not sure if that's the best way. Is there some advice for me on this?

[kato181]

Please read the forum rules with regards to Sect 5. Information is required of the system you are using. In terminal copy & paste the following command and post the results back here in between the code display brackets 5th icon above the text box.

Code: Select all

inxi -Fxz

Code: Select all

dmesg | egrep -i 'blue|firm'

[J_New]

Thank you.

Result of inxi -Fxz:

Code: Select all

System:
  Kernel: 5.15.0-58-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
    Desktop: Cinnamon 5.6.7 Distro: Linux Mint 21.1 Vera
    base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: Micro-Star product: MS-7D91 v: 4.0
    serial: <superuser required>
  Mobo: Micro-Star model: MAG Z790 TOMAHAWK WIFI (MS-7D91) v: 4.0
    serial: <superuser required> UEFI: American Megatrends LLC. v: H.00
    date: 09/21/2022
Battery:
  Device-1: hidpp_battery_0 model: Logitech MX Keys Wireless Keyboard
    charge: 55% (should be ignored) status: Discharging
  Device-2: hidpp_battery_1 model: Logitech Wireless Mouse MX Master 3
    charge: 100% (should be ignored) status: Discharging
CPU:
  Info: 24-core (8-mt/16-st) model: 13th Gen Intel Core i9-13900K bits: 64
    type: MST AMCP arch: N/A rev: 1 cache: L1: 2.1 MiB L2: 32 MiB L3: 36 MiB
  Speed (MHz): avg: 4910 high: 5700 min/max: 800/4053:4284:4300 cores:
    1: 5487 2: 5513 3: 5500 4: 5505 5: 5500 6: 5500 7: 5500 8: 5513 9: 5500
    10: 5513 11: 5680 12: 5700 13: 5500 14: 5500 15: 5500 16: 5501 17: 4282
    18: 4304 19: 4256 20: 4306 21: 4331 22: 4300 23: 4312 24: 4304 25: 4303
    26: 4282 27: 4293 28: 4273 29: 4293 30: 4279 31: 4320 32: 4301
    bogomips: 191692
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel vendor: Micro-Star MSI driver: N/A bus-ID: 00:02.0
  Device-2: NVIDIA GA104 [GeForce RTX 3070 Lite Hash Rate]
    vendor: Micro-Star MSI driver: nvidia v: 525.78.01 bus-ID: 01:00.0
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia
    resolution: 3840x2160~30Hz
  OpenGL: renderer: NVIDIA GeForce RTX 3070/PCIe/SSE2
    v: 4.6.0 NVIDIA 525.78.01 direct render: Yes
Audio:
  Device-1: Intel vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3
  Device-2: NVIDIA GA104 High Definition Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel bus-ID: 01:00.1
  Device-3: Micro Star USB Audio type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 1-11:7
  Sound Server-1: ALSA v: k5.15.0-58-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel driver: iwlwifi v: kernel port: N/A bus-ID: 00:14.3
  IF: wlo1 state: down mac: <filter>
  Device-2: Intel vendor: Micro-Star MSI driver: igc v: kernel port: N/A
    bus-ID: 05:00.0
  IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 1-14:11
  Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
  Local Storage: total: 15.46 TiB used: 3.32 TiB (21.5%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 PRO 2TB size: 1.82 TiB
    temp: 33.9 C
  ID-2: /dev/nvme1n1 vendor: Gigabyte model: GP-AG41TB size: 931.51 GiB
    temp: 34.9 C
  ID-3: /dev/sda vendor: Western Digital model: WD6004FZWX-00BKVA0
    size: 5.46 TiB
  ID-4: /dev/sdb type: USB vendor: Seagate model: Expansion SW
    size: 5.46 TiB
  ID-5: /dev/sdc type: USB vendor: Western Digital
    model: WD My Passport 0820 size: 1.82 TiB
Partition:
  ID-1: / size: 1.79 TiB used: 59.83 GiB (3.3%) fs: ext4 dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 511 MiB used: 5.2 MiB (1.0%) fs: vfat
    dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
  System Temperatures: cpu: 27.8 C mobo: N/A gpu: nvidia temp: 41 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Info:
  Processes: 513 Uptime: 2h 6m Memory: 62.58 GiB used: 4.54 GiB (7.3%)
  Init: systemd runlevel: 5 Compilers: gcc: 11.3.0 Packages: 2786 Shell: Bash
  v: 5.1.16 inxi: 3.3.13

Result of dmesg | egrep -i 'blue|firm'

Code: Select all

[    5.942700] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-66.ucode failed with error -2
[    5.942708] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-so-a0-gf-a0-65.ucode failed with error -2
[    5.943796] iwlwifi 0000:00:14.3: loaded firmware version 64.97bbee0a.0 so-a0-gf-a0-64.ucode op_mode iwlmvm
[    6.006962] Bluetooth: Core ver 2.22
[    6.006974] NET: Registered PF_BLUETOOTH protocol family
[    6.006975] Bluetooth: HCI device and connection manager initialized
[    6.006977] Bluetooth: HCI socket layer initialized
[    6.006978] Bluetooth: L2CAP socket layer initialized
[    6.006980] Bluetooth: SCO socket layer initialized
[    6.013291] Bluetooth: hci0: Device revision is 0
[    6.013293] Bluetooth: hci0: Secure boot is enabled
[    6.013293] Bluetooth: hci0: OTP lock is enabled
[    6.013293] Bluetooth: hci0: API lock is enabled
[    6.013293] Bluetooth: hci0: Debug lock is disabled
[    6.013294] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    6.013294] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
[    6.014007] Bluetooth: hci0: Found device firmware: intel/ibt-1040-0041.sfi
[    7.316427] Bluetooth: hci0: Waiting for firmware download to complete
[    7.317327] Bluetooth: hci0: Firmware loaded in 1272773 usecs
[    7.317436] Bluetooth: hci0: Waiting for device to boot
[    7.335391] Bluetooth: hci0: Device booted in 17630 usecs
[    7.343829] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-1040-0041.ddc
[    7.345427] Bluetooth: hci0: Applying Intel DDC parameters completed
[    7.349444] Bluetooth: hci0: Firmware timestamp 2022.5 buildtype 1 build 38020
[    9.946852] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    9.946856] Bluetooth: BNEP filters: protocol multicast
[    9.946860] Bluetooth: BNEP socket layer initialized
[    9.988420] Bluetooth: RFCOMM TTY layer initialized
[    9.988423] Bluetooth: RFCOMM socket layer initialized
[    9.988426] Bluetooth: RFCOMM ver 1.11
[ 4832.171342] Bluetooth: hci0: Ignoring error of Inquiry Cancel command
[ 5268.355305] Bluetooth: hci0: Ignoring error of Inquiry Cancel command
[ 5678.495289] Bluetooth: hci0: Ignoring error of Inquiry Cancel command
[ 5848.777295] Bluetooth: hci0: Ignoring error of Inquiry Cancel command
[ 6274.120307] Bluetooth: hci0: Ignoring error of Inquiry Cancel command

My problem appears to be with finding devices. It just won't acknowledge any of my Bluetooth devices. However, I'm sure it's running because when I run /etc/init.d/bluetooth status I get:

Code: Select all

bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2023-02-07 21:32:55 CST; 33min ago
       Docs: man:bluetoothd(8)
   Main PID: 7581 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 76643)
     Memory: 836.0K
        CPU: 24ms
     CGroup: /system.slice/bluetooth.service
             └─7581 /usr/lib/bluetooth/bluetoothd

[kato181]

Just because bluetooth is running, doesn't necessary means it will detect bluetooth devices.
What bluetooth devices do you have connected that are not being detected by bluetooth.
I'm running LM21.1 on a desktop and it will NOT detect my expensive bluetooth headset, yet it will detect my cheaper headset. I have to keep turning the device on and off until it detects it...go figure.. Ubuntu 22.04 has known bluetooth problems with regards to detecting devices.
Bluetooth worked in LM20.3 perfectly, then LM21 and LM 21.1 arrives and bluetooth connection problems appear, there doesn't seem to be a fix either.

[J_New]

I've never had any of my several Bluetooth devices connect as of yet.

This is a new build, but everything Mint was installed without issue. I don't know if there is a conflicting plugin, or a missing part of the program, but I have had no luck getting anything to be acknowledged whenever I search for new devices.

[SMG]

Result of inxi -Fxz:

You have extremely new hardware and the onboard graphics driver is not loaded because the kernel is too old to have the driver.

Graphics:
Device-1: Intel vendor: Micro-Star MSI driver: N/A bus-ID: 00:02.0
Device-2: NVIDIA GA104 [GeForce RTX 3070 Lite Hash Rate]
vendor: Micro-Star MSI driver: nvidia v: 525.78.01 bus-ID: 01:00.0
Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: nvidia
unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia
resolution: 3840x2160~30Hz
OpenGL: renderer: NVIDIA GeForce RTX 3070/PCIe/SSE2
v: 4.6.0 NVIDIA 525.78.01 direct render: Yes

Please upgrade to a newer kernel. You can install the latest 6.1-oem kernel with

Code: Select all

sudo apt-get install linux-oem-22.04c

and reboot.

The newer kernel may also help with the missing firmware listed in the output you posted. However, it is also possible you may need to manually load newer firmware. Let's see how the newer kernel works first.

Also, if this is the correct link Support For MAG Z790 TOMAHAWK WIFI:BIOS, it appears there have been two updates since the version you have installed.
Machine:
Type: Desktop System: Micro-Star product: MS-7D91 v: 4.0
serial: <superuser required>
Mobo: Micro-Star model: MAG Z790 TOMAHAWK WIFI (MS-7D91) v: 4.0
serial: <superuser required> UEFI: American Megatrends LLC. v: H.00
date: 09/21/2022

[J_New]

Please upgrade to a newer kernel. You can install the latest 6.1-oem kernel with

Code: Select all

sudo apt-get install linux-oem-22.04c

and reboot.

I just did, and now I cannot boot my computer. The only thing that shows up on the screen is:

Code: Select all

error: out of memory.
Press any key to continue...

Nothing happens when I press a key. This looks bleak.

[SMG]

I just did, and now I cannot boot my computer. The only thing that shows up on the screen is:

Code: Select all

error: out of memory.
Press any key to continue...

Nothing happens when I press a key. This looks bleak.

And what happens after you press any key? I suggest you go into your computer's BIOS/UEFI and switch to using the onboard graphics as primary so you can make the change so the system will boot.

This out of memory issue is a known issue due to a bug. Please see this post for an option which worked for many people.

[J_New]

As I stated, nothing happens. It just hangs.

However, I managed to get an older version back through the grub menu and safe mode.

There appears to be too many "known issues" for me to continue with Mint.

[SMG]

There appears to be too many "known issues" for me to continue with Mint.

Your choice. You have very new hardware which often means there are more likely to be issues because it takes a while for the open-source community to catch up to what Microsoft or Apple can do before releasing new hardware.

Are there newer BIOS/UEFI versions available? If that was the correct link, you will want to update.

[J_New]

I did update that latest AMI BIOS package dealing with exFAT support and some other things.

I finally got this back to the point where I don't need to boot in an earlier recovery mode. Who knows how long that will last, though.

I've had earlier versions of Mint with relatively no problems like what I'm having with Vera. They don't even acknowledge any Bluetooth issues on their latest release notes page.

[SMG]

I finally got this back to the point where I don't need to boot in an earlier recovery mode. Who knows how long that will last, though.

What is "an earlier recovery mode"? I don't understand what that means.

I've had earlier versions of Mint with relatively no problems like what I'm having with Vera.

You had earlier versions of Linux Mint on this hardware without problems?

They don't even acknowledge any Bluetooth issues on their latest release notes page.

Release notes can only mention known issues which happen prior to release. If there aren't known issues, then they will not be mentioned in the release notes.

There is a section in the Linux Mint User Guide on Bluetooth.

[SMG]

The latest blog post Monthly News – January 2023 mentions under Bug Fixes that "Blueman was upgraded to version 2.3.5." Please check to make sure you have the latest.

Checking the Blueman Issues, I see two open ones. I don't know if either of them sound like your issue.

[J_New]

After updating the kernel, my grub boot screen lists six different versions of the OS to choose from; three 'generic' versions and three with a recovery mode option.

I've been updating the Blueman as it becomes available. The two threads from the Blueman Issues page are from last year with Vanessa. They didn't address my problem.

[SMG]

After updating the kernel, my grub boot screen lists six different versions of the OS to choose from; three 'generic' versions and three with a recovery mode option.

That is the way grub works. You have the option to boot using the kernel in normal mode or you can boot using the kernel with additional parameters added to it to disable certain functionality including the graphics drivers (aka recovery mode).

All the kernels have numbers so it is better to state which kernel you are using rather than saying "earlier".

I've been updating the Blueman as it becomes available. The two threads from the Blueman Issues page are from last year with Vanessa. They didn't address my problem.

Vera was not available when those were posted. It is possible the exact same issue occurs with Vera as with Vanessa which is why I asked if you the problem sounds similar to what you are experiencing. I did not ask you to read them to see if they "addressed your problem". I asked you if they sounded like the same problem.