Arch Linux

bsfgp

Member

Registered: 2025-06-16

Posts: 3

[SOLVED] Can't connect logitech mx master 3s via bluetooth

I tried to connect my mouse (mx master 3s) via bluetoothctl, normally at first time, and the mouse was not found.

[bsfgp@lenovo-arch ~]$ bluetoothctl
[NEW] Media /org/bluez/hci0
  SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
  SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
Agent registered
[CHG] Controller  68:███████████:E0 Pairable: yes
hci0 new_settings: powered connectable discoverable bondable ssp br/edr
[bluetoothctl]> scan on
SetDiscoveryFilter success
Discovery started
[CHG] Controller 68:████████████:E0 Discovering: yes
[bluetoothctl]> devices
[bluetoothctl]> devices

Running it with sudo gave me the same result. The mouse was in pairing mode, of course.

Then I tried to connect it using scan le and transport le, again in bluetoothctl:

[bsfgp@lenovo-arch ~]$ bluetoothctl
[NEW] Media /org/bluez/hci0
  SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
  SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
Agent registered
[CHG] Controller 68:███████████:E0 Pairable: yes
hci0 new_settings: powered connectable discoverable bondable ssp br/edr
[bluetoothctl]> scan le
SetDiscoveryFilter success
Failed to start discovery: org.bluez.Error.InProgress

[bsfgp@lenovo-arch ~]$ bluetoothctl
[NEW] Media /org/bluez/hci0
  SupportedUUIDs: 0000110a-0000-1000-8000-00805f9b34fb
  SupportedUUIDs: 0000110b-0000-1000-8000-00805f9b34fb
Agent registered
hci0 new_settings: powered connectable discoverable bondable ssp br/edr
[CHG] Controller 68:███████████:E0 Pairable: yes
[bluetoothctl]> menu scan
Menu scan:
Available commands:
-------------------
uuids [all/uuid1 uuid2 ...]                       Set/Get UUIDs filter
rssi [rssi]                                       Set/Get RSSI filter, and clears pathloss
pathloss [pathloss]                               Set/Get Pathloss filter, and clears RSSI
transport [transport]                             Set/Get transport filter
duplicate-data [on/off]                           Set/Get duplicate data filter
discoverable [on/off]                             Set/Get discoverable filter
pattern [value]                                   Set/Get pattern filter
auto-connect [on/off]                             Set/Get auto-connect filter
clear [uuids/rssi/pathloss/transport/duplicate-data/discoverable/pattern] Clears discovery filter.
back                                              Return to main menu
version                                           Display version
quit                                              Quit program
exit                                              Quit program
help                                              Display help about this program
export                                            Print environment variables
script <filename>                                 Run script
[bluetoothctl]> transport le
[bluetoothctl]> back
Menu main:
Available commands:
-------------------
advertise                                         Advertise Options Submenu
monitor                                           Advertisement Monitor Options Submenu
scan                                              Scan Options Submenu
gatt                                              Generic Attribute Submenu
admin                                             Admin Policy Submenu
player                                            Media Player Submenu
endpoint                                          Media Endpoint Submenu
transport                                         Media Transport Submenu
mgmt                                              Management Submenu
monitor                                           Advertisement Monitor Submenu
assistant                                         Media Assistant Submenu
hci                                               HCI Submenu
list                                              List available controllers
show [ctrl]                                       Controller information
select <ctrl>                                     Select default controller
devices [Paired/Bonded/Trusted/Connected]         List available devices, with an optional property as the filter
system-alias <name>                               Set controller alias
reset-alias                                       Reset controller alias
power <on/off>                                    Set controller power
pairable <on/off>                                 Set controller pairable mode
discoverable <on/off>                             Set controller discoverable mode
discoverable-timeout [value]                      Set discoverable timeout
agent <on/off/auto/capability>                    Enable/disable agent with given capability
default-agent                                     Set agent as the default one
advertise <on/off/type>                           Enable/disable advertising with given type
set-alias <alias>                                 Set device alias
scan <on/off/bredr/le>                            Scan for devices
info [dev/set]                                    Device/Set information
pair [dev]                                        Pair with device
cancel-pairing [dev]                              Cancel pairing with device
trust [dev]                                       Trust device
untrust [dev]                                     Untrust device
block [dev]                                       Block device
unblock [dev]                                     Unblock device
remove <dev>                                      Remove device
connect <dev> [uuid]                              Connect a device and all its profiles or optionally connect a single profile only
disconnect [dev] [uuid]                           Disconnect a device or optionally disconnect a single profile only
wake [dev] [on/off]                               Get/Set wake support
bearer <dev> [last-seen/bredr/le]                 Get/Set preferred bearer
menu <name>                                       Select submenu
version                                           Display version
quit                                              Quit program
exit                                              Quit program
help                                              Display help about this program
export                                            Print environment variables
script <filename>                                 Run script
[bluetoothctl]> scan on
SetDiscoveryFilter success
Discovery started
[CHG] Controller 68:███████████:E0 Discovering: yes
[bluetoothctl]> devices
[bluetoothctl]> devices

