Raspberry Pi 5 - official announcement

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

windg

@retropieuser555 Yes, from Desktop. I haven't try it yet from emulationstation and Pi 5. I believe it needs a window manager to run from ES.

The first time it ask for fuse package, after i choose a game it doest run it because of the opengl ES version that pi4 is using. I think it will work in Rpi5.

windg

I try it with Pi5 and with first try is crashing (segment fault) But after i add the kernel line, in the config.txt file, emulator is running. But it needs vulkan that i don't know how to install it to test games.

This is the error log after i try to run a game, i try also vulkan from pikiss project,but the result was the same :

ioannes@raspberrypi:~/Downloads $ ./AetherSX2-v1.5-3606.AppImage
Program Path: /tmp/.mount_AetherRfZMxw/usr/bin/aethersx2
AppRoot Directory: /tmp/.mount_AetherRfZMxw/usr/bin
DataRoot Directory: /home/ioannes/.config/aethersx2
Resources Directory: /tmp/.mount_AetherRfZMxw/usr/bin/resources
Loading config from /home/ioannes/.config/aethersx2/inis/PCSX2.ini.
BIOS Directory: /home/ioannes/.config/aethersx2/../../../../media/ioannes/R3TRO/PS2 BIOS Complete (All Regions)/EU/SCPH-35004 EU 150-001228
Snapshots Directory: /home/ioannes/.config/aethersx2/snaps
Savestates Directory: /home/ioannes/.config/aethersx2/sstates
MemoryCards Directory: /home/ioannes/.config/aethersx2/memcards
Logs Directory: /home/ioannes/.config/aethersx2/logs
Cheats Directory: /home/ioannes/.config/aethersx2/cheats
CheatsWS Directory: /home/ioannes/.config/aethersx2/cheats_ws
CheatsNI Directory: /home/ioannes/.config/aethersx2/cheats_ni
Covers Directory: /home/ioannes/.config/aethersx2/covers
Game Settings Directory: /home/ioannes/.config/aethersx2/gamesettings
Cache Directory: /home/ioannes/.config/aethersx2/cache
Textures Directory: /home/ioannes/.config/aethersx2/textures
Input Profile Directory: /home/ioannes/.config/aethersx2/inputprofiles
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation
Case insensitive sorting unsupported in the posix collation implementation
Numeric mode unsupported in the posix collation implementation
Vulkan: Failed to load required instance function vkGetDeviceProcAddr
Vulkan: Failed to load required instance function vkEnumeratePhysicalDevices
Vulkan: Failed to load required instance function vkGetPhysicalDeviceFeatures
Vulkan: Failed to load required instance function vkGetPhysicalDeviceFormatProperties
Vulkan: Failed to load required instance function vkGetPhysicalDeviceImageFormatProperties
Vulkan: Failed to load required instance function vkGetPhysicalDeviceProperties
Vulkan: Failed to load required instance function vkGetPhysicalDeviceQueueFamilyProperties
Vulkan: Failed to load required instance function vkGetPhysicalDeviceMemoryProperties
Vulkan: Failed to load required instance function vkCreateDevice
Vulkan: Failed to load required instance function vkEnumerateDeviceExtensionProperties
Vulkan: Failed to load required instance function vkEnumerateDeviceLayerProperties
Vulkan: Failed to load required instance function vkGetPhysicalDeviceSparseImageFormatProperties
Vulkan: Failed to load required instance function vkGetPhysicalDeviceFeatures2
Vulkan: Failed to load required instance function vkGetPhysicalDeviceProperties2
Vulkan: Failed to load required instance function vkGetPhysicalDeviceMemoryProperties2

retropieuser555

@windg vulkan is installed by default

Ah you're right, it's this 4kb vs 16kb problem. I wonder if ubuntu runs at 4kb rather than 16kb and that's why it works. Guess it being closed source software it'll be hard to know what's going on with aethersx2.

Do you find the window isn't full screen? I find I have to enter this for a 1080p tv to go full screen in the PCSX2.ini:-

MainWindowGeometry = AdnQywADAAAAAAAAAAAAFAAAB38AAARLAAAAAAAAABQAAAd/AAAESwAAAAAAAAAAB4AAAAAAAAAAFAAAB38AAARL
MainWindowState = AAAA/wAAAAD9AAAAAAAABBoAAAJxAAAABAAAAAQAAAAIAAAACPwAAAABAAAAAgAAAAEAAAAOAHQAbwBvAGwAQgBhAHIAAAAAAP////8AAAAAAAAAAA==
DisplayWindowGeometry = AdnQywADAAAAAAAAAAAAFAAAB38AAARLAAAAAAAAABQAAAd/AAAESwAAAAAAAAAAB4AAAAAAAAAAFAAAB38AAARL

I'm sure someone smarter than me can figure out the Hex of this for 720p, 768p, 4k displays that people would have

scapermoya

@mitu That worked perfectly, thanks

windg

@retropieuser555 i didn't check the window size, did you have success with the games?
The real issue is that the developer don't work on this anymore, one critical update and emulator will stop working.

mitu

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

@roslof I can't reproduce the error, even with a new install of the lr-mupen64plus-next.
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 ?

retropieuser555

@windg said in Raspberry Pi 5 - official announcement:

@retropieuser555 i didn't check the window size, did you have success with the games?
The real issue is that the developer don't work on this anymore, one critical update and emulator will stop working.

Yeah the games work fine. So load up the aethersx2 app without a rom, tell it where your ps2 bios is stored (can see you've done that based on your error above earlier).

Then select settings > Graphics and set renderer to Vulkan. Then you should be all set to try some games

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 ?