ghost
commented
2 years ago Well, nevermind. In my infinite wisdom, I spent two days banging my head against this problem only to finally remember that, in a Linux environment, everything is case-sensitive. This includes things like the names of your BIOS images for ancient Japanese personal computers.
I can't figure this out for the life of me. Running any software (or even just attempting to start the core on its own) results in an instant crash of RetroArch. Enabling logging, I see...
...which is interesting as I have a directory named 'keropi' within my 'system' directory containing the necessary BIOS images with verified md5 checksums. RetroArch is correctly pointed at the 'system' directory.
This exact keropi directory, with the exact same BIOS images, works just fine on a Windows machine (with an older version of the core, as per the fairly recent 64-bit Windows toolchain issues apparently happening, just to be clear). On my Linux machine, however, I get the aforementioned error. The troubleshooting methods on the docs page for this core have been followed (i.e. the deletion of config and sram.dat) and I've even went as far as to strip the keropi directory down to the two necessary BIOS images (iplrom.dat and cgrom.dat) and have once again verified the md5 sums as correct as per the docs page. Same issue. For the record, all other cores are working just fine for me, even those expecting to find data in the RA 'system' directory.
As of this moment, the keropi directory is down to the two necessary BIOS images, and the core is fully updated. I'm sure I'm just overlooking something. Any ideas?