[SOLVED w/KERNEL UPDATE] Bluetooth devices gone. Nothing connects

[UncleSpellbinder]

NO IDEA what happened. But out of nowhere, my Logitech MX Anywhere 3 mouse stopped. I connected a wired mouse and attempted to connect. No-go as NO DEVICES show as available. Other devices that were available (game controller, 2 different TVs), no longer show.

What could have happened???

SYSTEM INFO:

[joekamprad]

systemctl status bluetooth

inxi -Eaz

[UncleSpellbinder]

❯ systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabl>
     Active: active (running) since Sat 2024-10-19 15:45:54 CDT; 1h 6min ago
 Invocation: 08c2284e393d484ea5a6e4cc8bbe01a2
       Docs: man:bluetoothd(8)
   Main PID: 547 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18820)
     Memory: 2.4M (peak: 2.9M)
        CPU: 48ms
     CGroup: /system.slice/bluetooth.service
             └─547 /usr/lib/bluetooth/bluetoothd

Oct 19 15:46:09 eos bluetoothd[547]: Endpoint registered: sender=:1.37 path=/MediaEndpo>
Oct 19 15:46:09 eos bluetoothd[547]: Endpoint registered: sender=:1.37 path=/MediaEndpo>
Oct 19 15:46:09 eos bluetoothd[547]: Endpoint registered: sender=:1.37 path=/MediaEndpo>
Oct 19 15:46:09 eos bluetoothd[547]: Endpoint registered: sender=:1.37 path=/MediaEndpo>
Oct 19 15:46:09 eos bluetoothd[547]: Endpoint registered: sender=:1.37 path=/MediaEndpo>
Oct 19 15:46:09 eos bluetoothd[547]: Endpoint registered: sender=:1.37 path=/MediaEndpo>
Oct 19 15:46:09 eos bluetoothd[547]: Endpoint registered: sender=:1.37 path=/MediaEndpo>
Oct 19 15:46:09 eos bluetoothd[547]: Controller resume with wake event 0x0
Oct 19 15:46:13 eos bluetoothd[547]: Controller resume with wake event 0x0
Oct 19 15:46:30 eos bluetoothd[547]: Controller resume with wake event 0x0
lines 1-23/23 (END)

❯ inxi -Eaz
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.1
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-5:4 chip-ID: 0bda:c821
    class-ID: e001 serial: <filter>
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.2
    lmp-v: 8 status: discoverable: no pairing: no class-ID: 6c0104

[joekamprad]

@UncleSpellbinder

Controller resume with wake event

could be simply this? it does not properly wake after sleep…
you tried sudo systemctl restart bluetooth ?

[UncleSpellbinder]

Nope. Same result. Even rebooted, no change.

[ricklinux]

Have you tried from the beginning and reset it, pair it connect, etc etc.

[hoosfoos]

it might be related to this:

Can't connect new bluetooth device

Hello helpful EndeavourOS folks. I generally use a bluetooth mouse (specifically, a Logitech ergo m575 trackball). I’ve been using EndeavourOS for years and years. A couple of months shy of 4 years, to be exact: [jason@xps139310 ~]$ stat / | grep Birth Birth: 2020-12-07 16:15:49.000000000 -0500 In any case, my bluetooth mouse doesn’t connect this morning (it was working fine yesterday). This is randomly happened once or twice before, and I usually just have bluetooth “forget” the device, …

https://bugzilla.kernel.org/show_bug.cgi?id=219385

[UncleSpellbinder]

Thanks so much for the link. As for now, I have a wired generic mouse attached. I prefer not to downgrade, so I’ll wait for a possible fix in the next available update.

[1093i3511]

On a side note, if the bluetooth connection is the culprit. You could switch to a unifying / bolt receiver temporarily until this issue is resolved.

[manuel]

Could be packages

linux-firmware
linux-firmware-whence

that were updated 2 days ago?

As a temporary test, you could try downgrading them to see if it helps. And be sure to have the USB installer available, just in case.

[HBR]

It’s a bug in kernel 6.11.4. Downgrading to 6.11.3 fixes it (while keeping linux-firmware up to date).

https://bugzilla.kernel.org/show_bug.cgi?id=219385

[keescase]

The bug report mentions kernel 6.12 rc 3. Is that the same kernel as 6.11.4 I wonder ?

[SundaSpirit]

@keescase

6.12 rc 3

No, they are two different kernels. Rc means release-candidate for mainline kernels.

The 6.12 rc 4 kernel does not find the existing Wi-Fi connections.

[Unexist]

Same problem with latest Kernel update

[keescase]

So if I understand this correctly 6.11.4 is the number that arch uses for kernel 6.12 rc 4 ?

[straycat]

No they are not the same 6.11 is stable and 6.12 is experimental meaning it is in testing.

[keescase]

That’s exactly what i thought but the link towards the bug report is about 6.12 not 6.11, that also seems to have the bug already because that is the kernel that is installed at the TS his system.

[HBR]

The bug report was opened for 6.12 but it also affects 6.11.4, as mentioned in the replies of the bug report.

It is just one example, there are more reports.

[emk2203]

Could you post the output of sudo dmesg | grep Bluetooth?

[Unexist]

I found a way around this problem for Logitech peripherals thanks to Warlock on the Telegram chat, and also resolved a couple other issues I had from the beginning of using EOS, so this was a productive tinkering day

1. Use a dongle for bluetooth keyboard and mouse (mine is Logitech Bolt).
2. Download Solaar and connect the dongle with the peripherals (only works with Logitech peripherals).

With this solution I can use keyboard and mouse BT with kernal 6.11.4, but I also resolved two other issues:

1. I can now use bluetooth keyboard to select the kernel/OS to boot on the boot screen.
2. With Solaar I can set the DPI for my mouse. For some reason on the Plasma settings they are capped and my mouse was very slow. But for this to work you need to add Solaar to autostart otherwise doesn’t work on reboot.