NOTE: When I tried posting it said I can’t put links in my post. I had a few links but they are removed so they just say “link here” with no link 
Yet another “my bluetooth doesn’t work with my xbox controller” post. I am, as you may have surmised, a new Manjaro user. I usually try to solve these things myself but I’m desperate. I can’t find anything similar with my searches and I’ve reached the end of my capabilities.
The gist of my problem is that bluez seems to be sending “LE Extended Create Connection” commands (only supported by BT5.0+ devices as far as I understand) to my Xbox Series X controller. As far as I understand, this controller is a BT4.0 device, so it fails to pair and returns “Unknown HCI Command” with status 0x01.
I have tried a lot of things but I haven’t found a way to forcibly use 4.0 commands. I’m not sure why it doesn’t recognize that it needs to use compatible commands. The biggest questions I have:
- Can I force LE Create Connection command instead of Extended?
- Is xpadneo (xbox series x BT driver) supposed to fix this, or is this a btusb problem? How can I tell if this driver is doing what it should?
- I did find some random post (can’t post a link due to being a new account) about ATS2851 based dongles that advertises support for LE extended create connection but doesn’t implement it which leads to failing connections in the same way. Is there a way to make my device use this fix? I don’t know how to tell what my device actually is.
I will list some details below about what I’ve tried and my system config.
Things I've tried
- Plugging in the controller with usb. This works fine but doesn’t solve my issue.
- Using the Manjaro settings menu GUI to pair. Same result.
- Pairing with the mgmt menu in bluetoothctl trying to force type 0x00 (BR/EDR), 0x01 (LE Public) and 0x02 (LE Random)
- Extracting the pairing keys from a Windows instance: (Arch wiki link) This doesn’t really help since although it thinks it’s paired, it still can’t connect.
- Various settings in /etc/bluetooth/main.conf As far as I can tell, none of these force it to use regular LE commands. I tried forcing BR/EDR but it fails with page timeout (0x04) when attempting to connect. I’m not familiar enough with BT to know how to set page settings. I also don’t know if the settings will work anyways (as per the message about kernal support in the main.conf file)
- Fooling around with all the settings in the bluetoothctl menus. None of them really do much for this scenario from what I’ve tried.
- Holding the pair button for 20sec to “reset” the controller.
- Telling windows to forget the connection
- Removing the battery from the controller and re-inserting
- Disconnecting and reconnecting the BT dongle
- Restarting my computer
Logs from a failed attempt
bluetoothctl log
sudo bluetoothctl ✔
Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# power on
[bluetooth]# Changing power on succeeded
[bluetooth]# pairable on
[bluetooth]# Changing pairable on succeeded
[bluetooth]# discoverable on
[bluetooth]# hci0 new_settings: powered connectable bondable ssp br/edr le secure-conn
[bluetooth]# hci0 new_settings: powered connectable discoverable bondable ssp br/edr le secure-conn
[bluetooth]# Changing discoverable on succeeded
[bluetooth]# [CHG] Controller F4:4E:FC:89:3F:40 Discoverable: yes
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# hci0 type 7 discovering on
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller F4:4E:FC:89:3F:40 Discovering: yes
[bluetooth]# [NEW] Device 1C:13:38:14:E5:74 PR BT 8755
[bluetooth]# [NEW] Device 68:6C:E6:4D:45:A3 Xbox Wireless Controller
[bluetooth]# [NEW] Device B4:D2:85:C6:EB:EE S5dfb24825d1806edC
[bluetooth]# [CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffd4 (-44)
[bluetooth]# [CHG] Device B4:D2:85:C6:EB:EE UUIDs: 00001122-0000-1000-8000-00805f9b34fb
[bluetooth]# [CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffcc (-52)
[bluetooth]# [NEW] Device 38:39:8F:D8:5E:71 Envoy / 202403018288
[bluetooth]# [CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffd4 (-44)
[bluetooth]# [CHG] Device 68:6C:E6:4D:45:A3 TxPower: 0x0014 (20)
[bluetooth]# [CHG] Device 68:6C:E6:4D:45:A3 UUIDs: 00001812-0000-1000-8000-00805f9b34fb
[bluetooth]# [CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[bluetooth]# [CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
[bluetooth]# 00 .
[bluetooth]# [CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffcc (-52)
[bluetooth]# [CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[bluetooth]# [CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
[bluetooth]# 03 00 80 ...
[bluetooth]# [NEW] Device 73:3C:95:E4:93:60 73-3C-95-E4-93-60
[NEW] Device 61:9E:CC:B2:3D:2C 61-9E-CC-B2-3D-2C
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
00 .
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
03 00 80 ...
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
00 .
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
03 00 80 ...
[CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffd4 (-44)
[CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffcb (-53)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
00 .
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
03 00 80 ...
[CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffd4 (-44)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
00 .
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
03 00 80 ...
[CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffcc (-52)
[CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffd4 (-44)
[NEW] Device 53:25:FA:80:F2:D6 53-25-FA-80-F2-D6
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
00 .
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
03 00 80 ...
[CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffcc (-52)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
00 .
[CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffd4 (-44)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
03 00 80 ...
[CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffcc (-52)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
00 .
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
03 00 80 ...
[CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffd4 (-44)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
00 .
[CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffcb (-53)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
03 00 80 ...
[CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffd4 (-44)
[CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffcb (-53)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
00 .
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
03 00 80 ...
[CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffd4 (-44)
[NEW] Device 42:56:2E:48:DE:28 SHIELD
[CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffcb (-53)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
00 .
[CHG] Device 68:6C:E6:4D:45:A3 RSSI: 0xffffffd3 (-45)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Key: 0x0006 (6)
[CHG] Device 68:6C:E6:4D:45:A3 ManufacturerData.Value:
03 00 80 ...
[bluetooth]# scan off
[bluetooth]# hci0 type 7 discovering off
[bluetooth]# Discovery stopped
[bluetooth]# [CHG] Device 42:56:2E:48:DE:28 TxPower is nil
[bluetooth]# [CHG] Device 42:56:2E:48:DE:28 RSSI is nil
[bluetooth]# [CHG] Device 53:25:FA:80:F2:D6 RSSI is nil
[bluetooth]# [CHG] Device 61:9E:CC:B2:3D:2C TxPower is nil
[bluetooth]# [CHG] Device 61:9E:CC:B2:3D:2C RSSI is nil
[bluetooth]# [CHG] Device 73:3C:95:E4:93:60 RSSI is nil
[bluetooth]# [CHG] Device 38:39:8F:D8:5E:71 RSSI is nil
[bluetooth]# [CHG] Device B4:D2:85:C6:EB:EE RSSI is nil
[bluetooth]# [CHG] Device 68:6C:E6:4D:45:A3 TxPower is nil
[bluetooth]# [CHG] Device 68:6C:E6:4D:45:A3 RSSI is nil
[bluetooth]# [CHG] Device 1C:13:38:14:E5:74 RSSI is nil
[bluetooth]# [CHG] Controller F4:4E:FC:89:3F:40 Discovering: no
[bluetooth]# devices
Device 1C:13:38:14:E5:74 PR BT 8755
Device 68:6C:E6:4D:45:A3 Xbox Wireless Controller
Device B4:D2:85:C6:EB:EE S5dfb24825d1806edC
Device 38:39:8F:D8:5E:71 Envoy / 202403018288
Device 73:3C:95:E4:93:60 73-3C-95-E4-93-60
Device 61:9E:CC:B2:3D:2C 61-9E-CC-B2-3D-2C
Device 53:25:FA:80:F2:D6 53-25-FA-80-F2-D6
Device 42:56:2E:48:DE:28 SHIELD
[blue68:6C:E6:4D:45:A3C:E6:4D:45:A3
Attempting to pair with 68:6C:E6:4D:45:A3
[bluetooth]# hci0 68:6C:E6:4D:45:A3 type LE Public connect failed (status 0x01, Unknown Command)
[bluetooth]# Failed to pair: org.bluez.Error.AuthenticationFailed
btmon output. Too much text, so it's truncated to after the scan off command
bluetoothd[242478]: @ MGMT Command: Stop Discovery (0x0024) plen 1 {0x0001} [hci0] 49.215549
Address type: 0x07
BR/EDR
LE Public
LE Random
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2 #321 [hci0] 49.215600
Scanning: Disabled (0x00)
Filter duplicates: Disabled (0x00)
> HCI Event: Command Complete (0x0e) plen 4 #322 [hci0] 49.216124
LE Set Scan Enable (0x08|0x000c) ncmd 1
Status: Success (0x00)
@ MGMT Event: Command Complete (0x0001) plen 4 {0x0001} [hci0] 49.216175
Stop Discovery (0x0024) plen 1
Status: Success (0x00)
Address type: 0x07
BR/EDR
LE Public
LE Random
@ MGMT Event: Discovering (0x0013) plen 2 {0x0002} [hci0] 49.216183
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Disabled (0x00)
@ MGMT Event: Discovering (0x0013) plen 2 {0x0001} [hci0] 49.216183
Address type: 0x07
BR/EDR
LE Public
LE Random
Discovery: Disabled (0x00)
bluetoothd[242478]: @ MGMT Command: Pair Device (0x0019) plen 8 {0x0001} [hci0] 55.784582
LE Address: 68:6C:E6:4D:45:A3 (Microsoft Corporation)
Capability: KeyboardDisplay (0x04)
< HCI Command: LE Add Device To Accept List (0x08|0x0011) plen 7 #323 [hci0] 55.784625
Address type: Public (0x00)
Address: 68:6C:E6:4D:45:A3 (Microsoft Corporation)
> HCI Event: Command Complete (0x0e) plen 4 #324 [hci0] 55.786067
LE Add Device To Accept List (0x08|0x0011) ncmd 1
Status: Success (0x00)
< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7 #325 [hci0] 55.786123
Type: Passive (0x00)
Interval: 60.000 msec (0x0060)
Window: 60.000 msec (0x0060)
Own address type: Public (0x00)
Filter policy: Ignore not in accept list (0x01)
> HCI Event: Command Complete (0x0e) plen 4 #326 [hci0] 55.788064
LE Set Scan Parameters (0x08|0x000b) ncmd 1
Status: Success (0x00)
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2 #327 [hci0] 55.788103
Scanning: Enabled (0x01)
Filter duplicates: Enabled (0x01)
> HCI Event: Command Complete (0x0e) plen 4 #328 [hci0] 55.790065
LE Set Scan Enable (0x08|0x000c) ncmd 1
Status: Success (0x00)
> HCI Event: LE Meta Event (0x3e) plen 31 #329 [hci0] 55.824088
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Public (0x00)
Address: 68:6C:E6:4D:45:A3 (Microsoft Corporation)
Data length: 19
Flags: 0x06
LE General Discoverable Mode
BR/EDR Not Supported
TX power: 20 dBm
Appearance: Gamepad (0x03c4)
Company: Microsoft (6)
Data[1]: 00
16-bit Service UUIDs (complete): 1 entry
Human Interface Device (0x1812)
RSSI: -48 dBm (0xd0)
< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2 #330 [hci0] 55.824140
Scanning: Disabled (0x00)
Filter duplicates: Disabled (0x00)
> HCI Event: Command Complete (0x0e) plen 4 #331 [hci0] 55.826064
LE Set Scan Enable (0x08|0x000c) ncmd 1
Status: Success (0x00)
< HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #332 [hci0] 55.826118
Filter policy: Accept list is not used (0x00)
Own address type: Public (0x00)
Peer address type: Public (0x00)
Peer address: 68:6C:E6:4D:45:A3 (Microsoft Corporation)
Initiating PHYs: 0x01
Entry 0: LE 1M
Scan interval: 60.000 msec (0x0060)
Scan window: 60.000 msec (0x0060)
Min connection interval: 30.00 msec (0x0018)
Max connection interval: 50.00 msec (0x0028)
Connection latency: 0 (0x0000)
Supervision timeout: 420 msec (0x002a)
Min connection length: 0.000 msec (0x0000)
Max connection length: 0.000 msec (0x0000)
> HCI Event: Command Status (0x0f) plen 4 #333 [hci0] 55.828067
LE Extended Create Connection (0x08|0x0043) ncmd 1
Status: Unknown HCI Command (0x01)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0002} [hci0] 55.828125
LE Address: 68:6C:E6:4D:45:A3 (Microsoft Corporation)
Status: Unknown Command (0x01)
@ MGMT Event: Connect Failed (0x000d) plen 8 {0x0001} [hci0] 55.828125
LE Address: 68:6C:E6:4D:45:A3 (Microsoft Corporation)
Status: Unknown Command (0x01)
@ MGMT Event: Command Complete (0x0001) plen 10 {0x0001} [hci0] 55.858112
Pair Device (0x0019) plen 7
Status: Unknown Command (0x01)
LE Address: 68:6C:E6:4D:45:A3 (Microsoft Corporation)
bluetoothctl[242736]: @ MGMT Close: bluetoothctl {0x0002} 82.484657
System Config
generic system config
inxi -zv8 (some unneccesary stuff removed)
System:
Kernel: 6.9.2-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.1.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz-6.9-x86_64
root=UUID=7b3ef6a3-6d66-4542-bc64-35a852f22534 rw quiet splash
resume=UUID=304e7af0-f073-4eb7-8a82-0f7f1b198d13 udev.log_priority=3
nvidia_drm.modeset=1 nvidia_drm.fbdev=1
Desktop: KDE Plasma v: 6.0.5 tk: Qt v: N/A wm: kwin_x11 dm: SDDM
Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-F GAMING v: Rev 1.xx
serial: <filter> part-nu: SKU uuid: 5e1c0096-b350-385e-cbab-d45d64501a1d
UEFI: American Megatrends v: 2901 date: 10/16/2019
PCI Slots:
Slot: 0 type: PCIe lanes: 1 status: in use length: short volts: 3.3
bus-ID: 02:01.0
Slot: 1 type: PCIe lanes: 16 status: in use length: long volts: 3.3
bus-ID: 00:03.1 children: 1: 08:00.0 class-ID: 0300 type: display 2: 08:00.1
class-ID: 0403 type: audio
CPU:
Info: model: AMD Ryzen 9 3900X socket: AM4 bits: 64 type: MT MCP arch: Zen 2
gen: 3 level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701013
Graphics:
Device-1: NVIDIA GA104 [GeForce RTX 3070] driver: nvidia v: 550.78
alternate: nouveau,nvidia_drm non-free: 550.xx+ status: current (as of
2024-04; EOL~2026-12-xx) arch: Ampere code: GAxxx process: TSMC n7 (7nm)
built: 2020-2023 pcie: gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4
speed: 16 GT/s ports: active: none off: DP-1,DP-2 empty: DP-3,HDMI-A-1
bus-ID: 08:00.0 chip-ID: 10de:2484 class-ID: 0300
Device-2: Microdia USB 2.0 Camera driver: snd-usb-audio,uvcvideo type: USB
rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-6:5 chip-ID: 0c45:636b
class-ID: 0102 serial: <filter>
Display: server: X.Org v: 21.1.13 with: Xwayland v: 24.1.0
compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch
display-ID: :0 screens: 1
Screen-1: 0 s-res: 5120x1440 s-dpi: 92 s-size: 1414x393mm (55.67x15.47")
s-diag: 1468mm (57.78")
Monitor-1: DP-1 mapped: DP-0 note: disabled pos: right model: Dell S2417DG
serial: <filter> built: 2019 res: 2560x1440 dpi: 123 gamma: 1.2 chroma: red:
x: 0.639 y: 0.329 green: x: 0.298 y: 0.600 blue: x: 0.149 y: 0.059 white:
x: 0.314 y: 0.329 size: 527x296mm (20.75x11.65") diag: 604mm (23.8")
ratio: 16:9 modes: 2560x1440, 1024x768, 800x600, 640x480
Monitor-2: DP-2 note: disabled pos: primary,left
model: LG (GoldStar) ULTRAGEAR serial: <filter> built: 2022 res: 2560x1440
dpi: 93 gamma: 1.2 chroma: red: x: 0.647 y: 0.337 green: x: 0.314 y: 0.631
blue: x: 0.153 y: 0.075 white: x: 0.314 y: 0.329
size: 700x390mm (27.56x15.35") diag: 800mm (31.5") ratio: 16:9
modes: 2560x1440, 1920x1080, 1280x720, 1024x768, 800x600, 720x576,
720x480, 640x480
EDID-Warnings: 1: parse_edid: unknown tag 112
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.78
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 3070/PCIe/SSE2
memory: 7.81 GiB
API: Vulkan v: 1.3.279 layers: 1 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 3070 driver: nvidia v: 550.78 device-ID: 10de:2484
surfaces: xcb,xlib
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: 03:00.0
chip-ID: 8086:1539 class-ID: 0200
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic scope: global broadcast: <filter>
IP v6: <filter> type: noprefixroute scope: link
Device-2: Broadcom BCM4360 802.11ac Dual Band Wireless Network Adapter
driver: wl v: kernel modules: bcma pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 04:00.0 chip-ID: 14e4:43a0 class-ID: 0280
IF: wlp4s0 state: dormant mac: <filter>
Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
WAN IP: <filter>
Bluetooth:
Device-1: Actions general adapter driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-1:2 chip-ID: 10d7:b012
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
USB:
...
Device-1: 3-1:2 info: Actions general adapter type: bluetooth
driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
mode: 1.1 power: 100mA chip-ID: 10d7:b012 class-ID: e001 serial: <filter>
...
mhwd -li
Installed PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-nvidia 2024.05.03 false PCI
network-broadcom-wl 2018.10.07 false PCI
Warning: No installed USB configs!
mhwd -l
0000:08:00.0 (0300:10de:2484) Display controller nVidia Corporation:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-nvidia 2024.05.03 false PCI
video-nvidia-470xx 2023.03.23 false PCI
video-linux 2024.05.06 true PCI
video-modesetting 2020.01.13 true PCI
video-vesa 2017.03.12 true PCI
> 0000:04:00.0 (0200:14e4:43a0) Network controller Broadcom:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
network-broadcom-wl 2018.10.07 false PCI
mhwd-kernal -li
Currently running: 6.9.2-1-MANJARO (linux69)
The following kernels are installed in your system:
* linux61
* linux66
* linux69
specific system config about this problem
lsmod | grep xpad
hid_xpadneo 40960 0
xpad 49152 0
ff_memless 20480 2 xpad,hid_xpadneo
inxi -Ea
Bluetooth:
Device-1: Actions general adapter driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-1:2 chip-ID: 10d7:b012
class-ID: e001 serial: ACTIONS1234
Report: btmgmt ID: hci0 rfk-id: 3 state: up address: F4:4E:FC:89:3F:40
bt-v: 5.3 lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
lsmod | grep bt
btusb 86016 0
btrtl 32768 1 btusb
btintel 65536 1 btusb
btbcm 24576 1 btusb
btmtk 12288 1 btusb
bluetooth 1122304 34 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
rfkill
ID TYPE DEVICE SOFT HARD
0 wlan phy0 unblocked unblocked
3 bluetooth hci0 unblocked unblocked
My computer was originally Windows only. As of now I have 1 drive that is Windows only and 1 drive that is Manjaro only. It is “dual boot,” but they do not share any space on a single drive. On Windows, my BT dongle works perfectly fine with all my devices as well as my Xbox controller.
On Manjaro, my dongle worked when I paired it with a cheap BT speaker and also a third-party Nintendo Switch Pro controller. (link here)
I am using bluez with the associated packages/bluez-utils.
I am using a USB BT dongle. (link here) [I can’t post links. The one I have is no longer available but seems to be the same as XDO Class 1 bluetooth dongle on Amazon)]
My drivers for this are the standard btusb drivers that come with Manjaro. I don’t really know what chipset this thing is so I haven’t looked for any “better” drivers since everything else has worked so far.
My controller is a standard official Xbox Series X controller. (link here)
For drivers, I am using xpadneo which I installed by cloning the repo and running the install script. I don’t think this is coming into the picture however, since I think this only does something after the controller is paired/connected. I could be wrong, but I don’t know enough to know how to check that. dmesg didn’t show anything xpadneo related.