Controller rumble has stopped working #461
Comments
|
Try Also, controllers usually disable rumble when battery runs low: Did you charge the controller? |
|
Closing as duplicate of #444 |
|
Sorry - this is an issue separate to that. Rumble no longer works regardless of the status of that setting. |
@RobotRoss Can you try the steps outlined in #462 (comment) (hidraw tester), and reply back here? |
|
I think I may have randomly stumbled into what may be causing the issue, seems like xpadneo isn't always taking control of the controller, so the generic kernel driver is used instead (which doesn't support rumble) dmesg output when rumble doesn't work: dmesg when rumble does work: |
|
Strange,i have same problem but dmesg is [ 154.324257] xpadneo 0005:045E:02FD.0003: Xbox Wireless Controller [98:b6:ea:40:7b:c0] connected
[ 169.437251] xpadneo 0005:045E:02FD.0003: reverting to original version (changed version from 0x00001130 to 0x00000903)
[ 169.437263] xpadneo 0005:045E:02FD.0003: reverting to original product (changed PID from 0x028E to 0x02FD)
[ 288.005364] xpadneo 0005:045E:02FD.0004: buggy firmware detected, please upgrade to the latest version
[ 288.005376] xpadneo 0005:045E:02FD.0004: pretending XB1S Windows wireless mode (changed PID from 0x02FD to 0x028E)
[ 288.005382] xpadneo 0005:045E:02FD.0004: working around wrong SDL2 mappings (changed version from 0x00000903 to 0x00001130)
[ 288.005389] xpadneo 0005:045E:02FD.0004: report descriptor size: 335 bytes
[ 288.005394] xpadneo 0005:045E:02FD.0004: fixing up report descriptor size
[ 288.005397] xpadneo 0005:045E:02FD.0004: fixing up Rx axis
[ 288.005401] xpadneo 0005:045E:02FD.0004: fixing up Ry axis
[ 288.005405] xpadneo 0005:045E:02FD.0004: fixing up Z axis
[ 288.005408] xpadneo 0005:045E:02FD.0004: fixing up Rz axis
[ 288.005412] xpadneo 0005:045E:02FD.0004: fixing up button mapping
[ 288.005734] xpadneo 0005:045E:02FD.0004: battery detected
[ 288.005737] xpadneo 0005:045E:02FD.0004: gamepad detected
[ 288.005739] xpadneo 0005:045E:02FD.0004: enabling compliance with Linux Gamepad Specification
[ 288.005797] input: Xbox Wireless Controller as /devices/pci0000:00/0000:00:08.1/0000:03:00.4/usb3/3-4/3-4:1.0/bluetooth/hci0/hci0:4/0005:045E:02FD.0004/input/input28
[ 288.006506] xpadneo 0005:045E:02FD.0004: consumer control detected
[ 288.006562] input: Xbox Wireless Controller Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:03:00.4/usb3/3-4/3-4:1.0/bluetooth/hci0/hci0:4/0005:045E:02FD.0004/input/input29
[ 288.006845] xpadneo 0005:045E:02FD.0004: input,hidraw1: BLUETOOTH HID v11.30 Gamepad [Xbox Wireless Controller] on 74:4c:a1:c9:e1:5e
[ 288.006980] input: Xbox Wireless Controller Keyboard as /devices/pci0000:00/0000:00:08.1/0000:03:00.4/usb3/3-4/3-4:1.0/bluetooth/hci0/hci0:4/0005:045E:02FD.0004/input/input30
[ 288.007122] xpadneo 0005:045E:02FD.0004: keyboard added
[ 288.007132] xpadneo 0005:045E:02FD.0004: controller quirks: 0x00000095
[ 288.007138] xpadneo xpadneo_welcome_rumble start
[ 288.998128] xpadneo xpadneo_welcome_rumble took 990ms
[ 288.998178] xpadneo 0005:045E:02FD.0004: Xbox Wireless Controller [98:b6:ea:40:7b:c0] connectedVibration in hidraw working |
Try If this works, try the Maybe also try |
|
Please re-open, if the latest commit doesn't fix your problem. |
|
The bug hasn't been patched by the latest commit. Vibration in hidraw works fine, but game rumble doesn't work. Occasionally game rumble might work, but I'd say that there's a 90% chance when connecting the controller that it doesn't. Rumble works consistently on a Dualshock 4 that I also have over bluetooth, and works in games okay. Another couple dmesg samples: |
This looks like Steam Input is taking over the controller. But this looks the same in the other log, so really the problem is with How did you install xpadneo? Did you use direct dkms install from source repository, or are you using a distribution package? Ensure that these files (https://github.com/atar-axis/xpadneo/tree/master/hid-xpadneo/etc-udev-rules.d) exist in either of the following directories:
After you confirmed your system state, we can proceed with diagnosing your situation. |
|
I'm using the dkms install via source. The udev rules are present in the correct directory and aren't duplicated. |
|
Then please turn the controller off and reboot the system, so we end up with a clean initial state. Now run The last or one of the last blocks should have something like I'm not sure if I can already see a problem here. Maybe you'll have to repeat this for the other case when we see only Thanks. |
|
I've attached the requested files. I couldn't find anything under dmesg: Weirdly, my following attempt to connect did work. dmesg: |
|
Is it possible that only the first connect after a reboot ends up in the If yes, please try adding the following file if your system uses Then reboot. I'd expect that now xpadneo correctly binds on the first connect. Other problems about making successful connections at all should probably attributed to bluez and your Intel Wireless chipset instead and should be reported to the bluez project if you still experience that. As long as xpadneo correctly binds to the device, rumble should work. Please test. |
Unfortunately not. It's seemingly random if rumble decides it wants to work or not, although mostly it doesn't work with occasional times it decides to work. |
|
Maybe something is working concurrently on your system and races... Is |
|
Compiled in kernel by the look of it: |
|
No, it's compiled as a module (but yes, as part of the kernel distribution, IOW, not an external module), otherwise it would say: So if you don't depend on any other Microsoft input devices, you could try blacklisting the module (as a work-around, not a final solution): Then run Devices affected by this would still work via |
|
One other thing, please check if this file (https://github.com/atar-axis/xpadneo/blob/master/hid-xpadneo/etc-modprobe.d/xpadneo.conf) has been installed in these directories without duplicates, and identical contents:
It should ensure that In your logs I can see the modalias showing in udev, so it should trigger loading xpadneo. I'd expect to see it loading as soon as the modalias shows up, but it only loads at bind time when already gone through |
Turns out there was a duplicate xpadneo.conf in /etc/modprobe.d which didn't match the contents of the github file. Have deleted the duplicate and will report back. |
|
Near as I can tell, this issue is now resolved and I haven't had any more issues with the controller in the past couple weeks. Closing! |
Version of xpadneo
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:
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
Gamepad rumble no longer seems to work as of the past day or so. Not sure what's changed - haven't done any system updates that might cause it to stop working. Tried a clean reinstall of xpadneo using the latest git, same problem.
Rumble support is advertised, but does not work.
Steps to Reproduce
Connect controller via Bluetooth, test rumble in a game or via gamepad tester.
Expected Behavior
Rumble to work.
Screenshots / GIFs / Videos
System Information
Controller and Bluetooth Information
Additional Context
xpadneo-btmon.txt
xpadneo-dmesg.txt
xpadneo-lsusb.txt
The text was updated successfully, but these errors were encountered: