Raspberry Pi 5 - official announcement

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.

mitu

@roslof said in Raspberry Pi 5 - official announcement:

After some time, audio went away, but issues seem to involve my controller (DualShock 4 AKA "Wireless Controller) stealing Default audio.

The DS4 has audio out, so it tends to break the card index when connected (either via USB or Bluetooth) since it adds an extra audio card entry. You can disable it via udev I think, with a rule.
If you're using PulseAudio or PipeWire (recommended), then they have the tendency to recognize it as a 'headphone' and route the audio automatically to it.

... boot/config.txt settings,..

You shouldn't touch config.txt for audio - btw the new location is /boot/firmware/config.txt.

roslof

@mitu said in Raspberry Pi 5 - official announcement:

You shouldn't touch config.txt for audio - btw the new location is /boot/firmware/config.txt.

Understood. My efforts were due to older threads that advise this, example, trying to force HDMI with:

hdmi_force_hotplug=1
hdmi_force_edid_audio=1

Which seemed to have no affect with the modern Pi 5 setup (to your point). After noting failure, reverted to stock. Of course, the Pi 5 is not officially supported yet, so appreciate the additional information.

Cheers mitu

mitu

@roslof said in Raspberry Pi 5 - official announcement:

Which seemed to have no affect with the modern Pi 5 setup (to your point)

They won't have any effect for any Pi model starting with Bookworm, not only for Pi 5.

DirtBagXon

@mechafatnick said in Raspberry Pi 5 - official announcement:

@DirtBagXon I have to admit I got things working and left it.

Well thank you for the starting point

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)

I don't think any existing, or near future, Pi or reasonably priced PC for that matter, is going to run the latest -new3d engine with the teams recent commits to main.

The arm branch is static now as the -legacy3d engine hasn't seen any changes for some time, some of the guys tested -new3d from that period and was still a no-go on Pi5.

Thanks for the feedback,

finbarrobrien

@LivenCorpse said in Raspberry Pi 5 - official announcement:

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.

I see an issue with logic used to detect if we are running RetroPie on an RPI in /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh which is affecting the audio driver selection for RPI 5:

https://github.com/RetroPie/RetroPie-Setup/blob/master/scriptmodules/emulators/mupen64plus/mupen64plus.sh#L437

/proc/cpuinfo on RPI5 doesn't have the 'Hardware' type listed, so this check falls back to setting SDL_AUDIODRIVER=pulse for mupen64plus and this results in the Audio failing to start.

Manually overriding this in the script with SDL_AUDIODRIVER=alsa or leaving SDL_AUDIODRIVER unset provides sound, but for me it's a bit choppy.

mitu

@finbarrobrien said in Raspberry Pi 5 - official announcement:

I see an issue with logic used to detect if we are running RetroPie on an RPI in /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh which is affecting the audio driver selection for RPI 5:

Thanks for the heads-up. It's indeed a bad detection case with the latest kernel (see https://retropie.org.uk/forum/topic/34627/raspberry-pi-5-official-announcement/277?page=14 above).

roslof

@mitu said in Raspberry Pi 5 - official announcement:

The DS4 has audio out, so it tends to break the card index when connected (either via USB or Bluetooth) since it adds an extra audio card entry. You can disable it via udev I think, with a rule.

Sticking with PulseAudio for the moment, I went ahead and installed pavucontrol, launched the desktop, ran the app and selected the Configuration tab. Was able to easily disable the DS4 speaker as an audio card and lock HDMI.

Worked perfectly and persists across boots and such. All audio is finally working.

I looked around my directories to see what it modified (including /etc/pulse, /etc/udev, /etc/alsa) and was unable to find any modified files, but it's an easy (albeit weird) solution. Will keep trying to find what it tweaked so a manual non-Desktop solution for the Bookworm/PA/DualShock 4 combo can be used.