You should change the Audio Device in EmulationStation's settings to one of the entries listed by aplay. If you the option doesn't show up in the menu, then edit es_settings directly and fill in the AudioDevice there.

front:CARD=Audio, DEV=0
USB Audio, USB Audio
Front Speakers

surround21:CARD=Audio, DEV=0
USB Audio, USB Audio
2.1 Surround output to Front and Subwoofer speakers

surround40:CARD=Audio, DEV=0
USB Audio, USB Audio
4.0 Surround output to Front and Rear speakers

@mitu It doesn't let me verify it

@sleve_mcdichael hmm that looks promising. I'll try to do any good with that in the following days. I really appreciate the help!

It seems the original raspberry pi HDMI cable was the issue.

I purchased a new micro-hdmi cable and all screenmodes work fine.

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.

@mitu Is it so simple then? OK, thank you for your answer and for your time.

@mitu Thanks. After I built RetroArch with your commit, works well now.
스크린샷 2023-05-23 21-53-39.png

@mtm81 Thanks for the replies up to this point - I'm pleased to say that I've got it fixed (well kind of).

With my previous setup I've confirmed that the ALL of the default settings I was putting into the pi (alsamixer, retropi config, config.txt, autorun, even going so far in the config.txt to turn off the HDMI audio all together etc) to force it to use headphones - all were working but ONLY after a certain point in the boot sequence. Up to that point, because I had the HDMI plugged in (for video only) the system was detecting that HDMI connection and setting the ouput audio to be HDMI. Once one the files config files was THEN loaded, the Headphone output would then take over.
The issue was always that, my file which was being used to control the audio volume output of the device - was being loaded BEFORE those other files took over, meaning my file was effectively turning the volume up and down on an output I wasn't using.

I've therefore changed my output to HMDI for audio output as well, and changed my cabling from using the headphone jack on the PI, to the output jack on the HDMI controller.
This works absolutely fine and works first time.

So although this issue is solved, the underlying reason still remains - if you want to use the headphone output for audio - that only is 'forced' so far into the boot sequence.

@sleve_mcdichael Yes.

For example ./retropie_packages.sh image all buster would build rpi1, rpi2/3 and rpi4 images based on buster.

Should be fixed now.
We don't support Dolphin on RPI (the system is not powerful enough to run it) and also RasPi OS bullseye support is still in beta.

@sleve_mcdichael @mitu

I see, thank you guys for the quick response! I'll try it just as explained.

@mitu

flashed retropie image from official site, configured keyboard and wifi, installed reicast and put bios on dc/bios (home folder) and...worked!!

Update image doesn´t works a good choice.
Now i ll do it in my main SD card.

Thanks anyway!

@Folly yea for sure i am about to install mame and other systems i let you know how it goes.

@Gérard
I was able to get into the editor and I made the changes that were suggested, but unfortunately my Bluetooth controllers are still not working. They worked a few years ago when I originally bought my pi. I guess I’ll keep digging around on the Internet.

Do you have the SSH enable from the raspi-config > Interfacing Options menu?

If it is enable, then, try to restart the router and the pi, maybe this will help.

Hi. I tried installing lr-applewin and this is the error i got...

Log started at: Fri 5 Apr 08:12:40 PDT 2024

RetroPie-Setup version: 4.7.1 (5b137bf4)
System: rpi4 (armv7l) - Raspbian GNU/Linux 10 (buster) - Linux retropie 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux

= = = = = = = = = = = = = = = = = = = = =
Installing dependencies for 'lr-applewin' : Apple2e emulator: AppleWin (current) port for libretro
= = = = = = = = = = = = = = = = = = = = =

/home/pi/RetroPie-Setup/tmp/build/lr-applewin /home/pi

= = = = = = = = = = = = = = = = = = = = =
Getting sources for 'lr-applewin' : Apple2e emulator: AppleWin (current) port for libretro
= = = = = = = = = = = = = = = = = = = = =

Already on 'master'
Your branch is up to date with 'origin/master'.
Already up to date.
HEAD is now in branch 'master' at commit '129077f9870426d1b7b3a8239d8b5a50bee017b4'
git clone --recursive --depth 1 --branch master "" ""
fatal: repository '' does not exist
HEAD is now in branch 'master' at commit '5b137bf44727cfa71ad2845cf792ce2a73383c10'
sed: can't read /home/pi/RetroPie-Setup/tmp/build/lr-applewin/source/frontends/common2/gnuframe.cpp: No such file or directory
/home/pi
Error running 'git clone --recursive --depth 1 --branch master ' - returned 128

Log ended at: Fri 5 Apr 08:12:42 PDT 2024
Total running time: 0 hours, 0 mins, 2 secs

Help! :D

We don't support 3rd party images and yours looks like it was customized and changed from the default RetroPie image.
I see you have a number of services (like snapd or bt-device) which are not standard on RaspiOS and I see also an error related to CPU throttling - maybe the system boot is slow because the CPU's frequency is scaled down.
You can use systemd-analyze how long it takes each system service to start, it may help identify which one is responsible for the slowdown.