@Lolonois
Since space is a critical factor for my arcade project (transforming a Nintendo NES controller into a portable game console with a small integrated TFT screen), I'd prefer to use the option where I modify the GPIO ports.
I only need to configure player 1; player 2 is useless.
Without wasting your time, you might not have a gpio-joystick.dts file, or at best, a gpio-joystick.dtbo file that matches my configuration. 😅
I'm not sure I'll be able to properly modify and compile the gpio-joystick.dts file to match my configuration. 🤣
Thanks.

@mitu with a cable mini usb to usb A
I think the link from the supposed fix is not available https://github.com/jeremyb31/bluetooth-5.13.git

also tried this , with no success

cd /lib/firmware/rtl_bt
sudo wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/rtl_bt/rtl8761bu_config.bin
sudo wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/rtl_bt/rtl8761bu_fw.bin

I.m so unlucky :))

If the inputs are not registering correctly when testing the input with evtest or jstest, they won't be delivered correctly also to EmulationStation - this is not related to any RetroPie configuration, but it's an OS (Linux) or Arduino issue.

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

@Jimi007 said in Retropie 4.8 and Amiberry latest version:

I just wanted to find out if anyone has a guide or knows if it's possible to update to the latest Amiberry v7 version on a Raspberry Pi 5 with Retropie 4.8.9

You can unpack the latest release from https://github.com/BlitterStudio/amiberry/releases/tag/v7.0.8 over the installed version in /opt/retropie/emulators/amiberry.

I thought the (full) Amiberry is not meant for anything other than a PC type system and the Lite version is recommended for weaker devices. Anything that's in v7 that you're looking for ?

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.