Rom appears but unplayable

Elitekrd

Hello everyone, I have come across an issues I cant seem to solve. I have actually looked around these threads and saw others have encountered the issue but none of the resolutions have worked for me.

I have downloaded a Rom into Retropie. Through a USB drive in the appropriate n64 folder. It shows up, but upon selecting it, it quickly fades in and out. I tested the Rom on another device (Iphone) and the file works without issue. I went into the Midnight File Manager and tried to copy and paste into the appropriate folder from my USB stick to Retropie to see if that would work and it still gives me the same issue. Not sure what it can be.

I try to see the error string through /dev/shm/runcommand.log but I am unsure of how to copy and paste it here.

Having someone help me troubleshoot would be appreciated.

mitu

Please add some info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

went into the Midnight File Manager and tried to copy and paste into the appropriate folder from my USB stick to Retropie to see if that would work and it still gives me the same issue. Not sure what it can be.

Your sdcard may have issues and the file is not copied correctly.

I try to see the error string through /dev/shm/runcommand.log but I am unsure of how to copy and paste it here.

You can copy the file on the USB and then access it from the PC, open it up in a text editor and copy the contents to paste them into a new post in the topic.

Elitekrd

Hello,

My setup is as follows:

Pi Model - RPi5 8gig version
Powersupply - Official RPi5 powersupply. 27watt.
RetroPie Version: 4.8.9
Built From: Premade SD Image made on top of existing OS (Raspbian OS)
USB Devices connected: Wireless Mouse, and Xbox Controller.
Guide Used: Official Guide on the Retropie site.

This is what the runcommand.log states

Parameters:
Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mupen64plus-next/mupen64plus_next_libretro.so --config /opt/retropie/configs/n64/retroarch.cfg "/home/karoldiaz/RetroPie/roms/n64/Legend of Zelda, The - Ocarina of Time (U) (V1.2) [!].z64" --appendconfig /dev/shm/retroarch.cfg
/opt/retropie/supplementary/runcommand/runcommand.sh: line 1328: 1367 Segmentation fault /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mupen64plus-next/mupen64plus_next_libretro.so --config /opt/retropie/configs/n64/retroarch.cfg "/home/karoldiaz/RetroPie/roms/n64/Legend of Zelda, The - Ocarina of Time (U) (V1.2) [!].z64" --appendconfig /dev/shm/retroarch.cfg

mitu

@Elitekrd said in Rom appears but unplayable:

Pi Model - RPi5 8gig version

Pi5 is currently in beta - are you aware of that ?
Your issue is most likely caued by the '16k page' kernel that's present by defaults. Add kernel=kernel8.img to /boot/firmware/config.txt and reboot.

Elitekrd

@mitu I knew it was in beta yet. However, I have seen many others be able to use it to play their games.

Your suggestion worked perfectly. I truly appreciate all the help. May I ask, how did you come to this conclusion? I am always eager to learn from my mistake and then use that information to help others if they come across the same thing.

mitu

@Elitekrd said in Rom appears but unplayable:

May I ask, how did you come to this conclusion? I am always eager to learn from my mistake and then use that information to help others if they come across the same thing.

It came up in a Github issue [1] a while ago, it's not something that's easy to spot. It was reported in the Pi5 topic that's pinned, but due to users posting any error they found on a Pi5 it's a bit difficult to find now.

[1] https://github.com/raspberrypi/bookworm-feedback/issues/107

Derivitiv

@mitu said in Rom appears but unplayable:

@Elitekrd said in Rom appears but unplayable:

May I ask, how did you come to this conclusion? I am always eager to learn from my mistake and then use that information to help others if they come across the same thing.

It came up in a Github issue [1] a while ago, it's not something that's easy to spot. It was reported in the Pi5 topic that's pinned, but due to users posting any error they found on a Pi5 it's a bit difficult to find now.

[1] https://github.com/raspberrypi/bookworm-feedback/issues/107

Thank you for this! I ran into the same issue and this resolved it.