Raspberry Pi 5 - official announcement

TPR

Is there a bookworm equivalent of jstest? I'm trying to set up Hypseus and the previous button number assignments no longer seem to work. I can't figure out what the equivalent for select & start would be in this:
[KEYBOARD]
KEY_UP = 273 114 14
KEY_DOWN = 274 102 15
KEY_LEFT = 276 100 16
KEY_RIGHT = 275 103 17
KEY_BUTTON1 = 306 97 2
KEY_BUTTON2 = 308 115 1
KEY_BUTTON3 = 32 113 4
KEY_START1 = 49 0 10
KEY_START2 = 50 0 11
KEY_COIN1 = 53 0 9
KEY_COIN2 = 54 0 7
KEY_SKILL1 = 304 119 3
KEY_SKILL2 = 122 105 6
KEY_SKILL3 = 120 107 8
KEY_SERVICE = 57 0 0
KEY_TEST = 283 0 0
KEY_RESET = 284 0 0
KEY_SCREENSHOT = 293 0 0
KEY_QUIT = 27 113 0 0
END

mitu

Is there a bookworm equivalent of jstest?

Yes, it's the same - jstest. If you have an issue that manifests only under Bookworm, I suggest opening a separate topic. Bookworm support, just like the Pi5, is still in beta.

TPR

@mitu Looks like I got it working! Thank you!

mitu

@TPR said in Raspberry Pi 5 - official announcement:

Getting the following error trying to install Yabasanshiro.

That's a generic installation error and doesn't exactly show what's wrong. A build log would be better, but it's not needed since I could reproduce it. As a rule of thumb, posting this kind of pictures doesn't help - they just show a generic installation error without context or the actual error message, so please don't post them. If you wish to add some info, get the actual log file from $HOME/RetroPie-Setup/logs and post the error message shown during the build.

In this case, yabasanshiro has issues with 64bit ARM, it needs to be fixed or maybe disabled for this arch.

TPR

@mitu Thank you for the update!

abj

Did you try with lr-yabause ?

Maybe lr-yabashansiro can fill the gap, it's running on a 64 bit system, but it doesn't work for now.

TPR

@abj said in Raspberry Pi 5 - official announcement:

Did you try with lr-yabause ?

Maybe lr-yabashansiro can fill the gap, it's running on a 64 bit system, but it doesn't work for now.

lr-yabause seems to have a lot more games that crash after the Saturn logo screen. I added the scriptmodule for lr-yabashanshiro but it comes up as red in the retropie-setup-script since it's flagged for Pi4.

Is there a way to change the scriptmodule to force it to install on the Pi 5?

ExarKunIv

@TPR you can try, but its not going to work. it fails to install

but all you have to do is remove all rpi4 from the rp_module_flags="!all rpi4" line in the script
and try it

TPR

@ExarKunIv said in Raspberry Pi 5 - official announcement:

@TPR you can try, but its not going to work. it fails to install

but all you have to do is remove all rpi4 from the rp_module_flags="!all rpi4" line in the script
and try it

Yeah I tried that and I couldn’t get it to install either. Hopefully at some point it gets updated or someone gets it to work. It seemed to be the best Saturn option on the Pi4 and I think it still works a little better than the current Pi5 Saturn options in my limited testing.

For example, Die Hard Arcade seems to play better on the Pi4 with YabaSinshiro than on the Pi5 with either working core.

duglor

@mitu I hope the Pi5 supports the essentials that people would love to see....ps2, gamecube, wii, and the 3ds. I don't know what else there could be or how high it could go, but I am assuming those 4 are key to the success of the pi 5. Best of luck to everyone and best wishes and huge thanks to all involved with this project.

abj

@duglor
Emulation of PS2, Wii, Gamecube is already here with RetroPie to be the only system that have a PS2 emulator, but don't expect optimal performance, PI5 is weak for this systems.
I don't know about 3DS, i haven't saw a video about that system in Pi5.

