Kernel 6.17 regression - Bluetooth X-Input controller connects but no input until USB replug

Support Kernel
1

System

  • Distribution: Manjaro Linux (stable)
  • Kernel: 6.17.11-1-MANJARO
  • Desktop: Cinnamon
  • Bluetooth adapter: TP-Link USB Bluetooth adapter (Realtek RTL8761, btusb)
  • Controller: 8BitDo Pro 2 (Bluetooth, X-Input / Xbox mode)
  • Steam: used, but issue occurs independent of Steam

Regression

This is a kernel regression.

Working

  • Kernel 6.6 LTS
  • Kernel 6.16.x

Broken

  • Kernel 6.17.x

Problem description

The controller successfully pairs and connects over Bluetooth:

  • solid LED
  • vibration feedback on connect

However, no functional input device is created.
No input is received and Steam does not detect the controller.

After unplugging and replugging the USB Bluetooth adapter, the controller is
immediately detected and works normally.

Bluetooth mouse and keyboard work correctly at all times.

Steps to reproduce

  1. Boot system with kernel 6.17.x
  2. Power on the controller (before or after boot)
  3. Controller connects (LED + vibration), but no input works
  4. Unplug USB Bluetooth adapter
  5. Plug adapter back in
  6. Controller works immediately

Expected result

Bluetooth X-Input controller should create a working input device when connected.

Actual result

Controller connects, but no functional input device exists until USB replug.

Additional information

  • The controller appears to be connected at the Bluetooth level, but the input
    path is not functional.
  • Replugging the USB Bluetooth adapter triggers a full reinitialization and fixes
    the issue immediately.
  • dmesg logs before and after USB replug are attached.

I can test with a mainline kernel or provide additional logs if needed.

2

Welcome to the Forum.

The Latest LTS Kernel is 6.18.x, can you install that and test this issue on that?

3

Kernel 6.18 has been installed successfully (linux618 + headers) and is available in GRUB.

Rebooting now to test and will report back with results.

4

Tested with kernel 6.18.0-1-MANJARO.

The issue is fixed there.
The Bluetooth X-Input controller is initialized correctly on boot, no USB replug required.

A working input device is created immediately (js and evdev present), and the
controller binds to the expected microsoft HID driver.

THX

5

No worries, please mark the post that you found most helpful, as the solution.

6

Small follow-up after further testing.

After a cold boot this morning, Bluetooth did not initialize correctly,
even on kernel 6.18.
This affected not only the controller but also Bluetooth keyboard and mouse.

A USB replug of the Bluetooth adapter (Unplug Wait Replug Works) immediately restores functionality,
after which all devices connect and work as expected.

Summary:

  • Kernel: 6.18.0-1-MANJARO
  • Cold boot: Bluetooth not functional
  • USB replug: Bluetooth stack initializes correctly
  • Behavior matches the previous regression pattern, but is less frequent

This suggests the issue may not be fully resolved yet and could be related to
a timing or initialization order problem during cold boot.

I can try to gather boot-time dmesg logs if that helps.

7

Yes, someone should be able to make sense of the logs. I’ll remove the solved, if that is possible.

Did it all work OK on 6.12.x, if so you could roll back to that… it is an LTS.

8

Saw that there was an release of a new 6.17.11.2 Kernel and 6.18.1-1 I will check them all out.

1 Like
9

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.