Raspberry Pi OS Bookworm Released

mitu

Release announcement: https://www.raspberrypi.com/news/bookworm-the-new-version-of-raspberry-pi-os/

windg

For me the most important thing from the new release is the optimisation of the Firefox. I will try to install RetroPie to the new version tomorrow but if it fail I am not gonna search the reason or post here for help ofc.

Update: Ok, i tested it and from the few things i try and they don't work are: kodi , lr-flycast, Redream, lr-swanstation, splashscreens. Desktop is working .

mitu

Yes, Firefox being support as a full featured browser is a big win. I'll probably test the new OS once I finish some work related to it on the current release.

Things that will not work right now in RetroPie:

Wifi configuration will not work with Network Manager. This is the bit that I'm working on currently.
Drivers since most drivers depend on Linux kernel headers and package naming for kernel related packages has changed in bookworm and RetroPie hasn't learned the new naming.

retropieuser555

Had a go this morning. Install the lite 64bit version of bookworm, in doing so I used raspi-config to add my network.

Ran the usual manual install steps that you have in the Docs. Mupen64plus won't install for me but everything else I tried seems fine. Standalone PPSSPP installs fine, lr-flycast worked for me.

Splashscreens on 64bit won't work so that's optioned out in setup script for me as I'm on a 64bit flag.

Haven't tried to add a network from the wifi script in RetroPie yet.

Audio works straight away, on bullseye I needed to do some extra steps to get it working. So I guess Pipewire works better than Pulseaudio?

Edit:- standalone mupen64plus is probably not building due to this issue outlined here https://github.com/RetroPie/RetroPie-Setup/pull/3576

RapidEdwin08

@mitu said in Raspberry Pi OS Bookworm Released:

Things that will not work right now in RetroPie:

Wifi configuration will not work with Network Manager. This is the bit that I'm working on currently.

Drivers since most drivers depend on Linux kernel headers and package naming for kernel related packages has changed in bookworm and RetroPie hasn't learned the new naming.

I have a modified version of the WiFi configuration script I personally use that supports Network Manager already.
It's excessive and could use some cleaning up, but feel free to try and use anything you need from it.

https://github.com/RapidEdwin08/wifi-networkmanager

Still waiting to get my rPi5 4GB but will be trying out Bookworm on 0lder Pi0-4 for now.

windg

I am using Bookworm 64 bit Lite with latest RetroPie script, without modify anything. The emulators that i am using all running without performance issues. I have a question, my curent setup, is running under Wayland or i am using the previous driver ? Thanks

mitu

@windg said in Raspberry Pi OS Bookworm Released:

I have a question, my curent setup, is running under Wayland or i am using the previous driver ? Thanks

Wayland is used only for the desktop, is not a driver per-se, but a new display manager which replaces Xorg/X11. If you don't install the full RaspiOS (with Desktop), then you won't have wayland, nor the new sound server (pipewire) - but neither of them is required for RetroPie.

We've added support for Networks Manager to the WiFi module and for the Linux kernel packages, but not for the new desktop environment (Wayfire). Will probably add entries for both DE (wayfire with Wayland and openbox with Xorg).

EDIT: the ppsspp issue is caused by the newer glibc in_bookworm_, we'll need to update to a later ppsspp version than the one pinned in the RetroPie's installation scripts.

retropieuser555

@mitu said in Raspberry Pi OS Bookworm Released:

Wayland is used only for the desktop, is not a driver per-se, but a new display manager which replaces Xorg/X11. If you don't install the full RaspiOS (with Desktop), then you won't have wayland, nor the new sound server (pipewire) - but neither of them is required for RetroPie.

So Pipewire doesn't install off the bat and it's desktop dependent? It's interesting as on Bullseye audio would be broken and required extra steps to solve it, but oddly under Bookworm doing a manual install with the same steps the audio works straight away? So I guess there's other changes in that area not just Pipewire?

mitu

@retropieuser555 said in Raspberry Pi OS Bookworm Released:

So Pipewire doesn't install off the bat and it's desktop dependent?

Yes, the Lite image doesn't include it.

It's interesting as on Bullseye audio would be broken and required extra steps to solve it, but oddly under Bookworm doing a manual install with the same steps the audio works straight away

