I have read about a similar issue in the forum, and the solution was to install the pulseaudio driver.
Before you try, back up your setup!

sudo apt install pulseaudio pulseaudio-utils

@mitu well I installed Steam through pi-apps, and I believe it installs box64 with Steam but when I was testing my theory I installed it for good measure together with wine and box86. Shotgun approach and all that, and I need wine for OpenBor and Mugen games.

But what initally happened was that if I installed Steam after RetroPie, Steam wouldn't finish the last installation step, when it asks to install a bunch of dependencies and then fails. So when I install Steam before Retropie, comment out the contents of sdl1.sh, sdl2.sh, and sdl12-compat.sh, (making sure all dependencies are met) and install RetroPie, it seems to use the system's sdl libraries to build things. So far everything's working as expected. Yeah, I see what you mean about using a translation layer. I'm ok with that. I can play TMNT Shredder's Revenge and a few others just fine.

Yeah, had no issues with Steamlink. Installed it and it worked right out of the box which is nice to have for games unwilling to run locally!

@dult-np ok I actually managed to compile but no rom would go past a black screen unfortunately. I guess we'll still have to stick to AetherSX2

Welcome to the forum :)

Wow, this hardware is also already retro. However, it can be refurbished for the 2020s.

For the Pi 4 or 5 there has been recently a thread https://retropie.org.uk/forum/topic/36439

If smooth N64 emulation is a must then it is a Pi5.

The current IPAC won't work. But if you are satisfied (also in terms of inputlag) you can use a IPAC for USB. You can also wire the GPIO directly as you have 12 buttons per player. I recently released a project which is compatible with the Pi5 (and earlier).

You will also need some adapters between the Pi's micro HDMI and the monitor connection (VGA, DVI, regular HDMI). Driving a CRT is a different story.
For the Pi 5 you will also need an USB audio device (any C-Media compliant stick will do).

Have fun!

@ExarKunIv said in [Pi5] Videos in EmulationStation "freeze" for about 1-2 seconds when stopping:

@roslof https://retropie.org.uk/forum/topic/35717/emulationstation-video-previews-on-raspberry-pi-5/22?_=1726283299547

Yes it has something to deal with that version of VLC.
So a downgrade is needed

Awesome! The details in that link did the trick. Ty @ExarKunIv

I think you meant to post this to https://forum.recalbox.com/, this is a RetroPie forum.

@sugarfree I tired this yesterday ish but I had to mess with everything before I added retropi on top of pi desktop. Works 90% ish you also have to take a file that is named the exact same thing and use the mv of cp command to move it into the right spot it seems

sudo mv splash.png /usr/share/plymouth/pix/splash.png

link text

@StuMcBill

So, I've updated the bootloader to "NVME/USB Boot" (got the green screen and rapidly flashing green light), removed the SD card, placed a USB stick (flashed with Raspbian Lite) into one of the USB3 slots, and it won't boot.

I get the message below:

"Raspberry Pi 5 - 4GB

bootloader: 6fe0b091 2024/06/05

update-ts: 1718268387

board: c04170 ce7cb976 d8:3a:dd:a6:ef:65

boot: mode USB-MSD 4 order f14 retry 0/128 restart 1/-1

SD: card not detected

part: 0 mbr [0x00:00000000 0x00:00000000 0x00:00000000 0x00:00 power: supply: RPi USB-PD 5000 mA CC1 PMIC: reset normal 0x0 us net: down ip: 0.0.0.0 sn: 0.0.0.0 gw: 0.0.0.0

tftp: 0.0.0.0 00:00:00:00:00:00

display: DISPO: HDMI HPD=1 EDID=ok #2 DISP1: HPD=0 EDID=none #0

Boot mode: USB-MSD (04) order f1

USB2[1] 000206e1 connected

USB2[1] 0020003 connected enabled

USB2 root HUB port 1 init

USB2[1] 000206e1 connected

USB2[1] 00200e03 connected

enabled

USB2 root HUB port 1 init

USB MSD stopped. Timeout: 25

Boot mode: SD (01) order f

seconds

Failed to open device: 'scard'

Failed to

(cmd 371a0010 status 1fff0001)

Boot mode: RESTART (0f) order 0

open device: 'scard (cmd 371a0010 status 1fff0001)

Boot mode: USB-MSD (04) order f1

USB2\1) 000206e1 connected

