@Jimmy14 Getting off-topic here but as a starter:

You may want to use something like the PAM8302 and then use audremap in the config.txt

I have not been down that road but the information in the refenced pages should get you started.

Feel free to start a new thread here, but I assume in the Raspberry Pi forums you will have more guys which may have dealt with it already.

Are you using the Libretro core of pcsx_rearmed or the standalone emulator ? Is your RetroPie installation updated ? How did you install RetroPie and which image did you use ?

Please add the make/model of your controller, 8bitdo have a lot of controller models.

Thank you Mitu

You can use jscal to modify the deadzone(s) of an analog joystick, then jscal-store to save the values so they can be applied automatically on boot.

@Jimi007 said in Retropie 4.8 and Amiberry latest version:

I thought V7 should be able to be used for more powerful devices including the Pi 5 and V5 Amiberry should be for Pi4 and below.

Looking at the description it would seem the new 7 version would work on the Pi5, but same description states that JIT for ARM platforms is missing. But is there anything in specific that's in v7 that you're looking for ?

@mitu thanks for suggestions and help

@Aterlom said in LR-FBNeo Diagnostic Input (dip switches) not working:

I don't understand why if by default it´s suggested that select / hotkey be the same button

Having a dedicated hotkey button is the recommendation as far as the libretro project is concerned, and it will configure this automatically with most controllers sold commercially. Using an already-in-use button is only a workaround for the few users who actually can't afford this. Retropie might be doing other recommendation though, i don't know.

@Aterlom said in LR-FBNeo Diagnostic Input (dip switches) not working:

Perhaps it would be convenient to add this information...

Well, that's not exactly a frequently asked question tbh, i think you are the first person bringing this up since i started working on this core over a decade ago, but i have seen similar issues where the user couldn't add credits in certain games (the coin input in arcade cabinets is kind of a hold mecanism). Also, this is more of a retroarch behavior than a core problem. Adding something about this in the doc might be a good idea though, thanks for the suggestion.

The game has been updated

@mitu created the folder and copied the file

pi@retropie:/lib/modules/5.10.103-v7+/updates/dkms $ ls
hid-sony.ko

pi@retropie:/lib/modules/5.10.103-v7+/updates/dkms $ sudo modinfo hid_sony
filename: /lib/modules/5.10.103-v7+/kernel/drivers/hid/hid-sony.ko

restarted

but still controller not recognized

too bad..

@Jiryn said in Manual Installation Broken at GitHub level:

Remote: Support for password authentication was removed on August 13, 2021

The issue was caused by your typo for the repository URL. Instead of RetroPie-Setup you entered RetroPie-Steup and Github assumed is a private repository and tried to authenticate you.

@hoeveler If core input remapping doesn't work, you can either do a configuration override (per-game) or manually add the input configuration in a game dependent configuration file (explained also on the same page).

@Folly

Cool thanks ill give it a try

@ldeveraux damn, sounds logic haha

@barbudreadmon oh ok I didn't realize they all should be uncompressed, I will try uncompressing them.

I will try the dmesg command and see what it shows, thanks

@CaptRobovski said in Can I backup current emulator state - corrupted memory stick:

A quick question - should the filename under etc/udev/rules.d end in the suffix '.rules' ? I have other files in there, such as 99-input.rules, 99-bluetooth.rules.

No, the extension is not needed. Only the lexically order may be relevant of all rule files (cf. man udev -> RULES FILES).

The memory stick has left the factory mostly fine I would assume. It is the firmware that make things worse in use cases like this (as likely the USB spec has not been implemented by the letter by the vendor).

If you change make and model of the memory stick you may leave the power control rule enabled (adapt to the VID/PID). Does not have an impact unless you run on battery.

Or you can make a backup of you new memory stick and run it without the power control rule. If things repeat restore the memory stick and enable the rule.
However, if it repeats on a different make/model the issue could also be caused by the RaspBerry Pi Kernel USB implementation.

Unless you're running under X/Desktop/Wayland, there's no control over the which display comes 'first' at runtime. You can use config.txt to enable/disable the LCD (is it a DSI display ?) or HDMI, but that requires a reboot.