Messed up retroarch

[qqMajiKpp]

still a little on the vague side…

if its a config issue maybe this may help:

Can't start RetroArch 1.8.1 with retroarch.cfg from GameShellDocs

I messed up my retroarch.cfg by resetting the config from the menu and try to use https://github.com/clockworkpi/GameShellDocs/blob/master/retroarch.cfg to fix it. But it won’t let me start RetroArch. I believe my RetroArch’s version is 1.8.1 (the one that comes with the v0.5 image, can confirm tomorrow because I don’t have my GameShell at hand right now). The config file on GitHub was updated more than 1 year ago. Can someone update that in the repo? And can we customize the preinstalled Retr…

there is a megathread here:

RetroArch Megathread

Thanks, This is what I get cpi@clockworkpi:~$ retroarch -L /home/cpi/.config/retroarch/cores/vice_x64_libretro.so /home/cpi/games/c64/BRUCELEE.D64 Segmentation fault if I mistype the D64 name it launches to the C64 core… I just flashed again your DEOT and tried adding new menu-item with the action.config and it works nicely, listing all my roms but again, running them does just not work. ROM=/home/cpi/games/c64/ ROM_SO=/home/cpi/.config/retroarch/cores/vice_x64_libretro.so EXT=d64,g64,t64,…

or maybe upgrade to 1.9:

Custom D.E.O.T. V2.0+/Clockwork OS v0.5 image - With customised DEOT interface, Kernel 5.7, Optional 1400MHz OC, Debian 10 Buster, Retroarch 1.9.0, Mupen64+ plus more! (Current build: 200903)

Similar to my previous DEOT custom build based on 0.4, I have put together a new image, based on the ClockWork OS 0.5. This is the same as the official 0.5 image, just with a lot of updates, and quality of experience optimisations. You don’t need the DEOT edition Gameshell to use this. The official DEOT image is much older, and behind the official 0.5 image. This custom image is the bridge to get the best of both worlds. [b7d679edaee7a55ad42147c9085b5e919824296a_2_462x500] Here is a google dr…