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

    Raspberry Pi 5 - official announcement

    Scheduled Pinned Locked Moved General Discussion and Gaming
    rpi5raspberry pi 5
    599 Posts 67 Posters 492.4k Views
    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.
    • 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
                  • roslofR
                    roslof @mitu
                    last edited by roslof

                    @mitu said in Raspberry Pi 5 - official announcement:

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

                    Got it.

                    Okay. I can confirm that reinstalling the "retropiemenu" package created the ES Audio entry. Values are the same as I described above.

                    Would you recommend I reinstall latest Retropie-Setup over the existing installation and see if it allows for correct behavior?

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

                      @roslof said in Raspberry Pi 5 - official announcement:

                      Would you recommend I reinstall latest Retropie-Setup over the existing installation and see if it allows for correct behavior?

                      There's no 'over' - you just update like normal and you get the latest version.

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

                        @mitu said in Raspberry Pi 5 - official announcement:

                        There's no 'over' - you just update like normal and you get the latest version.

                        I see. I do update regularly, but have never seen the HDMI options in my menu(s) since initial installation. Similar to the Audio menu not appearing due to early adoption, and manually having to re-install the package, wondering if other functions are broken as a result of early installation -- and that the update script won't otherwise resolve. Will keep digging, and might play with a fresh install.
                        Cheers

                        EDIT: Another possibility I always consider is that when manually installing RetroPie-Setup for the first time, end-users like me don't get the packaged config.txt and cmdline.txt files and we kind of cobble together updates based on forum and Raspberry Pi knowledge. Wondering if there's something missing or misconfigured there.

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

                          @roslof said in Raspberry Pi 5 - official announcement:

                          EDIT: Another possibility I always consider is that when manually installing RetroPie-Setup for the first time, end-users like me don't get the packaged config.txt and cmdline.txt files and we kind of cobble together updates based on forum and Raspberry Pi knowledge. Wondering if there's something missing or misconfigured there.

                          Yes, what's missing is the official support.

                          1 Reply Last reply Reply Quote 1
                          • C
                            Cvore2004
                            last edited by

                            I recently got a pair of 8bitdo controllers and updated everything, now I can’t get audio from either hdmi, regardless of hdmi1/0/default audio settings. Still a noob with this stuff, but it sounds like maybe more than just the dualshocks are causing issues? Or maybe it’s just something in the update.

                            Wish i had more time to play with this stuff

                            M 1 Reply Last reply Reply Quote 0
                            • retropieuser555R
                              retropieuser555
                              last edited by

                              https://gitlab.freedesktop.org/mesa/mesa/-/issues/10242

                              I noticed this ticket earlier, this is the reason standalone PPSSPP, VVVVV and various other SDL2 based applications don't boot correctly on the pi5 (without a desktop). Apparently requires a kernel fix so hopefully the RPI Devs will work on that sooner than later.

                              Pi 5 4GB

                              Retroflag GPI with raspberry pi zero 2 w/ wifi

                              Retroachievements:- lovelessrapture

                              mituM 1 Reply Last reply Reply Quote 0
                              • M
                                mechanicchicken @Cvore2004
                                last edited by

                                @Cvore2004 said in Raspberry Pi 5 - official announcement:

                                I recently got a pair of 8bitdo controllers and updated everything, now I can’t get audio from either hdmi, regardless of hdmi1/0/default audio settings.

                                You could try setting your 8bitdo controller to mimic a different controller? On the Pro + ones holding start + x makes it mimic a switch pro, and start + y mimics an xbox controller I think?

                                That may solve some compatibility issues.

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

                                  @retropieuser555 said in Raspberry Pi 5 - official announcement:

                                  I noticed this ticket earlier, this is the reason standalone PPSSPP, VVVVV and various other SDL2 based applications don't boot correctly on the pi5 (without a desktop). Apparently requires a kernel fix so hopefully the RPI Devs will work on that sooner than later.

                                  The fix is already done, it will be part of the next RP kernel release (6.6). In the mean time, enabling VSync should fix the issue for most SDL2 standalone applications.

                                  retropieuser555R 2 Replies Last reply Reply Quote 1
                                  • retropieuser555R
                                    retropieuser555 @mitu
                                    last edited by

                                    @mitu Would that need vsync settings specific to each program? Or there's a config that can be enabled when setting say VVVVV or PPSSPP?

                                    Pi 5 4GB

                                    Retroflag GPI with raspberry pi zero 2 w/ wifi

                                    Retroachievements:- lovelessrapture

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

                                      @retropieuser555 said in Raspberry Pi 5 - official announcement:

                                      Would that need vsync settings specific to each program?

                                      If it's SDL, then there's an env var that can be used (SDL_RENDER_VSYNC), otherwise is application settings specific.

                                      1 Reply Last reply Reply Quote 1
                                      • retropieuser555R
                                        retropieuser555 @mitu
                                        last edited by

                                        @mitu said in Raspberry Pi 5 - official announcement:

                                        The fix is already done, it will be part of the next RP kernel release (6.6). In the mean time, enabling VSync should fix the issue for most SDL2 standalone applications.

                                        The fix I think has been backported into 6.1.

                                        If I run update and upgrade etc then rpi-update, does rpi-update look for the most recent bump 6.1.73? Or up to the bleeding edge most recent commit even if it's not bumped to 6.1.74 yet?

                                        Pi 5 4GB

                                        Retroflag GPI with raspberry pi zero 2 w/ wifi

                                        Retroachievements:- lovelessrapture

                                        mituM 1 Reply Last reply Reply Quote 0
                                        • TPRT
                                          TPR
                                          last edited by

                                          Is there a recommended solution to port a Pi 4 build over to the Pi 5 board without having to start over from scratch?

                                          ExarKunIvE retropieuser555R 2 Replies Last reply Reply Quote 0
                                          • ExarKunIvE
                                            ExarKunIv @TPR
                                            last edited by

                                            @TPR unfortunately no.

                                            You can copy your roms and config files. But that's about it

                                            RPi3B+ / 200GB/ RetroPie v4.5.14, RPi4 Model B 4gb / 256gb / RetroPie 4.8.2
                                            RPi5 4gb / 512gb / RetroPie 4.8.9 -Basic
                                            Maintainer of RetroPie-Extra .

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