Raspberry Pi 5 - official announcement

S_Dev88

@Darksavior He is part of the community just like so manny other YouTubers that have showed their work. Not sure why your linking a YouTuber to the supreme team because he showed there work and helps test things for the retro community, that’s his own business and not supremes.

windg

I think we talked to much for a 3rd party image, and we are and in the wrong topic. Please don't continued it here, that people come to learn about RPi5 and RetroPie.

roslof

@roslof said in Raspberry Pi 5 - official announcement:

It's possible that the new code is adding some lag, but I'll look into this more later this evening.

@Widge I synched to the changelist that preceded the -show-fps option and I'm still reliably getting what I'd describe as garbage sound (playing random data) periodically especially when multiple TIEs are on screen, or when there are explosions, but can occur at any time. So the issue is not with the addition of -show-fps. I didn't hear this in your video, so it's confusing where this is coming from.

FWIW, I build without network support.

I cannot reproduce this raspy sound issue with the mechafatnick version. Both games are pretty zippy, but is "feels" like the mechafatnick version has less dips in performance. Could be placebo. But the audio with DBX's version is definitely a problem for me.

EDIT: I should clarify that BOTH versions run SWT at 59.997 (60fps) at 1080x768 either stock or overclocked. Infrequent hitching on Hoth and the forest speeder bike scene. Only infrequent moments of slowdown overall (load transitions, cutscenes and a few hardcore scenes). A very enjoyable experience.

scapermoya

Hello,

I have a fresh build of Raspberry Pi OS 64 bit on a 8gb Pi 5. I installed RetroPi using the latest git build. I am trying to get various consoles working like many of you. It seems like several people here have been able to get N64 titles running and I have had no luck. I have tried multiple titles with 4 different emulators and all of them just kick me back to the ES screen after a couple seconds of dark. This is a new environment for me so apologies for the noobness.

I have been able to get Crash Bandicoot running for PSX, many titles for GBA/SNES no problem. Not sure what is wrong with the N64 titles. Sorry ahead of time I am not sure what logs to post.

thanks in advance.

Darksavior

@windg Sounds good. My main interest was in possibly asking to get AetherSX2 officially on RetroPie. I tried that person's 3rd party doom image and performance was all over the place. Gradius 5 and Contra Shattered Soldier ran at 60fps most of the time but bosses make them slow down to a crawl.

@retropieuser555 It's not running AetherSX2 on the desktop/Ubuntu.

mitu

@scapermoya Probably you're missing this config - https://retropie.org.uk/forum/topic/34627/raspberry-pi-5-official-announcement/103

roslof

@scapermoya said in Raspberry Pi 5 - official announcement:

It seems like several people here have been able to get N64 titles running and I have had no luck. I have tried multiple titles with 4 different emulators and all of them just kick me back to the ES screen after a couple seconds of dark. This is a new environment for me so apologies for the noobness.

I admit that so far, I've only been able to get the stand-alone mupen64plus to compile and run, which works with most N64 games when you run the mupen64plus-glide64 emulator from runcommand.

I have not been able to build lr-parallel (exp). Errors out with:

recomp.c:(.text+0x5f0c): undefined reference to `free_assembler'
/usr/bin/ld: recomp.c:(.text+0x61e4): undefined reference to `init_assembler'

Perhaps @retropieuser555 has some insights, since he was able to compile and run.

Separately, I could build lr-mupen64plus-next (opt) and lr-mupen64-plus (main), but I have not been able to run them. Verbose Logging shows both error out with:

[ERROR] [EGL]: #0x3009, EGL_BAD_MATCH
[ERROR] [KMS]: Error when switching mode.
/opt/retropie/supplementary/runcommand/runcommand.sh: line 1319: 15209 Segmentation fault

and both conclude with a segmentation fault.

Having fun playing with the stand-alone mupen64plus in the meantime.

roslof

@mitu said in Raspberry Pi 5 - official announcement:

@scapermoya Probably you're missing this config - https://retropie.org.uk/forum/topic/34627/raspberry-pi-5-official-announcement/103

If it helps the conversation, I've been running with that config change in the [all] section of config.txt.

Wrong section, perhaps?

mitu

@roslof said in Raspberry Pi 5 - official announcement:

If it helps the conversation, I've been running with that config change in the [all] section of config.txt.

It should be fine as long as you don't use the sdcard/image on a Pi that doesn't support 64bit (Pi2 or earlier).

roslof

@mitu said in Raspberry Pi 5 - official announcement:

@roslof said in Raspberry Pi 5 - official announcement:

If it helps the conversation, I've been running with that config change in the [all] section of config.txt.

It should be fine as long as you don't use the sdcard/image on a Pi that doesn't support 64bit (Pi2 or earlier).

