xbox 360 controller not recognized properly

white_gecko

Since I've updated retropi to 3.8.1 my xbox 360 wireless controller doesn't work properly. The controller connects correctly and it shows the upper left LED (Player 1) but I don't get any action if I press the buttons.
When I first started the retropi I was able to configure the buttons, using the default xbox driver and then I've enabled the other xbox driver as explained in the wiki (https://github.com/RetroPie/RetroPie-Setup/wiki/Setting-up-the-XBox360-controller) and could configure the buttons as well, but after some restarts it stoped working.
If I start the raspberry with the wireless connector disconnect, and connect it once the console is running the controller works, but I think the "old" xbox driver is used, since the LEDS are flashing.

white_gecko

I think that in the cases that the controller works the xpad kernel driver is used, while it doesn't work when the xboxdrv userspace driver is used. Is there any way of debugging this?

---edit---

If now tried to debug the issue by uncommenting the line in /etc/rc.local and run it manually.
Before I start xboxdrv userspace driver the controller works, but the LED blinks.
When I start the xboxdrv driver with the following command (as in /etc/rc.local except for silent, daemon and detach options) the controller shows correctly the led for player one but stops working.

---code---
$ sudo "/opt/retropie/supplementary/xboxdrv/bin/xboxdrv" --dbus disabled --detach-kernel-driver --id 0 --led 2 --deadzone 4000 --trigger-as-button
xboxdrv 0.8.8 - http://pingus.seul.org/~grumbel/xboxdrv/
Copyright © 2008-2011 Ingo Ruhnke grumbel@gmail.com
Licensed under GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details.

Controller: Xbox 360 Wireless Receiver
Vendor/Product: 045e:0719
USB Path: 001:004
Wireless Port: 0
Controller Type: Xbox360 (wireless)

Your Xbox/Xbox360 controller should now be available as:
/dev/input/js1
/dev/input/event1

Press Ctrl-C to quit, use '--silent' to suppress the event output
Shutdown complete
---end code---

why does it end with "Shutdown complete". Is there any way of seeing the commands/key-presses coming from the controller?

dmesg shows this line:

[ 215.342197] input: Xbox Gamepad (userspace driver) as /devices/virtual/input/input5

---edit 2---
If I start the xboxdrv multiple times from the console, sometimes it stops emidietly with "Shotdown complete", sometimes it also outputs an event. Sometimes it doesn't stop and I see a lot of events and it is working in the menu as well.

Also in some cases, when it works I get the following message before the events are output to the screen:

[ERROR] USBController::on_write_data(): USB write failure: 12: LIBUSB_TRANSFER_ERROR
---end edit 2---

---edit 3---
If I enable the verbose mode I see, that the shutdown Method is triggered:

xboxdrv 0.8.8 - http://pingus.seul.org/~grumbel/xboxdrv/
Copyright © 2008-2011 Ingo Ruhnke grumbel@gmail.com
Licensed under GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it under certain
conditions; see the file COPYING for details.

Controller: Xbox 360 Wireless Receiver
Vendor/Product: 045e:0719
USB Path: 001:004
Wireless Port: 0
Controller Type: Xbox360 (wireless)

Your Xbox/Xbox360 controller should now be available as:
/dev/input/js1
/dev/input/event1

Press Ctrl-C to quit, use '--silent' to suppress the event output
[INFO] XboxdrvMain::shutdown(): shutdown requested
Shutdown complete

---end edit3---

white_gecko

Now I've recompiled it from source and also enabled debug mode and I get:

[ERROR] USBController::on_read_data(): USB read failure: 32: LIBUSB_TRANSFER_ERROR

:-\

BuZz

It's an issue with the current kernel and the xboxdrv driver. However the xpad driver works - the LED blinking was due to a missing kernel config option, which has been added, but the new kernel has not yet been packaged for Raspbian. You can get it manually using rpi-update though or ignore the LED flash.

white_gecko

Thank you for your answer.
What exactly are the problems with the current kernel there? Could you maybe point me to the relevant discussion?