RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login

    Raspberry Pi 5 - official announcement

    Scheduled Pinned Locked Moved
    General Discussion and Gaming
    rpi5 raspberry pi 5
    66
    588
    238.3k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      costin @mitu
      last edited by

      @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!

      mituM 1 Reply Last reply Reply Quote 0
      • mituM
        mitu Global Moderator @costin
        last edited by

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

        1 Reply Last reply Reply Quote 5
        • L
          LivenCorpse
          last edited by

          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.

          F 1 Reply Last reply Reply Quote 1
          • S
            S_Dev88
            last edited by 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.

            1 Reply Last reply Reply Quote 0
            • ByteThisB ByteThis referenced this topic on
            • R
              Retrodade
              last edited by

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

              1 Reply Last reply Reply Quote 0
              • G gvx64 referenced this topic on
              • M
                mechafatnick
                last edited by

                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

                M roslofR 2 Replies Last reply Reply Quote 0
                • M
                  mechafatnick @DirtBagXon
                  last edited by

                  @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)

                  DirtBagXonD 1 Reply Last reply Reply Quote 0
                  • M
                    mechanicchicken @mechafatnick
                    last edited by

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

                    1 Reply Last reply Reply Quote 0
                    • roslofR
                      roslof @mechafatnick
                      last edited by 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.

                      mituM 1 Reply Last reply Reply Quote 0
                      • mituM
                        mitu Global Moderator @roslof
                        last edited by 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.

                        roslofR 2 Replies Last reply Reply Quote 0
                        • roslofR
                          roslof @mitu
                          last edited by

                          @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

                          mituM 1 Reply Last reply Reply Quote 0
                          • mituM
                            mitu Global Moderator @roslof
                            last edited by

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

                            1 Reply Last reply Reply Quote 1
                            • DirtBagXonD
                              DirtBagXon @mechafatnick
                              last edited by

                              @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,

                              Hypseus Singe for RetroPie: https://github.com/DirtBagXon/hypseus-singe
                              Hypseus Singe Games: https://github.com/DirtBagXon/hypseus_singe_data
                              Hypseus Discord: https://discord.gg/dgCsCfmRfJ

                              1 Reply Last reply Reply Quote 0
                              • F
                                finbarrobrien @LivenCorpse
                                last edited by

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

                                mituM 1 Reply Last reply Reply Quote 0
                                • mituM
                                  mitu Global Moderator @finbarrobrien
                                  last edited by

                                  @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).

                                  1 Reply Last reply Reply Quote 0
                                  • mituM mitu referenced this topic on
                                  • roslofR
                                    roslof @mitu
                                    last edited by 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.

                                    roslofR 1 Reply Last reply Reply Quote 0
                                    • roslofR
                                      roslof @roslof
                                      last edited by roslof

                                      Been playing around a lot with PulseAudio and Pipewire.

                                      With PulseAudio, I've been able to play sound in both ES-dev and with all emulators -- but experience intermittent asserts with any RetroArch core after launch and prior to game render with a "[Core Info] Error parsing chunk" in the runcommand.log file (Verbose Logging). Game could run one moment and fail on the next launch. 100% due to Pulse being enabled. Other than that, also solved my issue with the DualShock controller being identified as default audio (previous post).

                                      EDIT: The issue mentioned above with "[Core Info] Error parsing chunk" was related to RetroArch caching, and was resolved by disabling caching via RetroArch/Settings/Core/Cache Core Info Files. Root cause of the problem is unknown and whether or not the audio issues I've been having exacerbated the problem, but this solved my issue.

                                      With Pipewire, fairly fire and forget. From raspi-config Advanced settings, switched. Only issue is that I've been unable to get it to play audio in EmulationStation (noted with video-snaps) . ES Sound Settings is set correctly for DEFAULT/MASTER, and all emulators seem to launch fine.

                                      Wondering what others are running for audio and if you've experienced any anomalies.

                                      mituM 1 Reply Last reply Reply Quote 0
                                      • mituM
                                        mitu Global Moderator @roslof
                                        last edited by

                                        @roslof said in Raspberry Pi 5 - official announcement:

                                        Wondering what others are running for audio and if you've experienced any anomalies.

                                        Running the default (ALSA). You do need to go once through the Audio menu and choose your output (HDMI1/HDMI2), but that's about it.

                                        roslofR 1 Reply Last reply Reply Quote 0
                                        • roslofR
                                          roslof @mitu
                                          last edited by roslof

                                          @mitu said in Raspberry Pi 5 - official announcement:

                                          Running the default (ALSA). You do need to go once through the Audio menu and choose your output (HDMI1/HDMI2), but that's about it.

                                          Hmm. I'm running ALSA (RetroArch), but my RetroPie Audio menu (audiosettings) does not show HDMI1 or HDMI2 as options. Menu offers:

                                          • 0 MAI PCM i2s-hifi-0
                                          • M Mixer - adjust output volume
                                          • R Reset to default
                                          • P Disable PipeWire

                                          Mixer shows card as "vc4-hdmi-0" with "This sound device does not have any controls".

                                          Must have something misconfigured here.

                                          EDIT: @mitu Wondering if by "Audio menu" you meant from the ES retropie system menu (Settings)? If so, mine never showed up after install -- and if it's supposed to be there, wondering if it's because of the system bug when I first installed RetroPie fresh...

                                          mituM 1 Reply Last reply Reply Quote 0
                                          • mituM
                                            mitu Global Moderator @roslof
                                            last edited by

                                            @roslof said in Raspberry Pi 5 - official announcement:

                                            Hmm. I'm running ALSA (RetroArch), but my RetroPie Audio menu (audiosettings) does not show HDMI1 or HDMI2 as options. Menu offers:

                                            You're either not running the latest RetroPie-Setup or the PulseAudio/Wireplumber services are messing up the ALSA outputs.

                                            roslofR 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                                            Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.