Raspberry Pi OS Bookworm Released

RapidEdwin08

@retropieuser555 Exactly, just replace with sirlemonhead fork, and #comment# out all the patches/diffs.

Don't bother trying to build Ion Fury from Experimental Section, it fails with FURY=1, but it will play just fine with this fork of eduke32.

Ion Fury .sh

_PORT_ "duke3d" "-gamegrp /home/pi/RetroPie/roms/ports/ionfury/fury.grp -game_dir /home/pi/RetroPie/roms/ports/ionfury"

mitu

@RapidEdwin08 said in Raspberry Pi OS Bookworm Released:

It would compile OK, but would not load at all, Log showed issues attempting to set any/all Video Modes.

It seems to start with a strange video mode, but after changing it from the game menu, it works for me. I'll take a look later on to see why it's not working right from the start.

RapidEdwin08

@mitu said in Raspberry Pi OS Bookworm Released:

It seems to start with a strange video mode, but after changing it from the game menu, it works for me. I'll take a look later on to see why it's not working right from the start.

Please elaborate, what setting did you change where?
I couldn't get the game to load at all to access the game menu?
I ask because this 0ld branch is still the only one that plays BloodCM for me.

mitu

Please elaborate, what setting did you change where?

The video resolution, under the Display -> Video Mode menu.

RapidEdwin08

ppsspp/lr-ppsspp fail to compile using v1.13.2, but both build fine using v1.16.6, plays well too.

~/RetroPie-Setup/scriptmodules/emulators/ppsspp.sh:
~/RetroPie-Setup/scriptmodules/libretrocores//lr-ppsspp.sh:

rp_module_repo="git https://github.com/hrydgard/ppsspp.git v1.16.6"

mupen64plus fails to compile without libvulkan-dev, just added it to depends (thanks @mitu for the info).

~/RetroPie-Setup/scriptmodules/emulators/mupen64plus.sh:

local depends=(cmake libsamplerate0-dev libspeexdsp-dev libsdl2-dev libpng-dev libfreetype6-dev fonts-freefont-ttf libboost-filesystem-dev libvulkan-dev)

dxx-rebirth failing to compile, x4 Errors in the log:
DxxRebirth_rps_2023-10-14_031312.log

retropieuser555

@RapidEdwin08 Ah I got mupen64plus to function by adding in this:- https://github.com/RetroPie/RetroPie-Setup/pull/3576 I didn't touch or add anything Vulkan related.

Any differences noticed btw? Compared to 32bit Buster RetroPie on pi 4, 007 Goldeneye definitely has a small speed boost. Couple of stutters playing Dam, before I'm sure the Dam was basically unplayable it was so slow.

Facility and Runway solid 60fps, no stutters.

Also was able to get Super Mario 64 upto UseNativeResolutionFactor = 3 in mupen64plus-GLideN64-highres and it still played at the 30fps it runs at. Don't think that is possible on 32 buster. Was running with an overclock on both systems if memory serves.

RapidEdwin08

@retropieuser555
I did try PSP BlazBlue Continuum Shift II + Prinny Can I Really Be The Hero, and man they were both Flying out-of-the-box not touching any Settings.
I actually have not tried anything for N64 yet, but if you really want a test try out Dinosaur Planet.

For mupen64plus, I got the fix from here could-not-successfully-build-mupen64plus.
I had the same error mentioned there, and same resolution.
I did not touch the swap settings, and upon looking it's already set to a static 750.

lr-dosbox fails to compile instantly with multiple errors:
ISO C++17 does not allow dynamic exception specifications

lr-mame2015/lr-mame2016 fail to compile with this error:
error: Cannot read opcodes file src/emu/cpu/mcs96/mcs96ops.lst [invalid mode: 'rU']

Appears to be due to issue with referencing 'rU' with Python 3.11.
For a fix I got lazy and just decided to stream edit on the fly and replace '~~rU'~~ with 'r' in all the *.py scripts in the source I found that referenced 'rU'
Note: They are the same *.py scripts for both, but in different locations.