Definitely running 64-bit just fine. Per post above, something to do with KMS switching. Searched for this KMS switching mode error and came up with no relevant hits:

[ERROR] [EGL]: #0x3009, EGL_BAD_MATCH
[ERROR] [KMS]: Error when switching mode.

While we can install retropie from a clean OS, there's always the possibility something is missing from config.txt or cmdline.txt since those wouldn't be included.

mitu

@roslof said in Raspberry Pi 5 - official announcement:

Definitely running 64-bit just fine. Per post above, something to do with KMS switching

Add the full runcommand log file (use pastebin.com and enable verbose logging) and post the output of kmsprint -m. Have you run rpi-update by any chance ?

roslof

@mitu said in Raspberry Pi 5 - official announcement:

Add the full runcommand log file (use pastebin.com and enable verbose logging) and post the output of kmsprint -m. Have you run rpi-update by any chance ?

Of course, mitu:

I haven't run rpi-update, but on initial install of the OS, I believe I updated everything to current with the recommended method.

Pastebin of verbose for lr-mupen-plus

Export of kmsprint -m

Connector 0 (32) HDMI-A-1 (connected)
   0 3840x2160@60.00  594.000 3840/176/88/296/+  2160/8/10/72/+     60 (60.00) P|D
   1 4096x2160@60.00  594.000 4096/88/88/128/+   2160/8/10/72/+     60 (60.00) D     256:135
   2 4096x2160@59.94  593.407 4096/88/88/128/+   2160/8/10/72/+     60 (59.94) D     256:135
   3 4096x2160@50.00  594.000 4096/968/88/128/+  2160/8/10/72/+     50 (50.00) D     256:135
   4 4096x2160@30.00  297.000 4096/88/88/128/+   2160/8/10/72/+     30 (30.00) D     256:135
   5 4096x2160@29.97  296.703 4096/88/88/128/+   2160/8/10/72/+     30 (29.97) D     256:135
   6 4096x2160@24.00  297.000 4096/1020/88/296/+ 2160/8/10/72/+     24 (24.00) D     256:135
   7 4096x2160@23.98  296.703 4096/1020/88/296/+ 2160/8/10/72/+     24 (23.98) D     256:135
   8 3840x2160@60.00  594.000 3840/176/88/296/+  2160/8/10/72/+     60 (60.00) D     16:9
   9 3840x2160@59.94  593.407 3840/176/88/296/+  2160/8/10/72/+     60 (59.94) D     16:9
  10 3840x2160@50.00  594.000 3840/1056/88/296/+ 2160/8/10/72/+     50 (50.00) D     16:9
  11 3840x2160@30.00  297.000 3840/176/88/296/+  2160/8/10/72/+     30 (30.00) D     16:9
  12 3840x2160@29.97  296.703 3840/176/88/296/+  2160/8/10/72/+     30 (29.97) D     16:9
  13 3840x2160@25.00  297.000 3840/1056/88/296/+ 2160/8/10/72/+     25 (25.00) D     16:9
  14 3840x2160@24.00  297.000 3840/1276/88/296/+ 2160/8/10/72/+     24 (24.00) D     16:9
  15 3840x2160@23.98  296.703 3840/1276/88/296/+ 2160/8/10/72/+     24 (23.98) D     16:9
  16 2560x1440@59.95  241.500 2560/48/32/80/+    1440/3/5/33/-      60 (59.95) D
  17 1920x1080@60.00  148.500 1920/88/44/148/+   1080/4/5/36/+      60 (60.00) U|D
  18 1920x1080@60.00  148.500 1920/88/44/148/+   1080/4/5/36/+      60 (60.00) D     16:9
  19 1920x1080@59.94  148.352 1920/88/44/148/+   1080/4/5/36/+      60 (59.94) D     16:9
  20 1920x1080i@60.00  74.250 1920/88/44/148/+   1080/4/10/31/+     60 (60.00) D     16:9
  21 1920x1080i@59.94  74.176 1920/88/44/148/+   1080/4/10/31/+     60 (59.94) D     16:9
  22 1920x1080@50.00  148.500 1920/528/44/148/+  1080/4/5/36/+      50 (50.00) D     16:9
  23 1920x1080i@50.00  74.250 1920/528/44/148/+  1080/4/10/31/+     50 (50.00) D     16:9
  24 1920x1080@30.00   74.250 1920/88/44/148/+   1080/4/5/36/+      30 (30.00) D     16:9
  25 1920x1080@29.97   74.176 1920/88/44/148/+   1080/4/5/36/+      30 (29.97) D     16:9
  26 1920x1080@25.00   74.250 1920/528/44/148/+  1080/4/5/36/+      25 (25.00) D     16:9
  27 1920x1080@24.00   74.250 1920/638/44/148/+  1080/4/5/36/+      24 (24.00) D     16:9
  28 1920x1080@23.98   74.176 1920/638/44/148/+  1080/4/5/36/+      24 (23.98) D     16:9
  29 1680x1050@59.88  119.000 1680/48/32/80/+    1050/3/6/21/-      60 (59.88) D
  30 1600x900@60.00   108.000 1600/24/80/96/+    900/1/3/96/+       60 (60.00) D
  31 1280x1024@75.02  135.000 1280/16/144/248/+  1024/1/3/38/+      75 (75.02) D
  32 1280x1024@60.02  108.000 1280/48/112/248/+  1024/1/3/38/+      60 (60.02) D
  33 1440x900@59.90    88.750 1440/48/32/80/+    900/3/6/17/-       60 (59.90) D
  34 1280x800@59.91    71.000 1280/48/32/80/+    800/3/6/14/-       60 (59.91) D
  35 1152x864@75.00   108.000 1152/64/128/256/+  864/1/3/32/+       75 (75.00) D
  36 1280x720@60.00    74.250 1280/110/40/220/+  720/5/5/20/+       60 (60.00) D
  37 1280x720@60.00    74.250 1280/110/40/220/+  720/5/5/20/+       60 (60.00) D     16:9
  38 1280x720@59.94    74.176 1280/110/40/220/+  720/5/5/20/+       60 (59.94) D     16:9
  39 1280x720@50.00    74.250 1280/440/40/220/+  720/5/5/20/+       50 (50.00) D     16:9
  40 1024x768@75.03    78.750 1024/16/96/176/+   768/1/3/28/+       75 (75.03) D
  41 1024x768@70.07    75.000 1024/24/136/144/-  768/3/6/29/-       70 (70.07) D
  42 1024x768@60.00    65.000 1024/24/136/160/-  768/3/6/29/-       60 (60.00) D
  43 832x624@74.55     57.284 832/32/64/224/-    624/1/3/39/-       75 (74.55) D
  44 800x600@75.00     49.500 800/16/80/160/+    600/1/3/21/+       75 (75.00) D
  45 800x600@72.19     50.000 800/56/120/64/+    600/37/6/23/+      72 (72.19) D
  46 800x600@60.32     40.000 800/40/128/88/+    600/1/4/23/+       60 (60.32) D
  47 720x576@50.00     27.000 720/12/64/68/-     576/5/5/39/-       50 (50.00) D     16:9
  48 720x576i@50.00    13.500 720/12/63/69/-     576/4/6/39/-       50 (50.00) D     2x|16:9
  49 720x480@60.00     27.027 720/16/62/60/-     480/9/6/30/-       60 (60.00) D     16:9
  50 720x480@59.94     27.000 720/16/62/60/-     480/9/6/30/-       60 (59.94) D     16:9
  51 720x480i@60.00    13.514 720/19/62/57/-     480/8/6/31/-       60 (60.00) D     2x|16:9
  52 720x480i@59.94    13.500 720/19/62/57/-     480/8/6/31/-       60 (59.94) D     2x|16:9
  53 640x480@75.00     31.500 640/16/64/120/-    480/1/3/16/-       75 (75.00) D
  54 640x480@72.81     31.500 640/24/40/128/-    480/9/3/28/-       73 (72.81) D
  55 640x480@66.67     30.240 640/64/64/96/-     480/3/3/39/-       67 (66.67) D
  56 640x480@60.00     25.200 640/16/96/48/-     480/10/2/33/-      60 (60.00) D     4:3
  57 640x480@59.94     25.175 640/16/96/48/-     480/10/2/33/-      60 (59.94) D
  58 720x400@70.08     28.320 720/18/108/54/-    400/12/2/35/+      70 (70.08) D