Again, no result.

Next, I tried the method with hcitool, it gave me an error:

[bsfgp@lenovo-arch ~]$ sudo hcitool lescan
[sudo] password for bsfgp:
Set scan parameters failed: Input/output error

Connecting via usb dongle works flawlessly, however, I only have one dongle and I have two computers (and only one has bluetooth). No other device is connected via bluetooth.
Can someone help me with this issue?

Last edited by bsfgp (2025-06-19 16:57:09)

ntb314

Member

Registered: 2025-02-13

Posts: 27

Re: [SOLVED] Can't connect logitech mx master 3s via bluetooth

Hey,

It looks like your Bluetooth controller is up and scanning, but it’s not finding the MX Master 3S. Just couple of thoughts, to maybe help you getting on the right track:

-Make sure the mouse is in actual pairing mode (so its blinking or something similar)

-Confirm bluez and bluez-utils are installed, and that the Bluetooth service is running:

sudo pacman -S bluez bluez-utils
sudo systemctl enable --now bluetooth.service

-Then maybe try restarting Bluetooth and doing a clean scan:

sudo bluetoothctl
power off
power on
scan on

-You could also run btmon in another terminal to see if anything is being picked up during the scan and being sure that this works.

-And to make sure there are no interfeerences clear out any previous device pairings and restart the service:

sudo rm -rf /var/lib/bluetooth/*
sudo systemctl restart bluetooth

-If nothing helps, check the cernel for driver errors or similar:

dmesg | grep -i blue

- And lastly if really nothing works, maybe try booting into a Live USB again (like Fedora or Ubuntu) to rule out config issues vs. hardware compatibility.

Hope this helped you getting closer.

Cheers!

Last edited by ntb314 (2025-06-19 12:33:12)

bsfgp

Member

Registered: 2025-06-16

Posts: 3

Re: [SOLVED] Can't connect logitech mx master 3s via bluetooth

Hi, thanks for your answer, and sorry for late response

I tried everything you suggested, even booting into different distributions, but it didn't help :(
Here is kernel debug message:

[    6.423469] Bluetooth: Core ver 2.22
[    6.423495] NET: Registered PF_BLUETOOTH protocol family
[    6.423498] Bluetooth: HCI device and connection manager initialized
[    6.423502] Bluetooth: HCI socket layer initialized
[    6.423505] Bluetooth: L2CAP socket layer initialized
[    6.423509] Bluetooth: SCO socket layer initialized
[    7.252470] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    7.252474] Bluetooth: BNEP filters: protocol multicast
[    7.252479] Bluetooth: BNEP socket layer initialized
[    7.254465] Bluetooth: MGMT ver 1.23
[   16.726162] Bluetooth: RFCOMM TTY layer initialized
[   16.726172] Bluetooth: RFCOMM socket layer initialized
[   16.726178] Bluetooth: RFCOMM ver 1.11

The mouse connects to my android phone, but I can't connect the phone to the computer either.
I'll try to change the wireless antennas later, one of them is torn in the middle, maybe it will help my situation somehow.

bsfgp

Member

Registered: 2025-06-16

Posts: 3

Re: [SOLVED] Can't connect logitech mx master 3s via bluetooth

I just discovered the reason for my connection failure: my wireless adapter does not support bluetooth low energy, which my mouse is running on. I `ll try to change the adapter later, thanks for help

ntb314

Member

Registered: 2025-02-13

Posts: 27

Re: [SOLVED] Can't connect logitech mx master 3s via bluetooth

Hey, nice to hear!

When you're looking for a new adapter, make sure it supports Bluetooth Low Energy sincw not all do, even if they support Bluetooth in general.
I think, intel and some CSR-based dongles should usually work well on Linux so I would try one of these to be sure it works out

Good luck with your replacement!

Cheers