Raspberry Pi 5 - official announcement
-
@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
-
@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.
-
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
-
@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
-
@mitu That worked perfectly, thanks
-
@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. -
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 forlr-mupen64plus
, howeverlr-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 thelr-mupen64plus-next
core again and make sure you have eithergl
orglcore
as Retroarch's video driver ? -
@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
-
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")
-
-
@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
yieldsLinux 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.
-
@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. -
@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.
-
@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 ? -
Thank you for all your hard work and dedication!
looking forward to an official release at some point.
I just like to tinker on my retro-pie, like DBX says to me -
Sent https://github.com/RetroPie/RetroPie-Setup/pull/3823 to fix detection in setup script.
-
@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.
-
@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 -
@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.
-
@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!
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.