search

atar-axis / xpadneo

Advanced Linux Driver for Xbox One Wireless Controller (shipped with Xbox One S)
https://atar-axis.github.io/xpadneo/
GNU General Public License v3.0
2.01k stars 113 forks source link

Controller Connects with No Vibration #101

Closed dhasial closed 5 years ago

dhasial commented 5 years ago

Controller connects, but doesn't rumble and input isn't working anywhere (tried Cemu through Playonlinux and multiple Steam games) after previously working fine.

Steps to reproduce the behavior:

  1. Install Xpadneo 2.Wait for it to (seemingly randomly) happen

Expected the controller to rumble when connected and for input to work normally.

dmesg -wH https://pastebin.com/0xfDtikQ

I think this may be related to the Xpadneo driver being unsigned, but Secure Boot is turned off so I didn't think it would matter anyways. I tried running sudo /root/module-signing/one-time-setup to sign the module, but I got the error: command not found.

atar-axis commented 5 years ago

[ +0.000301] hid_xpadneo: n' invalid for parameterdisable_ff'

have you changed the disable_ff parameter?

please give me the output of cat /etc/modprobe.d/99-xpadneo-bluetooth.conf and ls /etc/modprobe.d/

dhasial commented 5 years ago

No I haven't, I've done nothing in the way of customization so far. What's strange is that xpadneo worked fine last night, and overnight (never rebooting the pc), it seems to have gotten this bug. It might be worth mentioning that I got this same bug on my previous Ubuntu installation as well, makes me wonder if it's something I've done.

cat /etc/modprobe.d/99-xpadneo-bluetooth.conf https://pastebin.com/458KbMkF

ls /etc/modprobe.d/ https://pastebin.com/88D9jBG5

atar-axis commented 5 years ago

Hum, could you scan your system with sudo grep -r "disable_ff" / please?

dhasial commented 5 years ago

sudo grep -r "disable_ff" / https://pastebin.com/Km6JzMfM

atar-axis commented 5 years ago

thanks, can you please sudo ./uninstall.sh, get the new version (master) and sudo ./install.sh it again? :)

dhasial commented 5 years ago

Wow, it works beautifully now! I feel like an idiot for it having such a simple solution :P What did you realize was wrong with it? I'd like to understand if you have the time.

atar-axis commented 5 years ago

We changed the behaviour of disable_ff, therefore we switched from a boolean type (y / n) to a numeric one. Your kernel complained about the n, which is not longer accepted since it has to be numeric now, so it was clear that there must be the n somewhere - and as you can see I have forgotten to change the default value in the configure script. :)

Wow, it works beautifully now!

Thank you for reporting this issue!