Cheers and thanks!
-Ros

mitu

I haven't run rpi-update, but on initial install of the OS, I believe I updated everything to current with the recommended method.

That's fine. No need for rpi-update at the moment.

Pastebin of verbose for lr-mupen-plus

Hm, seems the core is requesting an OpenGL core context (3.3), but that's not available on the Pi. I'll take a look, maybe the Pi5 is mis-detected and the core doesn't get built with support for the GLES3 context (like it's doing on the Pi4).

EDIT: did you switch the 'video_driver' to 'glcore' in RA's config ?

roslof

@mitu said in Raspberry Pi 5 - official announcement:

did you switch the 'video_driver' to 'glcore' in RA's config ?

It's set for gl. FWIW I just tried glcore and it didn't work either (as presumably expected).

mitu

@roslof said in Raspberry Pi 5 - official announcement:

It's set for gl. FWIW I just tried glcore and it didn't work either (as presumably expected).

Yes, I suppose it wouldn't work. Strange, on a quick test this doesn't happen here with the 'next' core. I'll take a closer look later on.

...

[INFO] [Environ]: SYSTEM_DIRECTORY: "/home/pi/RetroPie/BIOS".
[INFO] [Content]: Loading content file: "/home/pi/roms/n64/Legend of Zelda, The - Ocarina of Time (USA) (Rev B).n64".
[ERROR] [Environ]: GET_VARIABLE: mupen64plus-next-EnableN64DepthCompare - Invalid value.
[ERROR] [Environ]: GET_VARIABLE: mupen64plus-next-EnableShadersStorage - Invalid value.
[INFO] [Environ]: SET_HW_RENDER, context type: gl.
[INFO] Requesting OpenGLES3 context.
[libretro INFO] mupen64plus-next: Goodname: Legend of Zelda, The - Ocarina of Time (U) (V1.2) [!]

