Xbox 360 Controller in Feisty

[KSI]

At risk of looking like an idiot, I'm bumping this. I've installed the xp360 files, ran modprobe, restarted, unplugged and replugged and I've yet to get the controller to work. Using a Joytech Advanced controller. Yes, I editted xpad.c to reflect this.

sudo tail -fn0 /var/log/messages

josh-laptop kernel: [  181.671217] usb 1-1: USB disconnect, address 3
Sep  3 13:57:55 josh-laptop kernel: [  184.580216] usb 1-1: new full speed USB device using ohci_hcd and address 4
Sep  3 13:57:55 josh-laptop kernel: [  184.688772] usb 1-1: configuration #1 chosen from 1 choice

After this, it lists my eth0 devices.

lsusb

Bus 003 Device 005: ID 059b:0272 Iomega Corp. 
Bus 003 Device 004: ID 1058:0903 Western Digital Technologies, Inc. 
Bus 003 Device 003: ID 05e3:0608 Genesys Logic, Inc. 
Bus 003 Device 001: ID 0000:0000  
Bus 002 Device 002: ID 1241:1166 Belkin 
Bus 002 Device 001: ID 0000:0000  
Bus 001 Device 004: ID 162e:beef  
Bus 001 Device 001: ID 0000:0000

Top three are extranals. Belkin is a mouse. No idea what 001/004 is.

udevinfo -q all -a -p /class/input/input7 | tee udev-output.txt

  looking at device '/class/input/input7':
    KERNEL=="input7"
    SUBSYSTEM=="input"
    DRIVER==""
    ATTR{modalias}=="input:b0019v0000p0005e0000-e0,5,kramlsfw0,"
    ATTR{uniq}==""
    ATTR{phys}=="PNP0C0D/button/input0"
    ATTR{name}=="Lid Switch"

That's the only one it gives me.

Does not recognize dev/input/js*

Just wondering if I missed anything or if I should toss this controller out and go get a proprietary one.

[po0f]

SeanS / KSI,

Try the following, please:

$ sudo modprobe -r xpad
$ sudo update-modules && sudo depmod

Reboot if you feel like it (not needed, I just checked), and run the `sudo tail...` command and try plugging your controller in. Hopefully it recognizes it.

I just did a fresh install 2 weeks ago and I'm just now getting around to installing the xpad360 module. At first it wasn't working. Couldn't for the life of me figure out why. Turns out I forgot to run `depmod`. I don't know if I mentioned having to run this command earlier; if not, OOPS!

[KSI]

With a fresh copy of the files:

josh@josh-laptop:~$ cd xpad360
josh@josh-laptop:~/xpad360$ make
make modules -C /lib/modules/2.6.20-16-generic/build SUBDIRS=/home/josh/xpad360
make[1]: Entering directory `/usr/src/linux-headers-2.6.20-16-generic'
  CC [M]  /home/josh/xpad360/xpad.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /home/josh/xpad360/xpad.mod.o
  LD [M]  /home/josh/xpad360/xpad.ko
make[1]: Leaving directory `/usr/src/linux-headers-2.6.20-16-generic'
josh@josh-laptop:~/xpad360$ sudo make install
mv -f xpad.ko /lib/modules/2.6.20-16-generic/kernel/drivers/usb/input
josh@josh-laptop:~/xpad360$ sudo modprobe -r xpad
josh@josh-laptop:~/xpad360$ sudo update-modules
josh@josh-laptop:~/xpad360$ sudo depmod
josh@josh-laptop:~/xpad360$ sudo tail -fn0 /var/log/messages
Sep  4 19:39:21 josh-laptop kernel: [  632.142511] usb 1-1: USB disconnect, address 4
Sep  4 19:39:22 josh-laptop kernel: [  632.902244] usb 1-1: new full speed USB device using ohci_hcd and address 5
Sep  4 19:39:22 josh-laptop kernel: [  633.010827] usb 1-1: configuration #1 chosen from 1 choice

Then it's back to the eth0 traffic.

[po0f]

KSI,

Weird. Would you mind uploading the source files you're using?

[KSI]

Just using the ones you attached on page one.

[paxmaniac]

In case anyone is trying to get this working in Gutsy, you need to know that the joystick modules now go in:

/lib/modules/$(shell uname -r)/kernel/drivers/input/joystick

(instead of drivers/usb/input), so you need to change the makefile accordingly.

[loctorn]

KSI,

I'm having the same problem as you.....I even went as far as to completely trash my system and go through the entire process again still with no luck. jscalibration show's it's there and that other function (forgot what it was) gives me some garble trash message once it's ran so I dunno what else to do till someone else figures it out.

I just started using Ubuntu Feisty Fawn about 1 week ago and don't plan on having to continuously install/reinstall to see if I can get this to work.

So if anyone is lucky enough to do so please post here as to EXACTLY what files and exact word for word install you done that way if that doesn't work I won't feel so bad when I bash my 360 controller on the asphault.

Thanks

[Surkow]

In case anyone is trying to get this working in Gutsy, you need to know that the joystick modules now go in:

/lib/modules/$(shell uname -r)/kernel/drivers/input/joystick

(instead of drivers/usb/input), so you need to change the makefile accordingly.

I just wanted to post the same. After this I'm finally getting some feedback from jscalibrator.

Edit: not all programs recognize the LT and the RT buttons as pressure buttons. I can't seem to get mupen64 to recognize the buttons (not even like a normal button). Sadly enough PCSX2 doesn't get any feedback from the controller at all.

[paxmaniac]

Edit: not all programs recognize the LT and the RT buttons as pressure buttons. I can't seem to get mupen64 to recognize the buttons (not even like a normal button). Sadly enough PCSX2 doesn't get any feedback from the controller at all.

Did they work under Feisty?

The LT and RT 'triggers' are registered, not as buttons, but as axes (indices 4 and 5). Any program should be able to access these if they look at the right index. Is PCSX2 looking at the right device file (e.g /dev/input/js0)? Some programs will look for /dev/js0 by default so you may have to use a symbolic link e.g:

sudo ln -s /dev/input/js0 /dev/js0

[Surkow]

Did they work under Feisty?

The LT and RT 'triggers' are registered, not as buttons, but as axes (indices 4 and 5). Any program should be able to access these if they look at the right index. Is PCSX2 looking at the right device file (e.g /dev/input/js0)? Some programs will look for /dev/js0 by default so you may have to use a symbolic link e.g:

sudo ln -s /dev/input/js0 /dev/js0

I already found out they were registered as axes (see this thread). I will try to create a symbolic link. Hopefully it can be solved as easily as that.

Edit: the symbolic link didn't work.