Raspberry Pi 5 - official announcement

costin

I've just installed RetroPie manually following the docs and advice in this thread (installed bookworm lite 64, ran retropie setup script from github, added kernel=kernel8.img to config.txt). It went ok but I couldn't configure it to run emulationstation on boot. Turns out that the retropie script detects "x11" platform and not "rpi", so it just creates a .desktop file. scriptmodules/system.sh detects the following:

__platform_flags=([0]="" [1]="64bit" [2]="gl" [3]="vulkan" [4]="x11")

costin

It seems the script tries to detect the platform based on the "Hardware" line in /proc/cpuinfo, but that line doesn't appear on my system. This page claims that the Hardware line isn't available (anymore?) and userspace code should use other ways to detect SoC.

Edit: my /proc/cpuinfo is here.

roslof

@mitu said in Raspberry Pi 5 - official announcement:

Your log shows the error for lr-mupen64plus, however lr-mupen64plus is not available for 64bit ARM - are you running a 32bit system (with the 64bit kernel) ? It doesn't seems so, from the log you posted earlier. Can you try with the lr-mupen64plus-next core again and make sure you have either gl or glcore as Retroarch's video driver ?

Hmm. Yes, very odd that lr-mupen64plus was installed (12/16). At this time, I no longer see it in retropie_setup's "main" section, so that's correct and the script is there, so that is proper. I nuked it from emulators.cfg and removed the folder completely so as not to distract...

For the record, uname -a yields

Linux retropie5 6.1.0-rpi7-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24) aarch64 GNU/Linux

For lr-mupen64plus-next, I'm still puzzled where the glcore logging is coming from.

Primary retroarch.cfg:

video_driver = "gl"

I also temporarily renamed retroarch.cfg so it rebuilt a fresh one and same issue occurs.

I checked for overrides in configs/n64/retroarch.cfg for video_driver and scanned the n64 directory and couldn't find anything of interest.

Will keep looking. Since I may be the only person with this problem, I'm thinking it's likely due to transferring some configs and such from the rpi4b, but I was fairly careful with this and never really played with glcore.

windg

@costin Someone else have the same issue recently. I didn't have this issue when i setup RetroPie 1 month ago, i don't know if something changes in the meantime. Here is the topic: https://retropie.org.uk/forum/topic/34901/autostart-to-es/3, it looks that you have to modify autostart.sh file, but i don't know what line, maybe @mitu can help with this.

mitu

@costin said in Raspberry Pi 5 - official announcement:

t seems the script tries to detect the platform based on the "Hardware" line in /proc/cpuinfo

It only looks for BCM and then it uses the Revision number to calculate the Pi model. But it seems the latest kernel removes any platform info (see https://github.com/raspberrypi/linux/issues/5783) so the detection fails.

You can run the setup with

sudo __platform=rpi5 ./retropie_setup.sh

to skip the detection, until the platform query is fixed in RetroPie-Setup.

mitu

@roslof said in Raspberry Pi 5 - official announcement:

Linux retropie5 6.1.0-rpi7-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24) aarch64 GNU/Linux

You may be experiencing the mis-detection mentioned by @costin earlier. Can you re-install the -next core by starting the setup script with the platform override I posted earlier on ?

Retrodade

Thank you for all your hard work and dedication!
looking forward to an official release at some point.
I just like to tinker on my retro-pie, like DBX says to me

costin

Sent https://github.com/RetroPie/RetroPie-Setup/pull/3823 to fix detection in setup script.

roslof

@mitu said in Raspberry Pi 5 - official announcement:

You may be experiencing the mis-detection mentioned by @costin earlier. Can you re-install the -next core by starting the setup script with the platform override I posted earlier on ?

Yup. You nailed it as always @mitu. I rebuilt with your recommendation sudo __platform=rpi5 ./retropie_setup.sh which yielded new RA-based errors. I needed to rebuild RetroArch and struggled a bit. I went ahead and merged in @costin 's changelist, rebuilt RetroArch and that took care of things for N64.