ChaosEffect

Early days for sure with all of this, but some great things so far! The Vulkan video driver really ups the ante on what can be done with lr-flycast-dev on the Raspberry Pi 5. Upscaling while still maintaining 60 FPS is a treat.

I have my Sinden lightguns working with lr-dolphin, and I'm wondering if I can use the Vulkan video driver there too. With the default video driver, some games are juuuust on the edge of full speed. However, the Vulkan video driver causes RetroArch to lock up with lr-dolphin. I then have to reboot my Pi. Anybody know of additional steps needed for lr-dolphin to use Vulkan more effectively (if possible yet)?

retropieuser555

@Darksavior said in Raspberry Pi 5 - official announcement:

@windg Sounds good. My main interest was in possibly asking to get AetherSX2 officially on RetroPie. I tried that person's 3rd party doom image and performance was all over the place.

@retropieuser555 It's not running AetherSX2 on the desktop/Ubuntu.

I'm curious when you run neofetch has he used bookworm/raspberry pi OS then somehow?

Sorry I probably wasn't clear, I got it by building RetroPie on top of Ubuntu 23.10, so I'm not running it from the desktop, my boot order goes to emulationstation and doesn't load the desktop.

I was going to use the server build of Ubuntu but for 23.10 couldn't use the steps others have used before on 22.04 to get RetroPie running.

windg

I have run AetherSX2 emulator in the past in Pi OS Bullseye 64 bit : https://retropie.org.uk/forum/topic/31676/aethersx2-ps2/10?_=1703147387237 but i don't remember what i did. So, i believe it will be possibly run this in the current version.

Edit: Ok, i run it in PI OS Bookworm Desktop.
I have to install fuse package for emulator to open. It's necessary also to install Vulkan i believe.

instructions tested with PI Os Bookworm 64 bit in RPi4 :

Download latest appimage : https://www.aethersx2.com/archive/?dir=desktop/linux
chmod +x the appimage
sudo apt install fuse
To run the emulator ./the_appimage

Maybe we can create a script to launch this with the help of matcbox window manager. Something similar with the standalone Duckstation from RetroPie-Extra repo.

DirtBagXon

@roslof said in Raspberry Pi 5 - official announcement:

@roslof said in Raspberry Pi 5 - official announcement:

It's possible that the new code is adding some lag, but I'll look into this more later this evening.

@Widge I synched to the changelist that preceded the -show-fps option and I'm still reliably getting what I'd describe as garbage sound (playing random data) periodically especially when multiple TIEs are on screen, or when there are explosions, but can occur at any time. So the issue is not with the addition of -show-fps. I didn't hear this in your video, so it's confusing where this is coming from.

FWIW, I build without network support.

I cannot reproduce this raspy sound issue with the mechafatnick version. Both games are pretty zippy, but is "feels" like the mechafatnick version has less dips in performance. Could be placebo. But the audio with DBX's version is definitely a problem for me.

EDIT: I should clarify that BOTH versions run SWT at 59.997 (60fps) at 1080x768 either stock or overclocked. Infrequent hitching on Hoth and the forest speeder bike scene. Only infrequent moments of slowdown overall (load transitions, cutscenes and a few hardcore scenes). A very enjoyable experience.

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

My Supermodel repo adds minimal to the MFN repo, but anything it does is direct from main supermodel additions or SDL's icculus libraries. One notable difference is the introduction of the "allegedly" more accurate Quad audio system. This stands out from your comments and did require some TLC in the configs, so if you are just swapping configs from pre/post could be the issue. As with increased emulation accuracy, more CPU cycles required, but all of the more recent engine updates have been skipped to save the Pi resources on the arm branch.

Haven't had any other reports of sound issues so tying this off as it's not really the right place for discussion of the issue.

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

retropieuser555

@windg from inside the desktop environment you mean? Or you were able to run it from emulationstation in Bookworm 64bit? I always get the segment fault. It's not the issue with fuse, as I've got that included and I found in ubuntu the error message when you're missing fuse says about requiring fuse to open the file. For me just now in bookworm it doesn't get as far as the fuse error message, just the segment fault