[Wine] Re: Getting gamepad to work, detection problems.
wineforum-user at winehq.org
Wed May 7 21:38:54 CDT 2008
> 000dom000 wrote:
> > sorry about that. in terminal the long output cuts off, is there a way to stop that? the short output doesn't give me enough info...
> lshal | less
> And look for your joystick's name. You need :
> input.device = '/dev/input/event0' (string)
> Where "0" will be some number.
> 000dom000 wrote:
> > also you said to find out which dev/input/event it is. isn't that what I use for native games. that is /dev/input/js1
> Yes and no. There are 2 joystick input interfaces - "Linux input" and "event device" aka evdev. Evdev is a newer interface. But most distros configured so you don't have direct access to those devices.
> You should find which device is it, and chmod it so Wine can use it.
Hi there, I'm brand new to Wine and these forums, and I've jumped into this thread because it seems like that with which I am dealing.
I have an Xbox360 guitar controller, for which I have compiled and installed working drivers in Linux (Ubuntu Hardy - Linux gnivler-desktop 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 GNU/Linux).
jscalibrate seems to confirm the controller driver is working on /dev/input/js0, and cat /dev/input/event8 shows response to the controller activity also.
I have no output to the debug command also, which I had to execute with winedbg substituted for WINEDEBUG since I have no command WINEDEBUG that I can find. I ran it with GH3.exe as the program.exe. Zero output after getting into and exiting the game.
Forgive my complete noob-ness in this regard. but you previously mentioned using chmod to make the device(s) usable by wine, and I tried this with 755 and 777 temporarily without any luck. Is there more required than just that? Like the DirectInput registry additions or similar?
Thanks for any and all help.
Here is the output of lshal | grep input.device (doesn't seem to show any names at all):
input.device = '/dev/input/event5' (string)
input.device = '/dev/input/event4' (string)
input.device = '/dev/input/event0' (string)
input.device = '/dev/input/event10' (string)
input.device = '/dev/input/event3' (string)
input.device = '/dev/input/event2' (string)
input.device = '/dev/input/event1' (string)
input.device = '/dev/input/event9' (string)
input.device = '/dev/input/event8' (string)
input.device = '/dev/input/event7' (string)
input.device = '/dev/input/event6' (string)
and dmesg | grep Xbox:
[ 2314.573844] input: Microsoft Xbox 360 Wireless Controller (PC) as /devices/pci0000:00/0000:00:0a.0/usb1/1-2/1-2:1.0/input/input15
[ 2314.629628] input: Microsoft Xbox 360 Wireless Controller (PC) as /devices/pci0000:00/0000:00:0a.0/usb1/1-2/1-2:1.2/input/input16
[ 2314.677579] input: Microsoft Xbox 360 Wireless Controller (PC) as /devices/pci0000:00/0000:00:0a.0/usb1/1-2/1-2:1.4/input/input17
[ 2314.741554] input: Microsoft Xbox 360 Wireless Controller (PC) as /devices/pci0000:00/0000:00:0a.0/usb1/1-2/1-2:1.6/input/input18
[ 2314.789501] /home/mason/xpad/xpad.c: driver for Xbox controllers v0.1.7
More information about the wine-users