~/RetroPie-Setup/scriptmodules/libretrocores/lr-mame2015:

function sources_lr-mame2015() {
    gitPullOrClone
	sed -i 's/rU/r/g' $md_build/src/emu/cpu/mcs96/mcs96make.py
	sed -i 's/rU/r/g' $md_build/src/emu/cpu/tms57002/tmsmake.py
	sed -i 's/rU/r/g' $md_build/src/emu/cpu/m6809/m6809make.py
	sed -i 's/rU/r/g' $md_build/src/emu/cpu/m6502/m6502make.py
}

~/RetroPie-Setup/scriptmodules/libretrocores/lr-mame2016:

function sources_lr-mame2016() {
    gitPullOrClone
	sed -i 's/rU/r/g' $md_build/src/devices/cpu/m6809/m6809make.py
	sed -i 's/rU/r/g' $md_build/src/devices/cpu/tms57002/tmsmake.py
	sed -i 's/rU/r/g' $md_build/src/devices/cpu/m6502/m6502make.py
	sed -i 's/rU/r/g' $md_build/src/devices/cpu/mcs96/mcs96make.py
}

windg

The strange thing that i have saw with Bookworm Lite is that is missing overscan settings and resolution settings in config.txt file. I don't know if this is intented or a bug of Pi OS devs.

dodonpachi

Glad to hear Retropie sort of already works right out of the box -- but I presume you all are testing this on a Pi 4, and not a 5?

retropieuser555

@RapidEdwin08 said in Raspberry Pi OS Bookworm Released:

@retropieuser555
I actually have not tried anything for N64 yet, but if you really want a test try out Dinosaur Planet.

Just gave Dinosaur Planet (02-05-23 enhanced version) a quick 10 min go this morning. The framerate counter is very low but given it's an unfinished game from Rare where they went as close to the max of the N64 without the console falling over that's not surprising.

The audio didn't stutter at all; it's probably running how the game is supposed to run as far as I can tell. I don't have an n64 or flashcart anymore to test that.

@dodonpachi yup, 64bit Bookworm Lite built on a pi4. I have preordered a pi 5 so will for fun have a go. Assuming anything will build at all, we'll find out

@windg I saw this in the raspi-config and thought it was strange, but then I don't have a TV or display that needs overscan changes so I'm not sure if it's just something that fixes itself or will be a problem for people who need to make that adjustment

mitu

@windg said in Raspberry Pi OS Bookworm Released:

I don't know if this is intented or a bug of Pi OS devs.

It's intended, resolution options have been removed some time ago from raspi-config. The Underscan should still be available, though it's possible it's not shown in all configurations (i.e. 64bit/wayland/etc.)

EDIT: to set manually the resolution, you have to edit the cmdline.txt file and add the options there - https://www.raspberrypi.com/documentation/computers/configuration.html#command-line-options.

windg

It looks that overscan settings will not work atleast for now :

From official announcement:
Compensation for displays which use overscan is tricky under Wayland, and we haven’t quite got it working yet, so this has been removed for now. The vast majority of displays nowadays don’t need it, but we will be putting it back when we have worked out how best to do it!

retropieuser555

Having a play around with silly stuff that I don't expect to work whatsoever; surprisingly lr-dolphin built and Animal Crossing loaded and the attract screen/demo played at normal 60fps.

Oddly I can't seem to get the controller to work, it's mapped in retroarch Controls but isn't responding (edit also tried changing the keyboard to game focus, still nothing). But I could get into the Retroarch menu with my hotkey combos. I would try other games but I imagine AC is the only thing likely to be playable on the old pi 4.

mitu

@RapidEdwin08 thanks for the tests.

PPSSPP was due for an update, it should be fine now after the bump to 1.16.6 (RetroAchievements !)

For mupen64plus, I got the fix from here could-not-successfully-build-mupen64plus.
I had the same error mentioned there, and same resolution.
I did not touch the swap settings, and upon looking it's already set to a static 750.

