Version of xpadneo
v0.11-pre-7-gd67479f
Controller Model
Connection mode
Installed Software
Protocol Information
Please help us identify at which layer the problem can be found if you want
to report mapping errors or if the controller fails to be detected:
Please describe how it is failing below in the next sections.
Severity / Impact
Describe the Bug
During gameplay, the system will encounter a freeze and hard crash mid-controller rumble. The rumble persists during the freeze and stops once the system crashes and reboots on its own.
Steps to Reproduce
Play a game with rumble enabled. After a few minutes, the crash occurs. It doesn't happen on the very first rumble, but does happen about maybe 3-5 minutes into gameplay.
Expected Behavior
Rumble occurs with no system crashes.
Screenshots / GIFs / Videos
System Information
# uname -a
Linux mike-pi 6.12.75+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.75-1+rpt1 (2026-03-11) aarch64 GNU/Linux
# dmesg -H | egrep -i 'bt|bluetooth|hci|l2cap|att|xbox|045e|hid|input|xpadneo' | tee xpadneo-dmesg.txt
[ +0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 cgroup_disable=memory numa_policy=interleave nvme.max_host_mem_size_mb=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 numa=fake=1 system_heap.max_order=0 smsc95xx.macaddr=2C:CF:67:53:3E:F9 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyAMA0,115200 console=tty1 root=PARTUUID=d85d0070-02 rootfstype=ext4 fsck.repair=yes rootwait usbcore.autosuspend=-1 btusb.enable_autosuspend=0
[ +0.007312] raspberrypi-firmware soc:firmware: Attached to firmware from 2025-08-20T17:02:31, variant start
[ +0.091632] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ +0.000039] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
[ +0.000967] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0300240000000890
[ +0.000542] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ +0.000028] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[ +0.000031] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[ +0.000028] usb usb1: Product: xHCI Host Controller
[ +0.000021] usb usb1: Manufacturer: Linux 6.12.75+rpt-rpi-v8 xhci-hcd
[ +0.000029] usb usb2: Product: xHCI Host Controller
[ +0.000021] usb usb2: Manufacturer: Linux 6.12.75+rpt-rpi-v8 xhci-hcd
[ +0.001581] sdhci: Secure Digital Host Controller Interface driver
[ +0.000047] sdhci: Copyright(c) Pierre Ossman
[ +0.000100] sdhci-pltfm: SDHCI platform and OF driver helper
[ +0.000189] hid: raw HID events driver (C) Jiri Kosina
[ +0.000083] usbcore: registered new interface driver usbhid
[ +0.000024] usbhid: USB HID core driver
[ +0.031962] mmc0: SDHCI controller on fe340000.mmc [fe340000.mmc] using ADMA
[ +0.059218] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[Apr13 00:30] usb 1-1.3: new full-speed USB device number 3 using xhci_hcd
[ +0.062481] systemd[1]: systemd 257.9-1~deb13u1 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +IPE +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +BTF -XKBCOMMON -UTMP +SYSVINIT +LIBARCHIVE)
[ +0.000095] input: vc4-hdmi-0 as /devices/platform/soc/fef00700.hdmi/rc/rc0/input0
[ +0.002682] Bluetooth: Core ver 2.22
[ +0.000055] NET: Registered PF_BLUETOOTH protocol family
[ +0.000004] Bluetooth: HCI device and connection manager initialized
[ +0.000014] Bluetooth: HCI socket layer initialized
[ +0.000006] Bluetooth: L2CAP socket layer initialized
[ +0.000009] Bluetooth: SCO socket layer initialized
[ +0.000080] input: vc4-hdmi-0 HDMI Jack as /devices/platform/soc/fef00700.hdmi/sound/card1/input1
[ +0.000120] input: vc4-hdmi-1 as /devices/platform/soc/fef05700.hdmi/rc/rc1/input2
[ +0.020160] input: vc4-hdmi-1 HDMI Jack as /devices/platform/soc/fef05700.hdmi/sound/card2/input3
[ +0.023726] usbcore: registered new interface driver btusb
[ +0.004769] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761
[ +0.003030] Bluetooth: hci0: RTL: rom_version status=0 version=1
[ +0.002970] Bluetooth: hci0: RTL: btrtl_initialize: key id 0
[ +0.000018] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin
[ +0.013011] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin
[ +0.007963] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210
[ +0.370100] Bluetooth: hci0: RTL: fw version 0xdfc6d922
[ +1.884882] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ +0.000019] Bluetooth: BNEP filters: protocol multicast
[ +0.000015] Bluetooth: BNEP socket layer initialized
[ +0.006580] Bluetooth: MGMT ver 1.23
[ +0.303645] Bluetooth: RFCOMM TTY layer initialized
[ +0.000028] Bluetooth: RFCOMM socket layer initialized
[ +0.000018] Bluetooth: RFCOMM ver 1.11
[ +2.578744] input: Xbox Wireless Controller as /devices/virtual/misc/uhid/0005:045E:0B13.0001/input/input4
[ +0.001246] hid-generic 0005:045E:0B13.0001: input,hidraw0: BLUETOOTH HID v5.23 Gamepad [Xbox Wireless Controller] on e0:d3:62:64:6c:13
[ +0.008484] hid_xpadneo: loading out-of-tree module taints kernel.
[ +0.000725] loaded hid-xpadneo v0.11-pre-7-gd67479f
[ +0.067920] xpadneo 0005:045E:0B13.0001: BLE firmware version 5.23
[ +0.000020] xpadneo 0005:045E:0B13.0001: pretending XB1S Windows wireless mode (changed PID from 0x0B13 to 0x028E)
[ +0.000006] xpadneo 0005:045E:0B13.0001: working around wrong SDL2 mappings (changed version from 0x00000523 to 0x00001130)
[ +0.000007] xpadneo 0005:045E:0B13.0001: report descriptor size: 283 bytes
[ +0.000005] xpadneo 0005:045E:0B13.0001: fixing up Rx axis
[ +0.000003] xpadneo 0005:045E:0B13.0001: fixing up Ry axis
[ +0.000003] xpadneo 0005:045E:0B13.0001: fixing up Z axis
[ +0.000004] xpadneo 0005:045E:0B13.0001: fixing up Rz axis
[ +0.000003] xpadneo 0005:045E:0B13.0001: fixing up button mapping
[ +0.000709] xpadneo 0005:045E:0B13.0001: gamepad detected
[ +0.000010] xpadneo 0005:045E:0B13.0001: enabling compliance with Linux Gamepad Specification
[ +0.000118] input: Xbox Wireless Controller as /devices/virtual/misc/uhid/0005:045E:0B13.0001/input/input5
[ +0.000797] xpadneo 0005:045E:0B13.0001: input,hidraw0: BLUETOOTH HID v11.30 Gamepad [Xbox Wireless Controller] on e0:d3:62:64:6c:13
[ +0.000127] input: Xbox Wireless Controller Consumer Control as /devices/virtual/misc/uhid/0005:045E:0B13.0001/input/input6
[ +0.000122] xpadneo 0005:045E:0B13.0001: consumer control added
[ +0.000066] input: Xbox Wireless Controller Keyboard as /devices/virtual/misc/uhid/0005:045E:0B13.0001/input/input7
[ +0.000371] xpadneo 0005:045E:0B13.0001: keyboard added
[ +0.000084] input: Xbox Wireless Controller Mouse as /devices/virtual/misc/uhid/0005:045E:0B13.0001/input/input8
[ +0.000325] xpadneo 0005:045E:0B13.0001: mouse added
[ +0.000019] xpadneo 0005:045E:0B13.0001: controller quirks: 0x00000050
[ +0.000008] xpadneo rumble_welcome start
[ +0.000004] xpadneo 0005:045E:0B13.0001: testing weak motor: sustain 50ms release 50ms loop 2 wait 30ms
[ +0.330057] xpadneo 0005:045E:0B13.0001: testing strong motor: sustain 50ms release 50ms loop 2 wait 30ms
[ +0.129793] xpadneo 0005:045E:0B13.0001: testing trigger motors: sustain 50ms release 50ms loop 2 wait 30ms
[ +0.330117] xpadneo rumble_welcome took 992ms
[ +0.000023] xpadneo 0005:045E:0B13.0001: Xbox Wireless Controller [44:16:22:d0:61:72] connected
[ +0.050598] xpadneo 0005:045E:0B13.0001: reverting to original version (changed version from 0x00001130 to 0x00000523)
[ +0.000018] xpadneo 0005:045E:0B13.0001: reverting to original product (changed PID from 0x028E to 0x0B13)
[ +0.000009] xpadneo 0005:045E:0B13.0001: removing controller quirks: 0x00000050
[ +0.000005] xpadneo 0005:045E:0B13.0001: battery removed
[ +0.054118] xpadneo 0005:045E:0B13.0001: mouse removed
[ +0.055990] xpadneo 0005:045E:0B13.0001: keyboard removed
[ +0.024020] xpadneo 0005:045E:0B13.0001: consumer control removed
[ +0.064536] xpadneo 0005:045E:0B13.0001: BLE firmware version 5.23
[ +0.000014] xpadneo 0005:045E:0B13.0001: pretending XB1S Windows wireless mode (changed PID from 0x0B13 to 0x028E)
[ +0.000005] xpadneo 0005:045E:0B13.0001: working around wrong SDL2 mappings (changed version from 0x00000523 to 0x00001130)
[ +0.000005] xpadneo 0005:045E:0B13.0001: report descriptor size: 283 bytes
[ +0.000005] xpadneo 0005:045E:0B13.0001: fixing up Rx axis
[ +0.000003] xpadneo 0005:045E:0B13.0001: fixing up Ry axis
[ +0.000003] xpadneo 0005:045E:0B13.0001: fixing up Z axis
[ +0.000004] xpadneo 0005:045E:0B13.0001: fixing up Rz axis
[ +0.000003] xpadneo 0005:045E:0B13.0001: fixing up button mapping
[ +0.000681] xpadneo 0005:045E:0B13.0001: gamepad detected
[ +0.000005] xpadneo 0005:045E:0B13.0001: enabling compliance with Linux Gamepad Specification
[ +0.000095] input: Xbox Wireless Controller as /devices/virtual/misc/uhid/0005:045E:0B13.0001/input/input9
[ +0.000218] xpadneo 0005:045E:0B13.0001: input,hidraw0: BLUETOOTH HID v11.30 Gamepad [Xbox Wireless Controller] on e0:d3:62:64:6c:13
[ +0.000065] input: Xbox Wireless Controller Consumer Control as /devices/virtual/misc/uhid/0005:045E:0B13.0001/input/input10
[ +0.000056] xpadneo 0005:045E:0B13.0001: consumer control added
[ +0.000055] input: Xbox Wireless Controller Keyboard as /devices/virtual/misc/uhid/0005:045E:0B13.0001/input/input11
[ +0.000053] xpadneo 0005:045E:0B13.0001: keyboard added
[ +0.000065] input: Xbox Wireless Controller Mouse as /devices/virtual/misc/uhid/0005:045E:0B13.0001/input/input12
[ +0.000102] xpadneo 0005:045E:0B13.0001: mouse added
[ +0.000011] xpadneo 0005:045E:0B13.0001: controller quirks: 0x00000050
[ +0.000005] xpadneo rumble_welcome start
[ +0.000004] xpadneo 0005:045E:0B13.0001: testing weak motor: sustain 50ms release 50ms loop 2 wait 30ms
[ +0.330040] xpadneo 0005:045E:0B13.0001: testing strong motor: sustain 50ms release 50ms loop 2 wait 30ms
[ +0.330048] xpadneo 0005:045E:0B13.0001: testing trigger motors: sustain 50ms release 50ms loop 2 wait 30ms
[ +0.330041] xpadneo rumble_welcome took 992ms
[ +0.000015] xpadneo 0005:045E:0B13.0001: Xbox Wireless Controller [44:16:22:d0:61:72] connected
Controller and Bluetooth Information
xpadneo-btmon.txt
xpadneo-dmesg.txt
xpadneo-lsusb.txt
Additional Context
Here is my setup:
-
Raspberry Pi 4 running Moonlight, which connects to a Windows 11 host PC running Apollo(Sunshine).
-
The Raspberry Pi streams games from the PC via the Apollo/Moonlight stream with controller rumble passed through.
-
The Xbox Series X controller that I use is connected to the Raspberry Pi client via a Bluetooth connection.
-
The Bluetooth connection is handled via the TP Link USB dongle, which is connected to the Raspberry Pi 4.
Version of xpadneo
v0.11-pre-7-gd67479f
Controller Model
Connection mode
Installed Software
Protocol Information
Please help us identify at which layer the problem can be found if you want
to report mapping errors or if the controller fails to be detected:
Games are being run through Sunshine(Apollo) and Moonlight
evtestis showing issues (describe the issues below)BTN_NORTHandBTN_WESTare intentionally swappedjstestis showing issues (describe the issues below)gamepad-toolis showing issues (post console output below)Please describe how it is failing below in the next sections.
Severity / Impact
Describe the Bug
During gameplay, the system will encounter a freeze and hard crash mid-controller rumble. The rumble persists during the freeze and stops once the system crashes and reboots on its own.
Steps to Reproduce
Play a game with rumble enabled. After a few minutes, the crash occurs. It doesn't happen on the very first rumble, but does happen about maybe 3-5 minutes into gameplay.
Expected Behavior
Rumble occurs with no system crashes.
Screenshots / GIFs / Videos
System Information
Controller and Bluetooth Information
xpadneo-btmon.txt
xpadneo-dmesg.txt
xpadneo-lsusb.txt
Additional Context
Here is my setup:
Raspberry Pi 4 running Moonlight, which connects to a Windows 11 host PC running Apollo(Sunshine).
The Raspberry Pi streams games from the PC via the Apollo/Moonlight stream with controller rumble passed through.
The Xbox Series X controller that I use is connected to the Raspberry Pi client via a Bluetooth connection.
The Bluetooth connection is handled via the TP Link USB dongle, which is connected to the Raspberry Pi 4.