@aerosheik I'm with the same issue using the RP4 and I just can see the boot secuence until the RetroPie logo in my CRT TV appears and then I lose signal cos probably Emulation Station has another resolution and is not the same as when the system boots.

Di you fixed or is impossible use RP4 with Retropie in a CRT TV using HDMI to a components transcoder? With a RPZero I can do that wihtout problems just changing the hdmi_mode and group like this:

hdmi_mode=1
hdmi_group=6

But I still can't use my CRT TV under Retropie with a 480i output and idk what can I do right now.

But nuts is pretty much where my head is at on this, yeah.

i use my Pi-Models 1-3 with CRTs (1x Samsung / 1x Bang&Olufsen)
Of course i wanted to connect the Pi4 also with my CRTs, but i only tried it once and burried that idea.
At least concerning the composite out.
Maybe i had bad luck and my Pi4/the AV-socket is broken, but the picture was H-O-R-R-I-B-L-E!!!

I am still searching for a verfied method to connect with better quality (Gert666, Pi2Scart etc.), but did not find anything that runs out of the box without any issues or performance loss :[

@deltagemini Strange but good it's resolved!

How do I know when it's finished updating, since I can't see anything? I have SSH setup, but no way of viewing the local output that I know of.

Check the latest log file under $HOME/RetroPie-Setup/logs, every install/update has a log file.

How do I prevent my monitor doing this again?

What kind of monitor do you have ? Does this happened before or just this once ?

FYI/UPDATE : For future browsers who may purchase and use this, or a similar, screen on their Pi.

https://www.amazon.com/dp/B07S82CN57 - Longruner Raspberry Pi Touch Screen

It turns out the driver for the LCD set the GPU RAM to 64MB upon installation. I tried it on 2 other 3B+ units I had running RetroPie because it was bugging me, and it did the same on both of them.

Just to confirm, I set it back to 128, reinstalled the driver, and it went back to 64 each time.

So if you use this screen, or maybe one similar to it, check your GPU RAM allocation after you install the drivers, it may have changed. Especially if you move the Pi back to a higher resolution display.

Edit: To be more specific, running "sudo ./LCD-hdmi" will set it to 64 every time. In my case, and probably others, if you move back to a "standard" HDMI display and do not run this, you will not have audio at all, no matter what you set in the Raspberry Pi/RetroPie. So if you use this or any similar LCD, and you notice you lost audio when moving to something else, don't forget to run this. Then check your GPU RAM allocation.

:)

@Thorr69 said in connect to tv and monitor:

Totally not what he asked about and why are you answering this really old thread?

Spam, really.

@bonch said in RGBPI over hdmi to vga converter:

OS: RGB_Pi_OS_V2_Pi3_FINAL_2_0_S

We don't support 3rd party images here - have you tried asking the author(s) of RGBPI OS for support ?

Do you have the 7″ touch display ? You probably had to configure the Pi to use the DSI output my modifying the bootloader configuration (the config.txt file on the boot) partition. To switch back to HDMI, you'll need to remove or comment the lines that enable and configure the LCD.
There might be a way to enable the LCD display only of HDMI is not detected through the use of conditional filters in config.txt, but you'll have to experiment and see if that's possible. If the LCD pannel cannot be detected at boot by the bootloader, then conditionally enabling/disabling it might not work.

You can try with a different hdmi_group/hdmi_mode until you find one that works (240p modes maybe ?).

@mitu yes, unfortunately

@scrumpydaniel

try power up the speaker via usb within the pi4 or by some audio converter from hdmi to 3,5 jack audio and have the audio setting of pi4 to hdmi and not 3.5 jack.

Nvm i figured it out

@john_carter No, it's is when I enable the VMS video driver and then the audio fails to work under HDMI. I haven't seen any other reports of this.

It's a common issue, since the HDMI audio is handled by the KMS driver automatically. It's been widely reported - in fact when the KMS driver for Pi4 was announced, it was one of the changes included (see this forum post). Here in the foruns - see this topic.