Are you using the audio over HDMI or the analog output ? The analog output works without any settings, for HDMI the audio menu in RetroPie should be able to configure it (but it's not yet automatic).

retropieuser555

@mitu said in Raspberry Pi OS Bookworm Released:

@retropieuser555 said in Raspberry Pi OS Bookworm Released:
Are you using the audio over HDMI or the analog output ? The analog output works without any settings, for HDMI the audio menu in RetroPie should be able to configure it (but it's not yet automatic).

Just using the HDMI audio that's output from HDMI0 with the video output, nothing unique in that regard.

windg

@retropieuser555 Audio works for me in both Bullseye and Bookworm with RPi4 after i set it manually from audio settings to HDMi0 and restarted the Emulationstation.

mitu

@retropieuser555 said in Raspberry Pi OS Bookworm Released:

Just using the HDMI audio that's output from HDMI0 with the video output, nothing unique in that regard.

That's strange, since the default ALSA audio output is Headphones if not configured.
EDIT: which Pi model are you using ?

retropieuser555

@mitu said in Raspberry Pi OS Bookworm Released:

@retropieuser555 said in Raspberry Pi OS Bookworm Released:

Just using the HDMI audio that's output from HDMI0 with the video output, nothing unique in that regard.

That's strange, since the default ALSA audio output is Headphones if not configured.
EDIT: which Pi model are you using ?

Just a standard raspberry pi 4 b model, can't remember the RAM size off hand.

Each time I just installed the 64 bit lite /no desktop version off raspberry pi imager, then run through the steps in RetroPie Docs Manual Install. It doesn't matter a great deal really each use case there is a solution, was just surprised the Audio worked without changes on bookworm whereas it didn't before under bullseye

RapidEdwin08

Had issues with eduke32 on Bookworm.
It would compile OK, but would not load at all, Log showed issues attempting to set any/all Video Modes.
I tried a few different versions/branches and was able to get this one working on Pi4 32/64bit:

~/RetroPie-Setup/scriptmodules/ports/eduke32.sh

rp_module_repo="git https://voidpoint.io/sirlemonhead/eduke32.git master 3191b5f41670ee9341f0298e155172c0ef760031"

I also #commented# out all the patches/diffs in the applyPatch section.

Ion Fury (in Exp Section) fails building, eduke32 fails to compile when attempting FURY=1 using this branch.
But I don't think it's needed anymore, as I can load Ion Fury just fine with this version of eduke32 mentioned.

Everything I tested seems to work, skyboxes, Ion Fury, and Duke Forces.

retropieuser555

@RapidEdwin08 Isn't the new commit
3191b5f41670ee9341f0298e155172c0ef760031
the master anyway that was last updated 2 years ago? RetroPie seems to point to
dfc16b0882fe6ed03aa3e9c7d4948a9ad309f23a
that is 4 years old itself.
I'd be curious if the new master works on 32bit buster anyway and could just be updated

RapidEdwin08

@retropieuser555 I tried several branches that I had luck with on other builds/devices, including the latest, and they all had same issue on Pi Bookworm, fails to set any/all video modes when loading.

#rp_module_repo="git https://voidpoint.io/terminx/eduke32.git master a9c797dcb60d4dfa2e21aed09e498132e59282ba"
#rp_module_repo="git https://voidpoint.io/terminx/eduke32.git master d890364d76e1553ae7d8b5b2fbef5e333c6d6123"
#rp_module_repo="git https://voidpoint.io/terminx/eduke32.git master 17844a2f651d4347258ae2fe59ec42dc3110506e"
#rp_module_repo="git https://voidpoint.io/dgurney/eduke32.git master 76bc19e2e55023ea5a17c212eab0e1e5db217315"

dgurney was the only one that actually works/loads after compile, but skyboxes are broken,
The rest do not load, feel free to try yourself, may be there's a newer version will work.

Edit: I did not try "3191b5f41670ee9341f0298e155172c0ef760031"
I thought "17844a2f651d4347258ae2fe59ec42dc3110506e" was newest commit...

retropieuser555

@RapidEdwin08 Ah you're right, I didn't notice you were looking at different user's forks, that makes sense. I'll mess around tomorrow at home, but we could just use the https://voidpoint.io/sirlemonhead/eduke32 fork if that's what works?

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.