It depends on how much memory your Pi model has, you won't see the error if you have 4G/8G. Nethertheless, it needs some fixes - mostly for armhf/32bit - to compile.

lr-dosbox fails to compile instantly with multiple errors:
ISO C++17 does not allow dynamic exception specifications

I'll take a look later on, thank you,~~AFAIR dosbox-pure requires a specific GCC version.~~

retropieuser555

@mitu said in Raspberry Pi OS Bookworm Released:

PPSSPP was due for an update, it should be fine now after the bump to 1.16.6 (RetroAchievements !)

I haven't tested yet but apparently has CHD support now too, that's good as psp game files seem absolutely giant

mitu

@retropieuser555 said in Raspberry Pi OS Bookworm Released:

I haven't tested yet but apparently has CHD support now too, that's good as psp game files seem absolutely giant

Hm, that warrants an update, thanks for catching it.
EDIT: actually, that's in 1.17.0, not in this update. But both .pbp and .cso files (supported right now) support compresion.

retropieuser555

@mitu ahhh yeah sorry you're right, I had the nightly build of PPSSPP, forgot about that. The dev for that emulator seems to update it constantly, always seems to be something new there. You're right though, aside from a couple of games (retro city rampage became 8mb instead of 120 ish, and street fighter came down to 80mb), cso seems to compress roughly the same as chd.

duglor

@retropieuser555 What's the latest build date for retropie's PPSSPP?

retropieuser555

@duglor I use @ExarKunIv 's Extras scripts and get the ppsspp-dev script. It downloads the master branch.

https://github.com/Exarkuniv/RetroPie-Extra

ParadoxGBB

Hi there,

I love Retropie so also wanted to share my notes when I attempted to get it working on Bookworm 64-bit in case it helps with future development. Some of this will sound familiar but a few things seem new. I might try again with 32-bit just to see if some of these clear up --- initially, I really wanted to see if I could get some performance improvements with 64-bit but I was having enough issues, some even performance on 64-bit bullseye, so I think I'm going to give up on that.

mupen64plus does not compile (this is the case in Bullseye 64-bit as well) --- first install libvulkan-dev as described here: https://retropie.org.uk/forum/topic/34679/could-not-successfully-build-mupen64plus/5?_=1698098017277
Oddly, after installing the samba shares through RetroPie-Setup the shares were not set up correctly and I only saw a share called "nobody" that was exposed when I accessed it via my windows box (that I do not have access to). I ran the "fix permissions" routine and then the samba shares routine again, and that did it, but that share is still there. The Retropie-Setup logs indicated that package "wsdd" was not installed the first time (it does not appear to be listed as part of the new packages installed in the log).
Although in another thread someone reported that they were able to get Kodi to install on 64-bit Bookworm, for me the package details show only the binary option (no source) and selecting that reports "Sorry, but Kodi is not installable for your OS/Platform via RetroPie-Setup". Kodi does install via apt-get (Nexus!) but the configuration does not point correctly to the shares and there is an error when launching about a missing config file, but I'm having a tough time finding the output as it's not in the console anymore when I F4. Outside of that, the default out-of-box experience is better than in 64-bit Bullseye --- the default is headphones audio but once you switch it things seem to work, although I haven't been able to test much yet though. Overall I've been seeing a lot of behavioral quirks with Matrix over Leia (one example being https://forum.kodi.tv/showthread.php?tid=374638) and at least some of the issues appear to be platform OS-related, at least on Bullseye.
Oddly, my 8BitDo N30 with a USB wireless adapter is being detected in EmulationStation as an XBOX 360 controller, whereas on Bullseye it's identified correctly. Not sure if it's related or not but I've been having a hard time getting specific ports in retropie like RetroPie to work due to input detection issues (example https://github.com/mmatyas/openblok/issues/26) but that is probably not related to this. OpenBlok looks like it doesn't even compile at the moment in Bookworm 64-bit (https://github.com/mmatyas/openblok/issues/59).

Happy to collect logs or further diagnostics if requested.

Thanks for the hard work! I look forward to grabbing a Pi5 someday, but probably not until another board revision is released.