That did it, my homemade joystick is working now direct into the CPU. I do find it disturbing though that an official release is internally inconsistent. With any open project my next move should be to volunteer to fix it. I'm not there yet but learning every day. Thanks for all the help! mcb

I take it nobody uses the GPIO for anything?!?

I had the same issue with the same controller. I suspected it was the Xpad driver and was correct after updating everything else individually. I'm not certain it will fix the issue, but here is my working Xpad driver's entire folder. Working Driver: https://drive.google.com/file/d/1HYT5lnioWIvuF3LuNHe4Wf91DzfLM5-k/view?usp=sharing These go in /opt/retropie/supplementary/xpad, but everything in there requires Root access to alter. SSH Method: https://retropie.org.uk/docs/FAQ/#why-cant-i-ssh-as-root-anymore I hope I was helpful.

Retropie4.4 's support of Xbox 360 controllers is broken Xpad works just fine. Xboxdrv has known issues with multiple controllers but that isn't something the retropie project maintains.

@dankcushions Well I guess I wont be playing that game. Thanks for the info John

@mitu No, I did it but the behaviour is still the same, as the 8bitdo N30 pro (with the difference that it doesn’t have the TURBO button). USB >> 8Bitdo NES30 Arcade Bluetooth >> szmy-power Ltd.Joypad

@retronoobie3000 I know this does not help DosBox but malcolm's Revenge runs flawlessly in scummvm.

@psyke83 Thanks a lot for your answer, it is a honor to receive answer of you, i've decided to leave it as it is now, i dont know too much about retropie, linux and that stuff, i've tried to manual install custombluez, sucessfully installed and had 5.50 but bluetooth was not working ok The only thing left for the moment is support for gasia and shanwguan clone controllers, and would have some problems with repos, and the distribution i have, now some stuff is not working like trying to install custombluez, customhidsony, and some other things because jessie is losing support When strech for my hardware is adapted and available gonna try it again, i have another raspberry 2, and a raspberry 3b, if i had some problems like this gonna try it again and ask you if i have a trouble Im still learning about retropie, linux, emulationstation and that stuff Thanks again for your patience and support

@buzz Thanks a lot - yeah I thought i'd open an enhancement anyway as I did some reading and one of the Retroarch devs confirmed the SW and HW cores are identical, except the HW one has the additional options. Both are the same if you run in software mode: https://www.reddit.com/r/emulation/comments/7hxke8/psa_psx_beetle_hw_is_absolutely_amazing/dquv1jp/ So I figured it would probably be a useful enhancement enabling HW support at some stage - albeit I appreciate not high priority. @psyke83 has kindly done a bit of work already to enable and i'm happy to test this out: https://github.com/RetroPie/RetroPie-Setup/pull/2279 Thanks again.

On my system sudo apt update sudo apt dist-upgrade install kernel 4.9.35-v7+. DragonRise Inc. Generic USB Joystick works without any problem (just redo controller configuration from EmulationStation). You should never use rpi-update ;-)

Here are some tests i have done : $ jstest /dev/input/js0 Driver version is 2.1.0. Joystick (PowerA Xbox One wired controller) has 6 axes (X, Y, Rx, Ry, Hat0X, Hat0Y) and 13 buttons (BtnX, BtnY, BtnTL, BtnTR, BtnTR2, BtnSelect, BtnStart, BtnMode, BtnThumbL, BtnThumbR, ?, ?, ?). Testing ... (interrupt to exit) Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off 12:off $ lsmod | grep xpad xpad 18566 0 ff_memless 5315 1 xpad $ evtest /dev/input/event[0] Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x24c6 product 0x543a version 0x101 Input device name: "PowerA Xbox One wired controller" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 304 (BTN_SOUTH) Event code 305 (BTN_EAST) Event code 307 (BTN_NORTH) Event code 308 (BTN_WEST) Event code 310 (BTN_TL) Event code 311 (BTN_TR) Event code 312 (BTN_TL2) Event code 313 (BTN_TR2) Event code 314 (BTN_SELECT) Event code 315 (BTN_START) Event code 316 (BTN_MODE) Event code 317 (BTN_THUMBL) Event code 318 (BTN_THUMBR) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 1 (ABS_Y) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 3 (ABS_RX) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 4 (ABS_RY) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 16 (ABS_HAT0X) Value 0 Min -1 Max 1 Event code 17 (ABS_HAT0Y) Value 0 Min -1 Max 1 Event type 21 (EV_FF) Event code 80 (FF_RUMBLE) Event code 81 (FF_PERIODIC) Event code 88 (FF_SQUARE) Event code 89 (FF_TRIANGLE) Event code 90 (FF_SINE) Event code 96 (FF_GAIN)

Hello! I have taken the liberty of a new thread: https://retropie.org.uk/forum/topic/17766/mame2003-plus-250-new-games-new-input-system-new-features-a-few-new-bugs/

@wombat We released the version without PCB yesterday (https://www.amazon.com/Super-Kuma-Case-Raspberry-Kintaro/dp/B0767HHJY1/ref=sr_1_1?ie=UTF8&qid=1512052347&sr=8-1&keywords=raspberry+pi+case+snes+kuma#Ask) and it comes with a custom heatsink. The version with pcb is expected to be released in january

@nsuk ok so you made me look like a jackass thanks.

So technically the above worked – I CAN use the Edimax EW-7611ULB combo bluetooth/wifi dongle after following the directions in that link I posted.. ...but weird stuff is happening: 1.) The keyboard (Rii mini, 2.4ghz dongle variety) is now ALWAYS player one. I mean ALWAYS. I unplug the keyboard, hit "A" on a hard-wired controller to start a game, and the keyboard is somehow still player 1 and I have to plug the keyboard back in in order to hit "Select + Start" to exit out of a game. Never had that happen before. Furthermore, my bluetooth controllers ALWAYS took priority (i.e. Player 1, then Player 2, etc) over hard-wired controllers no matter what port they were plugged into (don't play mutiplayer that often but I'm pretty sure that's how it always worked). 2.) WiFi doesn't auto connect. When I go into WiFi setup it even gives me an IP address ending in 140 which totally looks like it's connected if it has an IP address...but it's not really connected (can't SSH or FTP in for example). When I click on connect to a wireless network, re-enter my same password, it then connects, but the IP address changes to end in 12 (which has also never happened since my router I believe always saves the same IP address for a specific dongle...which is how my FTP bookmarks never fail to work). 3.) Since something is screwy, when I unplug the combo dongle, and (reboot) then plug back in the regular bluetooth dongle (which ALWAYS worked before - no special compiling of drivers needed) -- for the life of me I can't get my 8BitDo wireless controller to connect now (tried 2 different bluetooth controllers).

Ah ok thank you. So basicly i neet to change the command to subprocess.call("modprobe --first-time -r db9_gpio_rpi", shell=True) and import the subprocess?!