not sure. but if you want a more useful error message, try exiting to command line and doing (for the OP's example)

gdb --args /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-pcsx-rearmed/libretro.so --config /opt/retropie/configs/psx/retroarch.cfg /home/pi/RetroPie/roms/psx/EBOOT.PBP

then ENTER. that will start the debugger command line, then type run and ENTER, and then it should run and crash again, then you type bt then ENTER to get a useful backtrace, then paste the entire contents of that process here.

note that this is for working on your pi directly. if you do this via SSH you need to do tty /dev/tty1 before run, to make it run on your tv rather than try and run in your remote terminal window.

hi @Kristopherson05 i had the same issue on mine. If you look in the wiki for the gameboy advance https://github.com/retropie/retropie-setup/wiki/Game-Boy-Advance it tells you the name the bios file has to be.

I found one with a git of googling, then unziped it, and renamed the file to 'gba_bios.bin' and dropped it in the BIOS folder.

one reboot later and it was all working

Not that anyone is following this topic, but I ran a wire from the antenna input on my receiver to the metal casing of the monitor and the hum instantly went away. Reciever doesnt have a ground post, but at least its grounded this way and theres no stray current going through the rca cables.

Might help anyone with a similar solution.

@herb_fargus I'm on pi3, i will try lr-fba-next so, Thnaks!

I think 0.139 used CHD v4 (lr-mame2010) and 0.161 used CHD v5. You'll need a rollback file and use chdman from a command line (this can take a while for a whole set) if you can't find v4 CHDs.

I think these are the correct CHD versions if not they are close.

mame4all-pi (0.37b5) - N/A (CHD wasn't introduced until 0.62 or 0.63) lr-imame4all (0.37b5) - N/A (CHD wasn't introduced until 0.62 or 0.63) lr-mame2003 (0.78) - CHD v3 lr-mame2010 (0.139) - CHD v4 advmame-.94 (0.94) - CHD v3 advmame-1.4 (0.106) - CHD v3 pifba (0.114) - CHD v3 lr-fba (0.154) - CHD v5 lr-fba-next (0.173) - CHD v5 gngeopi (0.138) - CHD v4

Knowing the CHD versions could be useful as the Pi gets more powerful. :) I think some versions of MAME could use earlier versions of CHDs as "readonly" but if it was a CHD that could be written to for like high scores or something it doesn't work without the correct version.

Instead of modifying the CHD directly (which would change the internal/external hash--MAME only cares about the internal hash which is data minus metadata) I believe MAME would auto-create a <game>.diff file and use it.

I think current versions of chdman can verify older versions but not vice versa for obvious reasons. :)

Newer versions command line:
chdman verify -i area51.chd
chdman info -i area51.chd (shows CHD version & other info)

Older versions command line:
chdman -verify area51.chd
chdman -info area51.chd (shows CHD version & other info)

@GreenHawk84

I believe the cocktail table rom of 'Pac-Man' has a competitive play feature for two players.

Well I appreciate all the help today! Looks as though wifi is holding for now. lol. I will check into those other forums to further my education into all things pi

@ZombieMedia

https://retropie.org.uk/forum/topic/2/forum-rules

https://retropie.org.uk/forum/topic/3/read-this-first

got it covered, thanks! now i just have to figure out why my sfiii isn't working in the new install. sigh. :) EDIT - bad copy, that's fixed, at least!

one of these days it'll all work!

wait till you try to play any mame roms. I had a really hard time with it. ended up plugging in an external keyboard and pressing 'TAB' key to configure input via keyboard. I still needed the controller key codes that I got from the controller cfg files.

@Razzle Tech is easy, people are hard. But here you will find some of the most helpful and gracious people I've found on any forum. Keep up the good work guys!

@Concat, @BuZz

I really appreciate the extras eyes on this to confirm what I was seeing. I can't reproduce the problem on Windows or the MacOS, so maybe it's a Linux-specific issue. I'll open a ticket and see what the RetroArch team has to say. Thanks BuZz, for searching the sourcecode. I need to learn how to do that somewhere down the road. Also, thank you Concat for the map testing. I was beginning to think I was imagining the whole thing ;).

In an effort to move forward with my own goal, I'll have to rethink and even compromise the idea of a universal gamepad control scheme for now, but I have a few ideas in mind to easily allow switching between control schemes for all the systems that currently lack Joystick support. Perhaps a series of script templates that can easily be installed and launched from a sub-directory in the 'RetroPie' menu in Emulation Station. This might be better in the long run as the end user could duplicate and configure the templates on a game-by-game basis for systems like the ColecoVision that need a more refined control scheme depending on the game.

Edit: Also, thanks for the last suggestion Concat. While it doesn't meet the global requirements I need, I'm definitely going to keep that trick in mind for the future.

I was able to get past the controller config with the psx controller, so now I'm able to set the keyboard as the default, hopefully. I ran into some other issues and will test later to see if I can have the joystick plugged in and still use the keyboard. Thanks for the help!

@Duhjoker Most of the Bluetooth changes are since 3.8.1 - so you would need to update the RetroPie script to have them.
So I'l probably update the Wiki once the next image is produced.

Mame scraping is based on filenames rather than hashes - do you have an example of a filename you have in the folder?
Obviously the mame roms should remain zipped.

Oh okay sorry about that. I'll make that correction in future posts.

I changed the driver from udev to sdl2 and restarted a couple times and that seems to have fixed the problem!

Thanks so much for the help!!!!!

For future reference I edited the above mentioned config and the Gamepad.cfg to resolve the issue!

Thanks again!

I did a full reinstall and used a PS3 controller over Bluetooth and it is all working now.
All I can think of is that my old 360 controller is on it's last legs or it was pulling too much power.