arcadiacook wrote:If I switch back to modprobe gamecon_gpio_rpi map= 0,0,0,0,7,7 then everything goes back to working. I don't think this is a power issue, but I could totally be wrong. Even with all four controllers plugged in and their analog light on all 4 (the PS2 Controller had a light if you turned off and on the analog sticks,) the system went back to behaving like normal.
But if modprobe gamecon_gpio_rpi map= 0,0,7,7,7,7 with 1 or 4 controllers plugged in and I am fairly certain they all get power, there is no response. I am still thinking it is the ID they get in the kern log
Ok, it's not a power issue then if you get it working by just changing the driver config while the physical setup stays the same.
I tried to replicate this behaviour by connecting my PSX pad to GPIO4 and trying different setups:
Code: Select all
modprobe gamecon_gpio_rpi map=0,0,7,7,7,7
Code: Select all
modprobe gamecon_gpio_rpi map=7,7,7,7
jstest /dev/input/js2 #note the changed ID
Both worked for me without issues
One thing I forgot to mention that you should always run "rmmod gamecon_gpio_rpi" between consecutive modprobe commands (I though one couldn't even load the driver with new config without unloading first, but it seems so...), but if you tried the 4-pad config straight after reboot, then this didn't cause the problem.
I can't think of what could cause the issue, but it's not related to the IDs of /devices/virtual/input/inputX , which get assigned sequentially to new input devices (0 and 1 being most likely your kb and mouse). You can check the physical input mapping with lsinput
(ignore BUS_PARPORT). Did you try if "modprobe gamecon_gpio_rpi map=0,0,7,7" worked? That info could give some insight where the problem is.
arcadiacook wrote:Funny thing happened today as well. If I play two player NES two player games no problem with the two game pads, but for whatever reason playing 2 player SNES games player 2 wasn't working on a few games, but others it would. This is likely a separate bug, but curious nonetheless.
Hmm, are the pads identical? One more thing worth trying out (I'm sorry to make you the tester
) is to increase the psx pad access delay (add "psx_delay=25" to the modprobe command).