@Nash Thanks! My first guess would be that your wine executable is not set in your path.
So either you add the path to your wine executable to the $PATH variable or you put the path in front of the wine command like this:

trial2se = "XINIT-WM: /path/to/wine explorer /desktop=shell,1280x720 '/home/pi/RetroPie/roms/ports/Trials 2 Second Edition/trials2.exe'"

@aaronouthier said in Odroid XU4 SDL Problem Emulationstation:

I tried with --debug flag, however the screen is cleared by the crash dialog that comes up, so I can't read. I'll try tee'ing it to a text file.

That would have been useful to look, the other logs not so much. You can find the same log file in $HOME/.emulationstation/es_log.txt, there's no need to tee it.
Does detection works better on 22.04 - is the SBC detected as odroid-xu ?

@tar
The bit I used was about the size of the shaft/thread, or so I thought.. the smallest I owned.
I admit I DID go full speed.

I'm afraid I probably destroyed the board by now.

I was using a 1/16 drill bit made for all surfaces
alt text

I took the bits to a local do it yourself hardware place (Locally owned ace) and they tried to sell me 2 things, a borer and this screw removal kit..

alt text

I've tried all of them, none worked...

@retropieuser555 The touchscreen is connected in a case with a ribbon cable connected directly to the RPi.

Is it recognized as a joystick by the system (check dmesg after pairing it to see how it's detected) ? Does it work with jstest ?

In the end, I made a new retropie image and then made sure to properly configure the controller at startup. The other issue was related to faulty card reader.

@sugarfree said in Verifying write failed using Rpi Imager:

bad card reader

In my case a faulty card reader.

@jgraves Thank you very much for the brilliant idea with the diode!!!
This method suited me perfectly :)
But it is not a fact that it will suit others. Because in this case the "hot key" will be unavailable for other functions. (I do not use it).

@sugarfree said in Question about Vulkan on the RPi5.:

Is this still the right way to do it? Thanks!

Yes, since the PR is still not merged.

The status bar bug even occurs with the version installed by the stock wolf4sdl.sh script. For now I'll just stick with using the alternate script I created, which pulls from an older commit.

In a few days, when I have the time, I'll try to determine the exact commit where the bug begins. There also seem to be a couple other oddities with this port that I want to investigate at that time:

Redundant files with specific file names becoming necessary for the three expansion episodes to run. For example, three identical copies of AUDIOT.SOD --> AUDIOT.SD1, AUDIOT.SD2, AUDIOT.SD3. At least, if I remember the required file names correctly. There are multiple other files that require the same treatment.

And from a later commit (not effecting installs from the wolf4sdl.sh script up to this point in time)...

The game image being stretched to the full width of a 16:9 monitor, rather than preserving the original aspect ratio.

@mitu sorry was excited just had to set audio in retropie menu but some reason it didnt take the first 4 or 5 times
until i changed output to a diffrent output then back to hdmi .

FYI - "USE_OPENGL=0" seems to be the necessary flag. I can compile with or without "Polymer" and it will launch successfully.

@mitu

Nevermind, the </command> within es_systems.cfg under retropiemenu needed to be changed as well. All fixed now.

@MoleMan thanks for reporting the issue upstream.

@Healey85 said in Raspberry Pi Imager Update for Raspberry Pi 5?:

So at present time I own a Raspberry Pi 5. I see with the latest version of Raspberry Pi Imager version 1.8.5 you can install the Recalbox Operating System (under emulation and game OS), but not the RetroPie Operating System.

Yes, because RetroPie doesn't have an image released for the Pi 5. If it would have, it would be automatically picked by the RPI Imager. If you wish to use a Pi5, you can install manually RetroPie on top of a RaspiOS Lite installation, but support it's still beta and requires some Linux knowledge.

So if I want RetroPie on my Raspberry pi 5, am I better off seeking out a Raspberry Pi 4 separate from the 5 I already have?

It depends on what you kind of retro games you want to play - a Pi4 or even a Pi3 may be enough.