@mitu OK thanks

@mitu After running lsusb, I can see the adapter as follows: Bus 001 Device 004: ID 1292:4154 Innomedia Retro Link Atari cable Using the vendor and product codes from above with 0x appended to each to look up 0x1292:0x4154 with the search term quirks, I found documents referencing this is the option that corresponds to the vendor and product info for my device: options usbhid quirks=0x1292:0x4154:0x040 Some of these include the following sites: https://github.com/libretro/Lakka-LibreELEC/blob/master/packages/libretro/retroarch/modprobe.d/usbhid.conf https://github.com/msteinbeck/hid-retrobit/blob/master/DETAILS.md I edited the /boot/cmdline.txt file and added the following to the end of the line of text: usbhid.quirks=0x1292:0x4154:0x040 After rebooting, I can use the following commands to test that both controllers are working: jstest /dev/input/js0 jstest /dev/input/js1 Thanks for the help!

All right I'll try that!

Thank you ,however I still can't use my gasia controller wirelessly without custombluez installed. So I am trying to install custombluez.

It has nothing to do with the modules, there's something related to the kernel files copied by rpi-update which breaks the compilation - see https://github.com/raspberrypi/firmware/issues/1364.

@TheFloW said in Randomly slow EmulationStation menus on RPi 4: I was referring to how to get to HDMI boost and TV mode HDMI boot configuration is not available for the Pi4, as for the mode selection, you can just use raspi-config and select 1080p as default video mode.

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 - I got it recognised in the end and whilst playing the controller seems fine - it was just the initial set up. I think now I know the specifics, setting it up again would be easier I think it needs a quick press rather than a slow press from the sounds of it. Good work.

@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)