Linux pad: Debian 3.0/kernel 2.4.20

[Gismo]

Hello,

I was thinking about writing under the software thread, but as I experience this problem trying to use my PSXtoUSB on ePSXe under Debian, I wrote here.

Well, basically, I followed the istructions in the readme file from padJoy (the ammoQ pad plugin). Once I upgraded my kernel to 2.4.20 (the previous 2.2.20-idepci doesn't have the joydev module), I gave these commands:

modprobe joydev
od -xw8 /dev/input/js0

but everytimes it gave/gives me an error: it couldn't found /dev/js0 (or js1 or js2 or js3, there'r these 4 in the /dev/input/ dir). So, which r the other commands to start my PSXtoUSB working :confused:? Striking, under RedHat 7.2 (I didn't remember the kernel version), all worked w/o big problems, as soon as I put the commands...

Thx, bye

[Gismo]

ok, after a Google search and a night spent making tests and tests and tests :eyes:, I solved the problem, I mean, a part of the problem..

now I can see the PSXtoUSB w/ the following commands (from ammoQ pad plugin readme):

modprobe joydev
od -xw8 /dev/input/js0

and I see a list of values everytime I press a button/direction (even for the analog knobs and even for the button do change digital/analog).

The problem, now, is another: I can't configure ammoQ pad plugin on ePSXe, the same w/ the lame0 and linuxappz pad plugins.

Could someone help me?

Thx, bye

[ammoQ]

what do you mean "I can't configure ammoQ pad plugin"?

write "/dev/input/js0" into the "Device file" field, then click on one of the buttons in the dialog; within 2 seconds, press the appropriate button on the pad.
It should write something like "A1-" or "B4" next to the button in the dialog.

[Gismo]

Originally posted by ammoQ
write "/dev/input/js0" into the "Device file" field, then click on one of the buttons in the dialog; within 2 seconds, press the appropriate button on the pad.
It should write something like "A1-" or "B4" next to the button in the dialog.

well, it's exact what I did, but I got no reponse from the gampad config window: I mean, once I click the button I want to configure, I can't configure it, because as I release it, it becomes "light grey", it doesn't remain "dark grey" waiting for an input (I don't know if u could understand, ammoQ, I know, but I can't explain better, sorry )

I notice that this happens everytime I write "/dev/" in the "Device file" field, if I don't write anything, the button stayed "dark grey" for about 2 seconds. As I'm a newbie of linux, does I need to add my joypad in the "XF86Config" file as an input source?

Thx, bye

PS for the padAnalog plugin I referred to in my PM, well, I know that first of all I need to use the padJoy and then testing the padAnalog, but my aim is testing the padAnalog, as ATM my gpu (a SiS650) doesn't let me play PSX games on linux as well as on Windows, I need to use the P.E.Op.S. SoftGpu (the Pete's Mesa OGL is too slow)!

[ammoQ]

Originally posted by Gismo

well, it's exact what I did, but I got no reponse from the gampad config window: I mean, once I click the button I want to configure, I can't configure it, because as I release it, it becomes "light grey", it doesn't remain "dark grey" waiting for an input (I don't know if u could understand, ammoQ, I know, but I can't explain better, sorry )

I understand what you mean...

I notice that this happens everytime I write "/dev/" in the "Device file" field, if I don't write anything, the button stayed "dark grey" for about 2 seconds. As I'm a newbie of linux, does I need to add my joypad in the "XF86Config" file as an input source?

No need to touch the XF86Config. But: you must write "/dev/input/js0" in the "Device file" field, not just "/dev/".

[Gismo]

Originally posted by ammoQ
But: you must write "/dev/input/js0" in the "Device file" field, not just "/dev/".

yes, it's what I did, but: what I was trying to explain is that if I write "/dev/..." (where "..." means what u want, even "/dev/js0") I get always the same problems I described before... when I press a button to be mapped, the button doesn't stay in "dark grey"...

Maybe now u have better understood my problem, anyway thx for your help!

Thx, bye

