I've taken a look at this and it seems the issue is the Bluez updates due to CVE-2023-45866 (as I said initially).
This will likely affect any (old) gamepad which doesn't encrypt the comunication with the host. The workaround is suggested in the linked Ubuntu bug report:

Set ClassicBondedOnly=false in /etc/bluetooth/input.conf
Run sudo systemctl restart bluetooth or reboot

Possibly other gamepads affected - the Wii U Pro Controller (haven't tested it yet).

NB: this issue is not restricted to Raspberry Pi, it affects any platform where Bluez was patched for CVE-2023-45866.

@Robinson You don't need a bios for 2600, see : https://retropie.org.uk/docs/Atari-2600/

Apologies for bumping an old topic, but partial support for this has been added into Retroarch 1.17:-

https://www.libretro.com/index.php/retroarch-1-17-new-netplay-features/

This will only work with a handful of games that supported the GBA Wireless Adapter, so for example no Mario Kart Super Circuit.

However, apparently it works well with Mario Golf and Pokemon Emerald/Fire Red/Leaf Green (https://www.davidgf.net/2024/01/13/gba-wireless-adapter/)

@notthesame I can't believe that worked, you are a godsend. I'd also like to add a few details:

After pressing Start and Y, the LEDs start to rotate from left to right. After that, you hold pair for 2 seconds, the LEDs go off for a second, and then they start to rotate again.

At this point you need to go through the Bluetooth pairing process again (and if your controller is already paired, you should un-pair it before you re-pair it) but you do NOT need to set up the udev rule. All you need to do is reboot and configure the input like normal.

I think this should be added to the documentation.

@mitu Well ... looks like you are right. :D

Edit:
Fixed! ;)

@mitu I'm .. sure I'm not using it or setting it up appropriately.

I'm not using the runcommand.sh file that is for launching game in retropie. i'm sort of bypassing that, because I couldnt figure out the process or syntax

first, when you are just on the command line area (No Desktop) to initiate xinit, you must use sudo, but that doenst mean that retropie itself doesnt take care of that in some ... manner.

anyway, heres my commands.

the game's .sh file reads:

xinit /usr/local/bin/wine /home/pi/.wine/drive_c/game_path/game.exe

Next: es_systems.cfg file reads:

<command>sudo %ROM%</command>

thats it and it works.
I tried for hours to get the normal:
<command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 SYS pc</command> to work, but it wouldn't load, but also requires a config file.

so in the /opt/retropie/configs/pc
i created emulators.cfg file, but what do i put in there?
pc = wine ?
default = pc
and if so, what do I change the game.sh file to? it already has the wine command in it.

my main reason for creating this thread, was to figure out the syntax for 3 files.
/home/pi/RetroPie/rom/pc/game.sh
/etc/emulationstation/es_system.cfg
/opt/retropie/configs/pc/emulators.cfg

I've been working with the retropie software since 2015 when i got my first raspberry pi 2, but I've never tried this type of launch and its not easy to find the details about this type of functionality.

thanks for listening. :)

@mitu
I just reinstalled alsamixer and now everything is working. still no idea what caused this issue. made a backup image of my sd card now. thx for ur replies bud, learned a little more about alsa✌🏽

@mitu Thank you for the information. I am sorry for posting in the wrong area.

@luiz_angeloni said in Retopie update deleted the roms:

I have a retrorange retropi 4.4.2 ...

That's not an official RetroPie port - it's a fork that is not supported by RetroPie, but by the authors of that fork.

You should ask for help in the retrorangepi forums (or other support channels they might have), since we don't know how this fork (based on a quite old RetroPie version) is configured or works.

@retepam There is a section about choosing the correct arcade core for your needs in the libretro documentation, you should read it, mame4all/mame2000 is basically the worst choice you can make here.

I'm not aware of any issues with 22.04. There may have been, at the time it was launched, 2 years ago, but there shouldn't be today. Again, 18.04 is not supported upstream and support for it from various emulators is dwindling.

@windg Hi again.

I took your advice and uninstalled RetroPie completely, then reinstalled everything again.

