@windg Thank you for answer. You are right, i took a other rom version and this one runs as it should. o/

@mitu Omg, shame on me. All the time i used the wrong patch for my GPi Case. Instead of GPi Case 2 Patch i used GPi Case 2W Patch.

I installed the correct patch and retropie boot as it should and works immediately. Thank you for the help anyway...

And sorry for double post^^

@windg
It does make no difference. Display patch is installed too. But the problem is no longer so important to me. But thank you very much =)

@HeineBorel Yes, the naming of the overlay is unfortunate. Note that your link is for the PIZero2W patch, for the CM4 is a separate repository, but it has the same issue (similar overlay name with an existing one, distributed by the raspberrypi-kernel package).

There are 2 workarounds for this

either rename the overlays/dpi24.dtbo file to something else and update the config.txt with the new name when updating RetroPie, skip the kernel and system packages and update only RetroPie's packages.

Okay Thanks to mitu because I got to digging into the speaker-test function and because I only had the one snd_usb_audio
I found out that in the lcd config that comes with the GPi Case 2 patch they have the following in the config

dtparam=audio=off

so changing that to on enabled snd_bcm2835 at index 0 then I just followed the Alternate USB Audio Method from RetroPie Docs and changed the snd_usb_audio from index 1 to 0 and rebooted and now I have sound.

I do not know if this is 100% correct or a buggy workaround as I am all new to Linux. But thanks a bunch for the help :)

@mitu Heya! As an update, I got it working! Worked with a friend of mine who is a Linux expert and he walked me through it step by step, which did include the steps that you had pointed out. Thanks so much for your help!

Ok, thank you for letting me know. May be difficult to acquire another cm4, but I will check rpilocater daily from now on for a wireless version.

One point to note. On my GPi it looks like I could probably have hard-coded the value to unbind/bind the built in controller. But I felt it was taking a risk it wouldn't work right. So, instead, I use a temp file to pass the value between scripts.

@seatbeesate
I stand corrected, I did a fresh install again/installed safe shutdown script rebooted and seems to be working.

Going to try and reproduce to make sure maybe it was just the config.txt that got screwed up or something.

I get a lot of errors trying to run this script, syntax errors and unexpected tokens. We're just copying what you posted into a .sh file?

@EctoOne Yeah, I've seen that thread too. It's saying that the dock is using a unique way of wiring up the HDMI port, and that other docks besides the one it came with don't seem to work because they don't support the oddball standard RetroFlag chose. The port does work as a regular USB-C port though.

I have also resolved the issue with using a bluetooth controller for ScummVM. The write up is in the other post. In case you also need it:
https://retropie.org.uk/forum/topic/33334/scummvm-controller-help-needed