@mitu
After figuring out I shouldn't be using the 64bit version for this, I got the screen working with sound. Now it's just the usual gambling of installing stuff that's not just roms and emulators in retropie. :v

Thanks!

@mitu Great, thanks!

@martinrdgz before you dump your setup you may check these:

Run wpa_supplicant manually with -d : https://raspberrypi.stackexchange.com/a/103442

Maybe line ending in the wpa_supplicant.conf may be the cause (Mac -> Linux):
https://stackoverflow.com/a/18344020

And I noticed a space in the `psk="<space>...", is put there deliberately?

@mitu

Hey sorry for the long delay, yes it is 64bit

I didn’t have time to look at it for a long time and got back to it, a reboot later and reinstall of retropie yealed me no errors and seem like it installed fine

So no idea why it threw a fit the first time, anyway I love it! Very happy I came across RetroPi!

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

Thank you all for the feedback, I'll probably go with a Pi 4 and retropie.

You can also use an USB sound card, there's no need for a HAT/GPIO solution. Any card that advertises Linux support should work.
For a HAT solution, I think any of the DACs sold by the RPI folks directly might fit the bill - see https://www.raspberrypi.com/products/.

Excelente trabajo, me gustaría saber si lograste adaptar el tema a una pantalla pequeña 4:3, si me lo puede compartir, realmente esta genial tu trabajo

@Renetrox i will be posting updates and other similar topics here: https://t.me/+sL2deBcdYNUxZTEx

@cloc140 said in Enabling wifi in Retropie at installation on Picade Pi 4b:

it’s written on screen to press button A but I tried to press all buttons without sucess.

I assume you're taking about the controller configuration screen ? AFAIK the Picade needs a driver to be installed in order configure the input.

If you're trying to enable WiFi so that you can download and install the driver, then the easiest way would be to create a wpa_supplicant.conf configuration file on the sdcard - see https://retropie.org.uk/docs/Wifi/#connecting-to-wifi-without-a-keyboard. You can similarly enable SSH to be able to connect to the Pi and run commands - see the getting started documentation from the previous link I posted.

@mitu said in Raspberry pi screen not working:

hdmi_cvt=800 480 60 6 0 0 0

Wow! Now it's working great! Thanks.

I had tried all other options except

hdmi_cvt=800 480 60 6 0 0

@mitu

To circumvent the problem, I've just installed RetroPie via RPI's imager for now, as that will have to do.

Thank you for taking the time to look into the issue. :)

PS. Mega Man rules.

The functionality provided by the fbtft module has moved to an overlay in 5.10, you can try to use the overlay to configure your display.
The 4.7.1 is using the 5.4.72 Linux kernel version, if you need an earlier version you may try the 4.6 version, though I'm not sure which Linux kernel version is used in 4.6. Older versions are unsupported, but from 4.6/4.7 you can upgrade to the current RetroPie version and skip any Linux kernel updates.

My advice would be to try and use the overlay method to configure your screen. RetroPie uses a RaspiOS Lite (buster) as a base, so any instructions that apply to RaspiOS (Raspbian) Lite should work on RetroPie also.

@reaktor24 said in PSX Games not working on RetroPie:

Thanks for the tips. I updated RetroPie but wasn't able to update RetroArch through EmulationStation. Looks like this isn't an option.

You need to start the RetroPie-Setup script from the RetroPie menu and update it, then update retroarch like you did before.

Anyway I managed to get it working. I had renamed one of my games (Castlevania) to remove the [PSX] from the start of the file name and this seemingly broke all the games. Once I renamed it back again they all started working. Very strange. Anyway thanks for your help.

It's not strange, the .cue files contain the filename of the .bin cd image, if you renamed the .bin file(s) without updating the contents of the .cue file, then the emulator will not be able to find the correct cd image file(s).