Cheers @mitu. Thank you as always.
Same to you, @costin. Perfect timing.

Update: Worth noting that although the previously suggested override allowed lr-mupen64plus-next to be built, I noted performance issues. I decided to rebuild it again without the override and using costin's update to system.sh and the performance issues are gone. Early check shows I can now run Star Wars Rogue Squadron at 2X/60.00 fps.

roslof

@DirtBagXon said in Raspberry Pi 5 - official announcement:

So @roslof - a name from the distant past... :)

:) Good to be on the same thread with you again.

...so if you are just swapping configs from pre/post could be the issue.

Right, I'm actually sharing configs with the MFN version. Sounds like that's no-bueno and easy to sort. will try this in a bit.

Glad the FPS counter is of use, was a 2 line change so can be retrospectively added to any of the repos easily....

A great addition. Appreciated. Need to get a Sinden now... Yay, more toys.

Cheers DBX
-ros

mitu

@costin said in Raspberry Pi 5 - official announcement:

Sent https://github.com/RetroPie/RetroPie-Setup/pull/3823 to fix detection in setup script.

That's not enough, since it only detects the Pi5, but all Pi models are affected.

costin

@mitu I've added all the info I thought might be useful to the commit description, in case someone decides to go with another fix.

Thanks for help!

mitu

@costin said in Raspberry Pi 5 - official announcement:

@mitu I've added all the info I thought might be useful to the commit description, in case someone decides to go with another fix.

We added a (similar) fix now in RetroPie-Setup, which should solve the problem of RPI being mis-detected with the latest RaspiOS kernel. Thanks for reporting it.

LivenCorpse

From my own experience I didn't need that kernel=kernel8.img line in the boot configs up until I tried to run n64 emulators.

I kept getting a segmentation fault in the runcommand.sh script initially. After searching around if anyone else encountered this problem I saw plenty of users in this thread working with n64 emulators just fine. That lead me to the kernel8 config and now all Mupen64 based emulators work... sortof. GlideN64 based emulators don't have audio, which sucks cause those ones have the best renderers it seems. Going in the right steps though.

S_Dev88

Has anyone had this issue with EmulationStation on the pi 5 after updating mesa to 23.3 and then updating sdl2?

1ibEGL fatal: DRI driver not from this Mesa build ('23.3.1 (git-bcdc2b044d)' vs ‘23.2.1-1"bpo12+rpt2')

If you update mesa alone to 23.3 there seems to be no issues but once you update sdl2 and reboot, EmulationStation will not load.

Retrodade

Has anyone tried li-citrus for 3Ds in pi5?
hoping it will work on a pi5
Thank you

mechafatnick

Did you guys have sound issues? everything else works for me (aside from 1fps in some games :D) but i don't get any sound at all. I've tried switching the engine between pulse/alsa

mechafatnick

@DirtBagXon I have to admit I got things working and left it. I created configs that seemed to get the best settings out of most games, but with the Pi5 they should be changed anyway!

On the pi4, you HAD to use the legacy 3d flag to get any kind of reasonable performance, but with the pi5 it may not be needed (or maybe only for the most demanding games)

mechanicchicken

@mechafatnick Which micro hdmi port are you using? I found sound only worked out of port 0 not port 1

roslof

@mechafatnick said in Raspberry Pi 5 - official announcement:

Did you guys have sound issues? everything else works for me (aside from 1fps in some games :D) but i don't get any sound at all. I've tried switching the engine between pulse/alsa

I'm literally struggling with this now. I've had audio working then not working in-game and sometimes with my video snaps. After some time, audio went away, but issues seem to involve my controller (DualShock 4 AKA "Wireless Controller) stealing Default audio. Removing the controller currently allows audio to play for me (in-game and with in-game videos).

Otherwise, also been going back and forth with PulseAudio + ALSA controls + + /boot/config.txt settings, retropie_setup audio settings (setting Default and such) and researching previous issues. Would like a one-stop guide to proper, modern settings, since old threads provide information not necessarily relevant to current issues.