My ROMS worked before... but now they don’t
-
@dankcushions I am not running RetroPie via the pixel desktop. My pi is set to boot right into RetroPie upon startup.
-
Start EmulationStation with the
--debugswitch from the command line and then post the log ($HOME/.emulationstation/es_log.txt) to pastebin.com.
Disable first the Parge Gamelists Only setting. -
@mitu I have never done the debug switch before. Would you just type —debug in the command line before entering EmulationStation?
-
@mitu I don’t have the folder EmulationStation in my home directory.
-
@Brandon12345678 it's not
Emulationstationit's.emulationstation. read carefully.eg:
pi@raspberrypi:~ $ cd .emulationstation/ pi@raspberrypi:~/.emulationstation $ -
@dankcushions Here is the link to the paste of the es_log.txt,
-
@Brandon12345678 There's a single error about the
colecosystem missing the folder, but that's harmless.Unless you're having Sdcard issues - and files are disappearing because of it - I don't see what causes this. ROM/games don't disappear because you install an new emulator.
For the issue of launching games though, the errors should be present in
/dev/shm/runcommand.log, after launching a game. Can you post also this log file ? Make sure you enable verbose logging when launching the game, from the runcommand launch menu. -
The runcommand says this,
(==) Log file: "/home/pi/.local/share/xorg/Xorg.0.log", Time: Thu Jun 18 13:07:01 2020 (==) Using system config directory "/usr/share/X11/xorg.conf.d" modprobe: FATAL: Module g2d_23 not found in directory /lib/modules/4.19.118-v7l+A weird thing was that I tested a couple roms from different systems(For example, Bubsy on genesis) and they load, but there is a black screen and a retroarch error comes up saying that it failed to extract the game's contents. I think when parse gamelists is turned off, the games that run with it turned on do this. Weird.
-
@Brandon12345678 Your log file shows the X.org log file, which suggests the launch command is start Xwindows - this is not how the RetroPie default image is configured.
You're using a customized/3rd party image. I suggest, as others already did, to start from a stock image and you'll probably not have this issue. -
@mitu how would you get the stock image?
-
@Brandon12345678 If it was a legit image, could this problem be a bug in rpi4 RetroPie since the rpi4 version is a beta right now.
-
@Brandon12345678 said in My ROMS worked before... but now they don’t:
If it was a legit image, could this problem be a bug in rpi4 RetroPie since the rpi4 version is a beta right now.
That's a moot question, since you're not using a stock image. It's not a 'bug' though.
how would you get the stock image?
From retropie.org.uk/download.
-
@mitu That is how I installed RetroPie this time. I downloaded my image from there.
-
@Brandon12345678 Then why did you install the Pixel desktop? Maybe you should start again with a fresh official image and don't install Pixel.
If you wanted a desktop in your RetroPie installation for more convenience in managing and editing files etc., there are other ways to make your life (a little) easier, e.g. the terminal-based file manager
mc. Just entermcin the terminal to run it. -
@Clyde Ok thanks. I wanted to have a desktop, but have it boot into a terminal.
-
@Brandon12345678 How can I save as much of my RetroPie data like configs and ROMS to put them back on there when I reset?
-
@Brandon12345678 the same way you got them on your stock image, just in reverse-mode.
-
@sirhenrythe5th Ok thanks
-
@Brandon12345678 Most of the custom content and options should reside in
/home/pi/RetroPieand/opt/retropie/configs. That said, I would caution against copying all of it back to a new image in one go, but only step by step what you really need. Lest you copy any messed-up stuff on the fresh installation. -
@Clyde Ok.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.