@Lolonois said in usb boot from 5tb hdd:

@korn16ftl3 the legacy format is root=/dev/sda1 (or whatever drive and partition holds / (the root filesystem). Same format a la /dev/sda1 goes for /etc/fstab.

FWIW, there is a good reason why the legacy format is discouraged: https://wiki.archlinux.org/title/Persistent_block_device_naming

I haven’t read that link yet but the sda and sdb are all determined by the order of of detection at boot up or order of being plugged if I’m not mistaken so o can understand how this is discouraged and no longer the way to do things.

On a positive note I did get this all working with BOTH the original 5tb and the later 12tb hard drives. The solution…..so it all in Linux. I’ll write a guide here in this thread to help others and maybe a separate one individually so it can be stickied and not follow this trail of confusing stuff?

Long story short I/we were on the right patch to begin with…just don’t use windows to change to gpt for some reason that screw’s it all up.

Simple rundown is as follows:
Write SD boot firmware to SD card with pi imager> boot SD boot firmware sd card in pi >Write retropie image to 2+tb device > write raspberry pi OS to micro SD card > boot raspberry pi OS from SD > ensure all updates and such (use the config editor with the raspberry pi imager to speed up a few things like ssh and WiFi setup) > ensure GParted and gdisk are installed > use gdisk to change hard retropie drive to GPT > use GParted to expand the root file system > check the retropie partitions partuuid in the cmd prompt > edit the cmdline.txt partuuid to match the ones you just looked up > mount the root drive for the retropie storage device with cmd prompts > load the FStab with nano > edit both partitions partuuid to the corresponding ones you just found > unmount > attempt boot

It does give some errors upon the first boot after this process and scans the hard drive and says it’s in emergency mode because it can’t boot the kernel. Just let the hard drive finish its scan and then when you can’t do anything more (it won’t even do anything if you hit enter to continue) just unplug the pi and plug it back in everything should boot accordingly and be fine after that.

Which EmulationStation version are you using ? Perhaps you need to quote the path to the emulator, since it has spaces in it, or try to rename the "Project64 3.0" folder to not have spaces in it. How is the es_systems.cfg file set-up for the N64 system ?

@mitu I'll go to the Streets of Rage Remake and the BennuGD forum and ask if they can help sort this out. I might have to write to the developers in Spanish at BennuGD, but I'm thinking that it might give them a heads up on what's going on with the SorRMaker.dat file. Thanks for letting me know about what goes on when the core is created and your response on this issue. I'll keep you posted if any of them gives some feedback.

@Azuli they are running a newer version of it. we are not.
they might of worked out something with the dev to have it included in the build.

we are running the last version that was free before the dev closed source it. or something along those lines

@Renetrox ок, at openbor's github page, at download section i see OpenBOR-Linux-x64-v4.0.Build.7533.AppImage and OpenBOR-Linux-x86-v4.0.Build.7533.AppImage

https://github.com/DCurrent/openbor/releases/tag/v7533

how integrate it in pi's retropie?

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

I guess it should be added to retropie setup scripts ?

The version installed for ARM is from before the split happened, as far as I know.

xpadneo is exclusively used for Bluetooth connected controllers, it will not be used for controllers that are connected via USB.
EmulationStation crashing usually means the controller's USB connection is not stable and it keep disconnecting. You can run dmesg -w from an SSH connection while the controller is connected and you start EmulationStation to see if the connect/disconnect events are printed.

@mdarr007 said in 64 bit Retropie for Dolphin?:

Anyway it seems Dolphin is not available to me on my new Pi4 for some reason

As @sleve_mcdichael mentioned, installation needs a 64bit OS and also a recent OS. Do note that the Pi4 is underpowered for running Dolphin (Gamecube or Wii games) and the games will not run fullspeed on the system.

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

{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.