Raspberry Pi OS Bookworm Released

retropieuser555

@windg funnily enough I noticed this on 64bit bookworm build on pi 4 , but I suspected it was my TV/display as I couldn't replicate the error consistently. I did find it in Retroarch as well, not just on standalone emulators like mupen64plus , flycast or scummvm (tbf haven't played much of scummvm to test). I found it most common playing donkey Kong 64, but that could just be because I happened to play a few hours of that game recently moreso than anything else. If I'd played hours in something else perhaps I could replicate it

windg

@mitu said in Raspberry Pi OS Bookworm Released:

@windg Are you experiencing this issue ? Check dmesg for the error reported in the issue.

I checked dmesg but didn't find this error maybe because I tried the command after rebooting the system, I tried to connect from SSH when the system froze but it wasn't possible. Thanks!

windg

@retropieuser555 Thank you! At least now I know that I don't have a hardware problem.

RapidEdwin08

I may be experiencing this issue as well, I have not dmesg'd it, I honestly thought it was Dreamcast mem leak at first, but then the issue still occurred using lr-flycast on x2 different Pi4's with same build.

Bookworm Lite 64bit, TDE, RetroPie 4.8.5, and dtoverlay=vc4-kms-v3d build working perfectly for me except this black screen issue.
Screen goes black, but can here sound in background, just black screen, ssh still accessible.

Tried adding this to config .txt as well:

hdmi_force_hotplug=1

I will try the fix mentioned in this issue and see if it helps:

sudo rpi-update pulls/5684

Thanks for the info.

windg

@mitu It was possible to reproduse the issue and take a log from dsmeg . I confirm, is the issue you had reference.

[ 1719.110492] vc4-drm gpu: [drm] *ERROR* Failed to allocate DLIST entry: -28
[ 1719.122901] vc4-drm gpu: [drm] *ERROR* Failed to allocate DLIST entry: -28
[ 1719.142546] vc4-drm gpu: [drm] *ERROR* Failed to allocate DLIST entry: -28
[ 1719.512824] vc4-drm gpu: [drm] *ERROR* Failed to allocate DLIST entry: -28
[ 1719.558539] vc4-drm gpu: [drm] *ERROR* Failed to allocate DLIST entry: -28
[ 1719.712749] vc4-drm gpu: [drm] *ERROR* Failed to allocate DLIST entry: -28
[ 1719.764220] vc4-drm gpu: [drm] *ERROR* Failed to allocate DLIST entry: -28
[ 1719.815609] vc4-drm gpu: [drm] *ERROR* Failed to allocate DLIST entry: -28
[ 1720.213005] vc4-drm gpu: [drm] *ERROR* Failed to allocate DLIST entry: -28

Full dsmeg log: https://pastebin.com/75t7DSy9

mitu

@windg well, if you feel adventurous, you can try to install the ~~latest~~ rpi-update kernel from the linked issue and see if it fixes it. But, if you have any drivers installed for one of your gamepads, they'll likely break since there's no corresponding headers installed.

windg

~~I will leave it for now, i~~t is obvious that the OS needs time before it can be used for our purpose.

Ok i installed the latest kernel, i reinstall also xpad driver. So far no issues but will need few days to be sure.

windg

I used this setting in the last few days, with the kernel fix, and so far the system hasn't frozen again. If anyone wants to try it be careful, as mitu warns, it breaks the gamepads drivers.

mitu

@windg The fix has been merged into the RPI kernel, it will probably be in the next kernel package upgrade.

windg

@mitu This merge will add and the headers? Thanks!

RapidEdwin08

@windg said in Raspberry Pi OS Bookworm Released:

I used this setting in the last few days, with the kernel fix, and so far the system hasn't frozen again. If anyone wants to try it be careful, as mitu warns, it breaks the gamepads drivers.

Same here on x2 RPi 4's, No Issues since applying Kernel mentioned above.

I did not have to touch anything in regards to my generic xbox360 style joypad/receiver on either Pi.
Both of them worked out of the box before even installing xpad driver (or Kernel Fix) from RetroPie-Setup to begin with.
Ran lsusb -t and both appear to be using Driver=xpad at the moment.

windg

My gamepads (Logitech F310 and 710) are working too, but if i try to reinstall xpad driver it's failing.

mitu

@windg said in Raspberry Pi OS Bookworm Released:

@mitu This merge will add and the headers? Thanks!

Yes.

windg

I have build the cores For Bookworm Lite 64 bit in Pi5, can i transfer them in Pi4 with Bullseye or Bookworm Lite 64 bit? Do we know if the next stable image for Pi4 will use Bullseye or Bookworm? Thanks!

Edit: I transfer scummvm and it's working.

RapidEdwin08

@mitu said in Raspberry Pi OS Bookworm Released:

@windg well, if you feel adventurous, you can try to install the ~~latest~~ rpi-update kernel from the linked issue and see if it fixes it. But, if you have any drivers installed for one of your gamepads, they'll likely break since there's no corresponding headers installed.

Can you please provide or point me in the right direction to obtain the Kernel Hash# to Revert to Stock Kernel for Bookworm?

sudo rpi-update raspiOS-stock-hash-#

sudo rpi-update pulls/5684 definitely resolved the dlist memory issue on pi4.
But I think we're still waiting on 0fficial Kernel with dlistFix + headers...

mitu

@RapidEdwin08 said in Raspberry Pi OS Bookworm Released:

Can you please provide or point me in the right direction to obtain the Kernel Hash# to Revert to Stock Kernel for Bookworm?

https://www.raspberrypi.com/documentation/computers/os.html#how-to-get-back-to-safety

sseehra

Hello everyone,
I am currently having issues compiling mupenplus64 for retropie on Bookworm 32 bit full version. I have installed the libvulkan-dev package as recommended, and later used PiKISS to install the full vulkan package. Despite this, I am unable to compile the core. I have attached the log file as a google drive link. If anyone could assist me with this, I would greatly appreciate it.

Link: https://drive.google.com/file/d/1R5R8G55qsZVK04XgnqZUZoHM1JDhY8YU/view?usp=sharing

mitu

@sseehra said in Raspberry Pi OS Bookworm Released:

I am currently having issues compiling mupenplus64 for retropie on Bookworm 32 bit full version

On a 32bit system, RaspiOS will boot with the 64bit kernel and, because of it, Mupen64plus build scripts are assuming you're running a 64bit system. The build errors appear because of that.

Instruct the bootloader to not load the 64bit kernel and the build will work.

windg

@sseehra Add to the /boot/config.txt file this : arm_64bit=0 . It's what mitu suggest you.

You can access boot partition from a windows machine due to be fat32 or from SSH .

sseehra

@windg Thank you for the response. I ended up installing the 64 bit of bookworm, since I needed this version of the software for other purposes.