@martinrdgz before you dump your setup you may check these:

Run wpa_supplicant manually with -d : https://raspberrypi.stackexchange.com/a/103442

Maybe line ending in the wpa_supplicant.conf may be the cause (Mac -> Linux):
https://stackoverflow.com/a/18344020

And I noticed a space in the `psk="<space>...", is put there deliberately?

@alpinemonkey said in ROMs not working on clean install (after working fine on pre-built image):

I also found another version of the game (bin/cue files), have added it and it works.

For PS1 games, Redump validated .cue/.bin files should always work. You can compress them yourself with chdman if you'd like to save space.

I’m not new to using retropie, but I wanted to add an LCD screen to mine and when I downloaded the drivers through the command line, I tried to type in emulation station to come back. When I did this it gave me an error, I don’t remember what the error was because this happened last year, but it wouldn’t let me back in retropie. I think this could be something wrong with the retropie software that I download, because I think I remember trying to exit the command line on my tv and it not working, but I still don’t want to risk it because I have a lot of saved data on my rpi. Can someone help me?

@andini

If you are using Wayland as your display server (now default on Ubuntu 22.04 on) try switching to Xorg instead.

@mitu Lol, this is the way. Thank you so much. Feel so dumb for not thinking to make an issue in GitHub. I appreciate you as always, mitu!

@mitu I fixed it! There was a problem with the Wi-Fi links around the house, as i was in the back room. It appears that the keyboard has a problem, so that is probably fine as I connected a ps3 controller via Bluetooth. Thank you!

@jawsisra said in 4.8 Emulationstation Problems:

Power Supply used: Do not know the name of it. It has a switch to turn off the power

is this the way you shut down retropie / the raspberry pi?

If I connect the dots here and in addition to the merged changes [1] @pjft was referring to, I see also the option that the file log might choke caused by a specific combination of many log writes, threaded loading and slower file operations by rpi3 and/or sd-card (or even undervoltaging, which is crucial to sd-card operations).

While I am unable to reproduce it, it might be considered to reduce the log output of missing theme resources by lowering the log level (WARNING to DEBUG). It would reduce the probability of file log chokes and would also speed up the normal ES boot:

diff --git a/es-core/src/ThemeData.cpp b/es-core/src/ThemeData.cpp index cb1b265..45b54a6 100644 --- a/es-core/src/ThemeData.cpp +++ b/es-core/src/ThemeData.cpp @@ -517,11 +517,11 @@ void ThemeData::parseElement(const pugi::xml_node& root, const std::map<std::str if(!ResourceManager::getInstance()->fileExists(path)) { std::stringstream ss; - ss << " Warning " << error.msg; // "from theme yadda yadda, included file yadda yadda + ss << " Message " << error.msg; // "from theme yadda yadda, included file yadda yadda ss << "could not find file \"" << node.text().get() << "\" "; if(node.text().get() != path) ss << "(which resolved to \"" << path << "\") "; - LOG(LogWarning) << ss.str(); + LOG(LogDebug) << ss.str(); } element.properties[node.name()] = path; break;

Additionally a mutex for log file write operations might be used as outlined here [2] to make fprintf() [3] thread safe.

[1] github.com/RetroPie/EmulationStation/pull/774/files#diff-20f861dd5841312f45eb90d5a56cd5addad0657c66605d6235696a345907e15d
[2] https://stackoverflow.com/questions/43427405/c-writing-to-a-file-in-multithreaded-program
[3] https://github.com/RetroPie/EmulationStation/blob/52c04d77864287aa0ae7f484460966d8253079df/es-core/src/Log.cpp#L77

@asktheaxis it should not be too hard to find a correct rom for SNES, it may become much harder when you decide to go for arcade roms ;D
However: a sidenote, you can keep the SNES roms in zip-format.
Try to search for zipped roms with the addition "good", "[!]" or "tosec".
Those will work for sure.

@when_suddenly said in PiGRRL Zero troubleshooting adding roms:

The problem is none of the emulators show up on boot. I looked at another form for this issue and apparently they had their "Parse Gameslists only" option set to on... however I cannot even access that option in the emulation station main menu. The "other settings" tab is completely missing.

That means you're using a very old EmulationStation (and possibly RetroPie) version. Emulators not showing up on boot means also that they're not installed. Looking at the date of the installation document, it's from 2016, so it looks like they're using an old image.

Use the image from retropie.org.uk/download and we can provide support, otherwise ask the provider of the image for help.

@hunksurvivorx Agree it's something to do with the newest update. It was perfect before because I played it briefly back in july. Playing it with the latest build and the sounds is terrible and even screeching at times.

@dankcushions
Yeah, I checked the sites myself and had no issue. I don't see how it could be the connection on the Pi, though, since the wifi works for anything I do via the GUI - both the main Retropie interface and the setup interfaces. Scraping, updating, etc, all works until I go into the terminal. I'll probably have to seek help elsewhere as I suspect that's still outside of your ability to assist.

Thanks for the help, though. I at least now know some stuff to look at should other problems arise in the future.

@dankcushions luckily i found the bios needed thanks

@pedrovay2003 well the keys were leaked many years ago. Possible that they are in there. Or they have some hackey way of decrypting like the programs that will extract a clean iso from a bought pbp.
You may be the one of the very few people to attempt to run a DRMed file in an emulator, because for the most part, it should not work.
Also beetle-psx is practically the same emulator as mendafins.

@mitu Before I considered dismantling the buttons from my arcade, I found this other command called jstest, which allowed me to see on the command line what each button was configured to on the USB encoder.

Once I ran jstest /dev/input/js0 for player 1 controls and jstest /dev/input/js1 for player 2 controls, Player 1 appeared to be configured correctly with buttons A and B. However, Player 2 clearly is the one not configured correctly. Here I finally found my problem where player 2 had buttons A and B setup to the wrong physical pins of the USB encoder.

Now that I had SW proof of my mistake, I disassembled my controller case and flipped the connections for those two buttons on player 2 onto the USB encoder. Put everything back the way it was, and behold my arcade is now acting correctly with both controls synced up.

Thank you very much @mitu for your suggestion. I do appreciate it.

@mitu Good call! I'm not sure how much power it's pulling, but setting over_voltage to 2 definitely makes it last longer, though not completely staying on all the time. Trying with setting it to 3 right now and that seems to be going strong!

Is your PI configured to boot from USB (not only from sdcard) ?
Check out the Pi 4 Boot Diagnostics page to determine that - look for the 'boot mode' configuration that is shown when you start and see if it includes USB.

@mitu used all the resolutions but they had the same issue. I fixed it by making the bars smaller and modifying some code. Here is what i did. Reference if someone comes with same problem.

First here the two smaller images. https://imgur.com/a/BbOfzr7
I named them gamelist_outline_smaller.png and gamelist_background_smaller.png

Uploaded this files to my pi on /etc/emulationstation/themes/snes-mini/art
then modified the setup xml with

sudo nano /etc/emulationstation/themes/snes-mini/layouts/setup.xml

replaced both paths with the new images like this example

<image name="gamelist_background" extra="true"> <path>./../art/gamelist_background_smaller.png</path>

since my resolution is using 4x3 i went and

sudo nano /etc/emulationstation/themes/snes-mini/layouts/4x3setup.xml

i replaced gamelist outline so it alignscorrectly, with this code

<image name="gamelist_outline" extra="true"> <origin>0.5 0.5</origin> <pos>0.7055555555555556 0.5</pos>

and done

Everything seems okay now. I had a Linux system I needed to set up. (Others were in use and I couldn't easily use them for this.) I got it up, added GPartEd (which, interestingly, did not include GPart as a dependency) and read the card from there. GPartEd could not find anything wrong with the partitions on the card, but after I used it to read and very, the card worked when I put it in the Pi!

I didn't write anything to this device, in Mac or Linux, so my guess is that GPart or GPartEd did something while just reading. Maybe it had trouble with a few bytes or when it wrote a date, it updated something else. I don't know, but just reading it and having GPart look at it was enough that the card started working when I tested it.

It's worth noting that when I booted it with my Pi, the system did have issues with partitions and scanned them, but found no errors.

I'll be taking it down and testing it in the arcade setup this evening.

I just updated to the Beta version for Raspberry Pi 4 and it seems to be working. Thanks!