Hi and welcome to my thread regarding my problem using an xbox360 wireless controller through xboxdrv with xbmcubuntu.
I must warn that I am not a linux expert but I believe I can think relatively logically and I am able to follow instructions.
I had this working before with an older versions of xbmcubuntu and perhaps xboxdrv, and I think I've done the same things that I did back then - and I still can only get the mapped KEY-events to work - not the mapped BTN-events (Yes, I have some buttons mapped as joypad events and others as keyboard events at the same time). Back in the day everything worked.
I've recently done a fresh install on my mediacenter with the following livecd from xbmcfreak.nl.
XBMCbuntu 12.04 with pre-Frodo (end October release)
I installed xboxdrv as mentioned in this thread which was instrumental in my previous success:
http://forum.xbmc.org/showthread.php?tid=99344 (I just assume that this method is still correct)
I booted xbmc and the gamepad didn't work. I tried starting the xboxdrv manually and get this message:
"Error couldn't claim the USB interface: LIBUSB_ERROR_BUSY"
The error message kindly suggest that I rmod xpad - which I do (I have to sudo)
I run it agan with the -c "path to my config" and it kinda works - but ONLY KEY events not BTN events.
So I have this one problem with starting the driver - "things must have changed", if you know what I mean..., but I look at this as a "first world's problems". Right now, I just need help getting everything working correctly.
Somehow the left thumbstick now acts as mouse. I don't know why that is either - it didn't use to.
this is my config:
ui-clear = true
device-name = "Microsoft Xbox 360 Wireless Controller (PC)"
Please help. If I haven't provided enough info I will get what is needed. It might be obvious to some, but certainly not to me.
Xboxdrv in xbmc BTN-events doesn't work KEY-events does?
Joined: Nov 2012
2012-11-03 13:50 Post: #1
Joined: Nov 2012
2012-11-04 01:13 Post: #2
Well I found the solution. My startup script starting the driver wasn't working properly - I was already aware of that. What I didn't know until through random luck after searching high and low was that if the driver is started AFTER Xbmc (which it was in my case) - stuff wouldn't work in xbmc. Restarting XBMC made everything work again.
Kinda lame really, but thankfully stuff works now.