so having a look here to see what matches and what to replace in the fstab and what I'm seeing is the following:

/dev/mmcblk0p1: LABEL_FATBOOT="bootfs" LABEL="bootfs" UUID="F737-8E10" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="90ace319-01" /dev/mmcblk0p2: LABEL="rootfs" UUID="d6ecfcd5-2703-41bf-9301-10c403b6fb0c" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="90ace319-02"

those would be the SD card labels if im not mistaken and you had said:
@mitu said in usb boot from 5tb hdd:

The PARTUUID of the disk is not the one you have in /etc/fstab - the one in /etc/fstab actually refers to the partition from the uSD card.

however i am not seeing the PARTUUID d9c86127 anywhere in the mmcblk0 read outs. I'm curious how you came to that conclusion.

do i change the entire PARTUUID in the fstab to match the ones in the blkid readout:
i.e.
from this in fstab:

PARTUUID=d9c86127-01 /boot/firmware vfat defaults 0 2

to this:

PARTUUID=701069d0-00cf-01dc-e814-08b86700ee00-01 /boot/firmware vfat defaults 0 2

I'm assuming that the -01 at the very end directs it to partition 1 on the hdd as it is labeled /boot/firmware under the proc column.

lastly i should change the cmdline.txt from this:

code_textconsole=serial0,115200 console=tty1 root=PARTUUID=d9c86127-02 rootfstype=ext4 fsck.repair=yes rootwait quiet init=/usr/lib/raspberrypi-sys-mods/firstboot cfg80211.ieee80211_regdom=NA systemd.run=/boot/firstrun.sh systemd.run_success_action=reboot systemd.unit=kernel-command-line.target

to this:

console=serial0,115200 console=tty1 root=PARTUUID=701069d0-00cf-01dc-e814-08b86700ee00-02 rootfstype=ext4 fsck.repair=yes rootwait quiet init=/usr/lib/raspberrypi-sys-mods/firstboot cfg80211.ieee80211_regdom=NA systemd.run=/boot/firstrun.sh systemd.run_success_action=reboot systemd.unit=kernel-command-line.target

what kind of throws me for a loop is the fact that the HDD PARTUUID has so many more characters than the original PARTUUID. Is there any particular reason for this?

OBS Studio (video capture tool) adds this strange, unwanted scanline effect right away, which is even more annoying. It might be related to the encoder settings, and I basically have no idea how to get rid of it. The game itself and the CRT shader looked perfect on screen. The curved lines were added after I captured it. This can be seen in the video from my channel.

Leaving aside the fact that 2GB is not enough to run the latst RetroPie image (or RaspiOS for that matter), this looks like an issue with the way the card is read/writen - are you using a mSD adapter or a SDcard port on your PC ?

@Moulinex I did the installation guide

At some point I was suspecting the SD card but it seems it was fine

But I did not have the "ASCII" Retropie color logo when you start the Pi in bash mode

@danturn said in < 30 FPS, Can't get games running smoothly on Raspberry pi 5 (Rodland, Gods, New Zealand story):

@RapidEdwin08 ok thanks, i might check this out... did you change due to issues with amiberry?

Yes actually, and I was only playing SuperOffRoad and Lemmings...

I found an older Binary I built on RPi5 Bookworm back in December.
Maybe give this a try and see if the results are better than what you're getting now...

Amiberry v5.7.2 202412

pkg_origin="source" pkg_date="2024-08-05T16:57:07-04:00" pkg_repo_type="git" pkg_repo_url="https://github.com/BlitterStudio/amiberry" pkg_repo_branch="v5.7.2" pkg_repo_commit="d4418a16827d0edd619874405d990725b908b82a" pkg_repo_date="2024-06-06T16:22:44+02:00" pkg_repo_extra=""

Just replace the files as needed and make the binary/sh executable (chmod 755).
I have not gone back and tried this binary myself, but curious what your results are if you do.

Here's an older Module script for v5.6.6 too if you want to try (don't forget the amiberry/*.diffs)
RetroPie 4.8.6 Amiberry v5.6.6 Setup Script

Edit: To be clear I've been using [video=HDMI-A-1:1920x1080@60D] in my cmdline.txt since day 1 on RPi5

{Too long and don't wanna read all that}

I have a save file that is zipped by default.

Never seen that before until now.

That error shouldn't have an impact on running a N64 game - can you please post the entire /dev/shm/runcomamnd.log file ?

Do you also get an error if you install the lr-mupen64plus-next N64 emulator and run the game with it ?

It seemed logical to buy a Pi 5 which was already 2 years after its release in 2023. Being a novice to Pi in general, it was quite a struggle but I basically succeeded in getting Jaguar Tempest 2000 to run on my Pi 3, only to find out the Pi 3 is WAY too slow for it. Retropie still isn't a simple install, but once again with a lot more effort Tempest is at least installed, and very smoothly is running through its demo screens so it appears that Pi 5 is fast enough to play it. But controls don't work - more struggle to come. The method of screen rotation is very annoyingly not compatible with previous methods requiring jumping out of Emulationstation to set the rotation for every reboot (wtf where the developers thinking??). Pi 5 also lacks a sound jack requiring consumption of a USB port and the sound isn't working correctly with the adapter. I would say a Pi 5 is a poor option for use with Retropie. I'm sorry I bought it.

It seems that Retropie does not currently handle dual monitors. I am going to try a few different options. Maybe loading the Pi right into Mame, or maybe start an OS with retroarch and load a core.

More to come….

@mitu I don't remember I haven't booted Linux on arcade in a while. Sorry.

@roslof Do you have a folder with "lr-mame" 0.278 for rpi5 64bit that you can share? Thanks

@BlackLord
note : my understanding is that this modified genplus-gx core is breaking some stuff, so it is not recommended to replace the original genplus-gx core by it (which is probably what you did)