PS out from the analog, I'd like also to try the ForceFeedback on Linux (not on ePSXe ATM) as I posted in another thread, so perhaps in the next future ePSXe on Linux could support rumble

[ammoQ]

Please post the output of
modprobe joydev
od -xw8 /dev/input/js0

(you did run modprobe joydev before trying to configure padJoy, did you?)

[Gismo]

sure... sorry for the waiting, I don't have a lot of time during the day... and yes, I always run modprobe joydev before trying to configure padJoy

the output (no joystick button pressed):
==========
gismo:~# od -xw8 /dev/input/js0
0000000 3cd2 000f 0000 0081
0000010 3cd2 000f 0000 0181
0000020 3cd2 000f 0000 0281
0000030 3cd2 000f 0000 0381
0000040 3cd2 000f 0000 0481
0000050 3cd2 000f 0000 0581
0000060 3cd2 000f 0000 0681
0000070 3cd2 000f 0000 0781
0000100 3cd2 000f 0000 0881
0000110 3cd2 000f 0000 0981
0000120 3cd2 000f 0000 0a81
0000130 3cd2 000f 0000 0b81
0000140 3cd2 000f 0000 0c81
0000150 3cd2 000f 0000 0d81
0000160 3cd2 000f 0000 0e81
0000170 3cd2 000f 0000 0f81
0000200 3cd2 000f 0000 1081
0000210 3cd2 000f 0000 1181
0000220 3cd2 000f 0000 1281
0000230 3cd2 000f 0000 1381
0000240 3cd2 000f 0000 1481
0000250 3cd2 000f 0000 1581
0000260 3cd2 000f 0000 1681
0000270 3cd2 000f 0000 1781
0000300 3cd2 000f 0000 0082
0000310 3cd2 000f 0000 0182
0000320 3cd2 000f 0000 0282
0000330 3cd2 000f 0000 0382
0000340 3cd2 000f 0000 0482
0000350 3cd2 000f 0000 0582
0000360 3cd2 000f 0000 0682
0000370 3cd2 000f 0000 0782
0000400 3cd2 000f 0000 0882
0000410 3cd2 000f 0000 0982
0000420 3cd2 000f 0000 0a82
0000430 3cd2 000f 0000 0b82
0000440 3cd2 000f 8001 0c82
0000450 3cd2 000f 8001 0d82
0000460 3cd2 000f 8001 0e82
==========

Thx, bye

[ammoQ]

ok, that's the init stuff... and now press some buttons, more lines should appear. Post those lines, pleas.

[Gismo]

Originally posted by ammoQ
ok, that's the init stuff... and now press some buttons, more lines should appear. Post those lines, pleas.

ok, wait just a moment, I came back on Windows because I needes some stuffs on it... just 5min

Thx, bye

[Gismo]

ok, here I am...

- triangle
0000470 4d82 0003 0001 0001
0000500 4dfa 0003 0000 0001

- circle
0000510 c4e2 0003 0001 0101
0000520 c55a 0003 0000 0101

- cross
0000530 1c26 0004 0001 0201
0000540 1c6c 0004 0000 0201

- square
0000550 4dfe 0004 0001 0301
0000560 4e44 0004 0000 0301

- up
0000570 728e 0004 8001 0902
0000600 728e 0004 8001 0102
0000610 728e 0004 8001 0202
0000620 7306 0004 0000 0902
0000630 7306 0004 0000 0102
0000640 7306 0004 0000 0202

is it ok?

Thx, bye

[ammoQ]

(edit: My first guess about the problem was most likely wrong)
Please download the brand new padJoy 7.2! http://download.ammoq.com
It contains more debug output on stderr. To see that, you must start ePSXe (resp. PCSX) in a console window.

edit: check the "Device file name" for the second pad, too. padJoy tries to open both for input (so someone could use two pads with 6 buttons each to emulate a PSX pad with 10 buttons)

edit: made some additional very little changes, version number is still 0.72 . It might take some more changes to fix Gismos problem, I don't want the version number to skyrocket. Except for people who have the same problem like Gismo, nothing has improved. No need to upgrade if everything works. (Doesn't hurt, eighter)