TPR

Why does this current version of emulationstation treat controllers like XBOX 360 and PS2 Dual Shock differently? For example, when I configure the inputs, this is what I get:

XBOX 360:
START - Button 7
SELECT - Button 6
East - Button 1
South - Button 0
North - Button 3
West - Button 2
L - Button 4
R - Button 5
LT - Axis 2+
RT - Axis 5+
L Thumb - Button 9
R Thumb - Button 10

PS3 Dual Shock:
START - Button 9
SELECT - Button 8
East - Button 1
South - Button 0
North - Button 2
West - Button 3
L - Button 4
R - Button 5
LT - Axis 2+
RT - Axis 5+
L Thumb - Button 11
R Thumb - Button 12

WiiU Pro Controller:
START - Button 9
SELECT - Button 8
East - Button 1
South - Button 0
North - Button 2
West - Button 3
L - Button 4
R - Button 5
LT - Button 6
RT - Button 7
L Thumb - Button 11
R Thumb - Button 12

So the START & SELECT buttons are assigned to different button numbers. Retroarch doesn't seem to mind but if I'm using a stand alone core like Hypseus I can no longer use START + SELECT for the same functionality on the PS2 controller as I can on the XBOX 360.

I never had this issue on any of my Pi 4 builds.

I'm currently using emulationstation V2.11.2RP

My retropie setup script is at 4.8.7

mitu

@TPR said in Raspberry Pi 5 - official announcement:

Why does this current version of emulationstation treat controllers like XBOX 360 and PS2 Dual Shock differently? For example, when I configure the inputs, this is what I get:

Please don't clobber this topic with your issues - which are not really Pi5 related. Open separate topics for the problems you encounter on the latest RaspiOS.

abj

Did someone else have issue with the standalone mupen64plus-GLide64 ?
I have sound but no image - black screen. If i remember correct it was working before. This start to happen after i update core and main packages.

roslof

@abj said in Raspberry Pi 5 - official announcement:

Did someone else have issue with the standalone mupen64plus-GLide64 ?
I have sound but no image - black screen. If i remember correct it was working before. This start to happen after i update core and main packages.

Yeah, I've been seeing the same issue recently, but only on some ROMs and not others. Example: It runs fine with Conker's Bay Fur Day, but no longer with Crusin' USA. I spent a few hours last night trying to find any breaking change.

Can rule out these recent commits, which are fine:
eaa8a13 mupen64plus - fix building on armv8 with 64bit kernel/32bit userland
1da8bdd mupen64plus - add flag nodistcc to disable distcc for module

I tested the script prior to these ^^ changes and still yielded the black screen issue on some ROMs that used to properly render. Nothing of substance from runcommand.log, in fact, it's fairly blank other than showing code execution.

abj

I reinstalled from my backup, which is 3 weeks old, and then updated the: retropie-setup script, core packages, raspberry packages and everything is working correctly.
If i update the mupen64plus then the problem appears.

roslof

@abj said in Raspberry Pi 5 - official announcement:

I reinstalled from my backup, which is 3 weeks old, and then updated the: retropie-setup script, core packages, raspberry packages and everything is working correctly.
If i update the mupen64plus then the problem appears.

Okay, there were five (5) upstream changes made to the mupen64plus-core repo on May 3rd. UPDATE: Issue identified and explained here with temporary workaround.

mitu

@abj said in Raspberry Pi 5 - official announcement:

If i update the mupen64plus then the problem appears.

Which means this is not related to any OS/RetroPie updates, but with a core update. Just like @TPR before, you're reporting any issues un-related to the Pi5 on your installation here, just because you're using Bookworm on a Pi5. I'm going to lock this topic down if it's going to become a dumping ground for any issues appearing on RaspiOS Bookworm with/without PI5.

abj

@mitu
Sorry, my only purpose was to inform users to be careful with what is safe to update to avoid this problem. I will not post any issue again.

abj

@roslof i have already try this but without luck.