Everything works as intended, and now I can also play N64 games (mupen64plus-next wouldn't load previously).

Thanks for helping.

@barbudreadmon OK think I've solved it. Mame2003plus does show the correct colours so I've used that rather than FBNeo, then I can access the MAME menu from the Tab and set the 2-Player Start. Thanks for your help

@Ashpool

So that's the reason why many use the 0.139 (2010) with Retropoie? At least that's my feeling. I also have a full RomSet of 0.139, but it bothers me that there are so many duplicate entries in the game list in Retropie and also games that cannot be played due to a lack of controllers. But I haven't found a halfway good way to sort the roms, at least not without investing a lot of time into learning how to do it. But from what I hear now, it sounds like I should ignore it because the newer romsets aren't as well supported and I can be happy with the 0.139 where all games run at good speed.

Thank you both.

Your comments lead me to explore the emulator settings more and I found that it was set the keyboard for control. As soon as I set it to controller all the settings mapped correctly.

@mitu

Thank you all for this information, it is most appriciated.

@Limegreengamer9 I don't 'have' any other drivers.

You may try to see if the gamepad works with a more recent Linux kernel, with the drivers included there. Boot with a recent Raspberry Pi OS Lite and try to run jstest there to see if all inputs are properly detected. You may need to install the joystick package for the jstest command.

You still need this? It took me a while but I did build it using the instructions below

(Windows) git clone https://github.com/ppy/osu cd osu dotnet workload install android maui-android dotnet publish -c Debug --runtime linux-arm64 (or Release) (Saved location)\osu\osu.Desktop\bin\Release\net6.0 Copy over linux-arm64 folder to the pi (Raspberry Pi) sudo apt install 7zip sudo apt install libsdl2-dev https://www.un4seen.com/download.php?bass24-linux go into \bass24-linux.zip\libs\aarch64 and copy the libbass.so to /usr/lib https://www.un4seen.com/download.php?z/0/bass_fx24-linux go into bass_fx24-linux.zip\libs\aarch64 and copy the libbass_fx.so to /usr/lib https://www.un4seen.com/download.php?bassmix24-linux go into bassmix24-linux.zip\libs\aarch64 and copy the libbassmix.so to /usr/lib /home/pi git clone --recursive https://github.com/veldrid/veldrid-spirv/ cd ext ./sync-shaderc.sh mv src shaderc cd .. ./build-native.sh -release linux-x64 cd build/Release/linux-x64 mv libveldrid-spirv.so liblibveldrid-spirv sudo cp liblibveldrid-spirv /lib/aarch64-linux-gnu /home/pi mkdir libs cd libs wget https://chromium.googlesource.com/android_tools/+archive/20ee6d20/ndk/platforms/android-21/arch-arm64/usr/lib.tar.gz 7z x lib.tar.gz 7z x lib.tar sudo cp libandroid.so /lib/aarch64-linux-gnu sudo cp libdl.so /lib/aarch64-linux-gnu/ sudo cp liblog.so /lib/aarch64-linux-gnu/ sudo apt-get install libstb-dev add kernel=kernel8.img to /boot/firmware/config.txt sudo reboot cd (wherever you have osu) chmod +x osu\! LIBGL_ALWAYS_SOFTWARE=true ./osu\! stop the game from loading after the fonts load (ctrl + c) nano ~/.local/share/osu-development/framework.ini change "WindowedSize" to 640x480 chnage "FrameSync" to Unlimited change "WindowMode" to Windowed save the file LIBGL_ALWAYS_SOFTWARE=true ./osu\! osu should load in at 640x480 windowed

ceb13383-7674-4078-bb0b-b40ace6a4b48-image.png

theres a couple of things with your provided information.

#1 there isnt an official release of the RetroPie software for the Raspberry Pi 5

#2 more importantly, the Pi5 can emulate (barely) original Xbox games and not very well.

the Raspberry Pi 5 will never, and I mean NEVER play Xbox 360 games, so using your kinect for 360 games in not a possibility. the kinect might work in some other way with other emulators and motion games, but i dont know and doubt it, because no one is working on any software to make the 360 kinect sensor work. also a very important note: the Xbox 360 used special GPU instructions called AVX and not only will ARM processors never work with this, but many Intel chips wont use it either.

I dont say never very often, because there are some amazing programmers out there that make magic happen sometimes, but this isnt one of them.
Xbox 360 emulation will never work on a Raspberry Pi 5, sorry :-/