USB2(1) 00200e03 connected enabled

USB2 root HUB port 1 init"

Any ideas?

here is my config.txt

For more options and information see http://rptl.io/configtxt Some settings may impact device functionality. See link above for details Uncomment some or all of these to enable the optional hardware interfaces

#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

Enable audio (loads snd_bcm2835)

dtparam=audio=on

Pretends no audio formats are supported by HDMI display, forcing all sound out the 3.5mm headphone jack. May not be needed for all HDMI devices

hdmi_ignore_edid_audio=1

forces HDMI mode

hdmi_drive=2

#kernel
kernel=kernel8.img

Additional overlays and parameters are documented /boot/firmware/overlays/README Automatically load overlays for detected cameras

#camera_auto_detect=1

Automatically load overlays for detected DSI displays

#display_auto_detect=1

Automatically load initramfs files, if found

auto_initramfs=1

#hdmi

#resolution

framebuffer_width=1920
framebuffer_height=1080
hdmi_force_hotplug=1
hdmi_group=2
hdmi_mode=82

Enable DRM VC4 V3D driver

dtoverlay=vc4-kms-v3d
max_framebuffers=2

Don't have the firmware create an initial video= setting in cmdline.txt. Use the kernel's default instead.

disable_fw_kms_setup=1

Run in 64-bit mode

arm_64bit=1

Disable compensation for displays with overscan

#disable_overscan=1

Run as fast as firmware / board allows

arm_boost=1

[cm4]

Enable host mode on the 2711 built-in XHCI USB controller. This line should be removed if the legacy DWC2 controller is required (e.g. for USB device mode) or if USB support is not required.

#otg_mode=1

[cm5]
#dtoverlay=dwc2,dr_mode=host

[all]

0.3 seems to be the sweet spot. I did the change on GitHub

@dvojkaa for others there is this topic
https://retropie.org.uk/forum/topic/35350/no-audio-on-raspberry-pi-5/8

and it seems to work for him so i will try the same a write here again what happes

Almost ready. Some parts needs millimetre adjustments and finetuning (hence new 3d printed parts). Also a RPI badge is needed ...

IMG_2668.jpeg

@petrockblog said in Have I fried my Controlblock (or Pi5)?:

@StuMcBill If the Pi does not respond to a power button event, I would look for

The connection between the button and the ControlBlock: Do you see the same behavior with another button or, for example, just by using jumper wires like most simple buttons? The ControlBlock service installation: Does the ControlBlock LED stop pulsing and switch to a steady on state after booting? If not, the ControlBlock service is not running properly for some reason. The ControlBlock configuration: This is rare, but sometimes the power switch functionality is not enabled in the ControlBlock configuration in /etc/controlblockconfig.cfg.

Perhaps these items will give you a clue as to what is causing your observation?

Hi,

Thanks for the response.

I've not tried this, however, I have tried directly connected to GPIO of my Pi5 and my Pi4 - same behaviour - Controls work, but Power doesn't. I will check this I have tried toggling on and off in controlblock configuration - no change

I'll report back.

@Retrodade What kind of Repository do you use for "retropie-extra", this ?
I think this works fine (but I haven't tested yet Philips CDI games):
https://github.com/Exarkuniv/RetroPie-Extra

But I tested it with many other emulators like:
"AetherSX2 - PS2 Emulators" runs in 60Fps with my Pi5.
"Sega Supermodel 3" runs very well with my Pi5.

Start a PSX game with verbose logging enabled and post the log file here using pastebin .

@sleve_mcdichael Thanks sleve, typo on my side in the post. I was using "\". tried without the c$ as well. I installed winSCP and it popped up right away. Transferred all my files that way. Thanks!

@mitu
It works again. I re-install PipeWire and AudioPulse from rasPi config and everything works great. thanks for your support

Sorry, I have messed up my forum notification settings, but they should be good again now 🤦‍♂️
Sort for this delayed reply!

The ControlBlock driver was updated five months ago for some RPi 5 specifics, but if a new kernel version introduces changes to the device tree, the driver probably needs an update again. I will take a look at this! I will update the test script that comes with driver as well. It is not up to date anymore and not very helpful with the RPi 5.

@sleve_mcdichael Sorry about that, and thank you for your help. I will attempt that today!