Hi all,
I seem to have jacked up my Bluetooth setup. I was previously able to use my BT mouse and standing desk with only minor issues. In trying to fix those minor issues, I have apparently jacked up my adapter. I can see the adapter and use bluetoothctl to initiate scans and other things, but the scan never returns anything.
Sadly, I’m not even sure what I changed to get here. I added a couple kernel parameters and then removed them. I also disabled and then re-enabled Legacy USB Support in my BIOS settings.
I even booted the EndeavourOS live usb and it had the same bluetooth issues.
Weirdly, Windows (which I haven’t been in for a couple months) had no issues with Bluetooth and the mouse connected immediately.
Here’s the output from some commands if that helps:
❯ inxi
System:
Kernel: 6.1.37-1-lts arch: x86_64 bits: 64 compiler: gcc v: 13.1.1
Desktop: i3 v: 4.22 Distro: EndeavourOS base: Arch Linux
Bluetooth:
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB
bus-ID: 1-3:2
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
❯ systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: active (running) since Mon 2023-07-03 14:36:46 PDT; 3h 33min left
Docs: man:bluetoothd(8)
Main PID: 692 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 38308)
Memory: 2.5M
CPU: 28ms
CGroup: /system.slice/bluetooth.service
└─692 /usr/lib/bluetooth/bluetoothd
❯ pacman -Qs blue
local/blueman 2.3.5-2
GTK+ Bluetooth Manager
local/bluez-git 1:5.66.r166.g011e562a9-1
Libraries and tools for the Bluetooth protocol stack
local/bluez-tools 0.2.0-5
A set of tools to manage Bluetooth devices for Linux
local/hidapi 0.14.0-1
Simple library for communicating with USB and Bluetooth HID devices
local/libldac 2.0.2.3-1
LDAC Bluetooth encoder library
local/pipewire-pulse 1:0.3.72-1
Low-latency audio/video router and processor - PulseAudio replacement
local/sbc 2.0-1
Bluetooth Subband Codec (SBC) library
I’m open to any suggestions, thanks for looking!
is your system dual-booted ?
If yes, then you might get problems with devices that gets connected to Windows and then you’re trying to connect them to linux.
Try removing those devices from your windows OS. Then connect on linux
What is the bluetooth adapter chipset?
inxi -Na
I ran the same problem, guess I gonna wait for update
Have you tried
sudo modprobe -r btusb
sudo modprobe btusb
sudo systemctl restart bluetooth
1 Like
I did, it does not fix the bluetooth, for both lts and regular kernel
UPDATE: somehow my bluetooth works again
UPDATE 2: Oh boy, bluetooth is crash again
It is, but I was using multiple Bluetooth devices on Linux up until yesterday. I did boot into windows last night to test, but only after this failed connection problem started tearing it’s head.
I’ll boot back in and unpair Windows from my mouse just to be sure.
-Na only showed my network adapter
Network:
Device-1: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 04:00.0
chip-ID: 8086:1539 class-ID: 0200
-Ea showed the Blurtooth one if that’s what you’re after
❯ inxi -Ea
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-3:4 chip-ID: 2b89:8761
class-ID: e001 serial: 00E04C239987
Report: bt-adapter ID: hci0 rfk-id: 1 state: up address: 0A:62:21:20:7E:88
Just gave that a shot, but no luck. At the end there, I have my mouse in pairing mode and would expect to see it show up.
❯ sudo modprobe -r btusb
[sudo] password for XXX:
❯ bluetoothctl
Agent registered
[bluetooth]# show
No default controller available
[bluetooth]# exit
❯ sudo modprobe btusb
❯ sudo systemctl restart bluetooth
❯ bluetoothctl
Agent registered
[bluetooth]# show
Controller 0A:62:21:20:7E:88 (public)
Name: Alfonso
Alias: Alfonso
Class: 0x006c0104
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x000000b4
Pairable: yes
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0542
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x04 (4)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
[bluetooth]# scan on
Discovery started
[CHG] Controller 0A:62:21:20:7E:88 Discovering: yes
[bluetooth]#
Yeah, that’s the weird part. It shows up in bluetoothctl and shows that it’s on and scanning, it just never finds any devices 
Sometimes you have to fiddle with blutoothctl and go through the process of removing and starting from scratch to get it to do each step so it selects the proper device hardware info.
Hey Rick,
I was sick for a bit, so just getting back to this. I tried clearing out devices in bluetoothctl, but no luck.
Do you know of a way I could fully reset my adapter? I feel like something got tripped up and now it’s in this weird state.
Thanks for all your help!
Your bluetooth adapter is a usb device? What device are you trying to connect to?
Edit:
Have you checked rfkill
rfkill shows
❯ rfkill list
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
And yes, I have a usb bluetooth adapter. I’m trying to get it to detect my bluetooth mouse when scanning, but it currently doesn’t show any devices at all.
I tried using an older usb bluetooth dongle, which does see the mouse, but that device has issues with dropping connections quite frequently.
Have you tried bluetoothctl?
bluetoothctl scan on
Does it not find it. If you can see it with the other adapter you can identify it.
Maybe this helps?
Yeah, bluetoothctl is what I’ve used to manage this device for the past few months with no issues. Now, though, it’s able to see the adapter and start the scan, but the scan never finds anything.
~ main [!] +58 -57 10:23:42 AM
❯ bluetoothctl show
Controller 0A:62:21:20:7E:88 (public)
Name: Alfonso
Alias: Alfonso
Class: 0x006c0104
Powered: yes
Discoverable: no
DiscoverableTimeout: 0x000000b4
Pairable: yes
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0542
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x04 (4)
SupportedIncludes: tx-power
SupportedIncludes: appearance
SupportedIncludes: local-name
SupportedSecondaryChannels: 1M
SupportedSecondaryChannels: 2M
SupportedSecondaryChannels: Coded
~ main [!] +58 -57 10:36:19 AM
❯ bluetoothctl scan on
Discovery started
[CHG] Controller 0A:62:21:20:7E:88 Discovering: yes
I don’t know? Maybe try plugging the usb mouse into a different port?
Edit: Does it list anything
lsusb
Hmm, the mouse itself is wireless. I’ve tried plugging the Bluetooth adapter into multiple ports with no luck. lsusb shows:
~ main [!] +58 -57 10:39:48 AM
❯ lsusb
Bus 004 Device 003: ID 05e3:0620 Genesys Logic, Inc. GL3523 Hub
Bus 004 Device 002: ID 0bda:0411 Realtek Semiconductor Corp. Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 04d9:4545 Holtek Semiconductor, Inc. Keyboard [Diatec Majestouch 2 Tenkeyless]
Bus 003 Device 006: ID 046d:0825 Logitech, Inc. Webcam C270
Bus 003 Device 005: ID b58e:9e84 Blue Microphones Yeti Stereo Microphone
Bus 003 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 003 Device 002: ID 0bda:5411 Realtek Semiconductor Corp. RTS5411 Hub
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 003: ID 054c:0ce6 Sony Corp. DualSense wireless controller (PS5)
Bus 001 Device 002: ID 046d:c07e Logitech, Inc. G402 Gaming Mouse
Bus 001 Device 005: ID 2b89:8761 Realtek Bluetooth Radio
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
With the second-to-last item being the adapter.
I’ve got no good ideas on how to debug this atm. I think at this point I either need to wipe my machine and fresh install the OS or buy a different bluetooth adapter.
Well if it’s only a usb mouse they are not that expensive. Did the adapter come with the mouse?
