[Help] My TV doesn't detect my RetroPie anymore? (HDMI)

[Malixx]

Hello,

Here is the story, my Raspberry was working fine on my TV (HDMI) then I went away from home for a week with my Raspberry and I plugged in another TV (HDMI) with another HDMI cable but with the same power supply and it still worked fine.

Except that the sound wasn't playing so I just went in the RetroPie menu to select "HDMI audio" and everything was ok (the resolution wasn't good but it was an old HDMI TV).

But then I returned to my home and now it seems that my TV for some reason doesn't detect the Raspberry anymore?

I tried with 3 different HDMI cables but... still the same result!

I also tried to make these changes in the config.txt but nothing worked.

hdmi_force_hotplug=1
hdmi_drive=2

Or

hdmi_group=1
hdmi_mode= 4

And even this

hdmi_safe=1

Thank you for helping me.

---

Pi Model: Raspberry Pi 3 Model B
Power Supply used: 5V 2.5A
RetroPie Version Used: 4.4
Built From: Image on RetroPie website
USB Devices connected: None
Controller used: 8Bitdo NES30 Pro Gamepad

[mitu]

If you run tvservice -s from the PI, does it output something ? On a connected TV, should say something like

pi@retropie:~ $  tvservice -s
state 0x12000a [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive

[Malixx]

@mitu Thank you for your answer, this what I get:

pi@retropie:~ $ tvservice -s
state 0x12000a [HDMI DMT (4) RGB full 4:3], 640x480 @ 60.00Hz, progressive

Maybe this is a clue, the 4:3 must block the signal or something, how do I change this?

[SuperFromND]

@malixx Actually, I think it's that DMT part that's causing signal issues. Usually, CEA is used for televisions, while DMT is used for computer monitors.

[Malixx]

@supercatfooz Ok I trust you! But what should I do, if there is something I can do about it?

[SuperFromND]

@malixx Try running something like tvservice -p to start the TV service with preferred settings, then starting emulationstation.

[Malixx]

@supercatfooz Hmm it says -bash: syntax error at or near the symbol " ( " when I try to put these configs state 0x12000a [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive what am I doing wrong :(

[mitu]

@malixx Usually tvservice -p does not take any arguments, I think just tries to get the optimal setting from the monitor and set it. Where do you get this error and what command are you trying ? See Video modes docs on the parameters availble.
Alternatively, you could run sudo raspi-config and configure the video output from the RPI configuration utility.

[Malixx]

@mitu Ok I thought I had to put the everything after tvservice -p(btw it does nothing) so I went in sudo raspi-config and tried to change some settings, but still nothing...

Edit: I changed the resolution to 1080p in the sudo raspi-config but when I type tvservice -s these settings are still showing
state 0x12000a [HDMI DMT (4) RGB full 4:3], 640x480 @ 60.00Hz, progressive

[Malixx]

I also tried with a fresh install and still nothing!

[mitu]

@malixx What is the resolution on your TV set ? Is it really '640x480' ? Can you try changing it and see if it's picked up by RP ?

[Malixx]

@mitu Thank you for your answers btw, my TV is 4K and sadly no it doesn't change the resolution even if I try to...

[mark1986]

have you read through this https://www.raspberrypi.org/documentation/configuration/config-txt/video.md

Which values are valid for my monitor?
Your HDMI monitor may only support a limited set of formats. To find out which formats are supported, use the following method:

Set the output format to VGA 60Hz (hdmi_group=1 and hdmi_mode=1) and boot up your Raspberry Pi
Enter the following command to give a list of CEA-supported modes: /opt/vc/bin/tvservice -m CEA
Enter the following command to give a list of DMT-supported modes: /opt/vc/bin/tvservice -m DMT
Enter the following command to show your current state: /opt/vc/bin/tvservice -s
Enter the following commands to dump more detailed information from your monitor: /opt/vc/bin/tvservice -d edid.dat; /opt/vc/bin/edidparser edid.dat

[Malixx]

Hello @mark1986, thanks for trying to help I got this:

pi@retropie:~ $ /opt/vc/bin/tvservice -m CEA
Group CEA has 2 modes:
           mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive
           mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive

pi@retropie:~ $ /opt/vc/bin/tvservice -m DMT
Group DMT has 1 modes:
  (prefer) mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive

pi@retropie:~ $ /opt/vc/bin/tvservice -s
state 0x12000a [HDMI DMT (4) RGB full 4:3], 640x480 @ 60.00Hz, progressive

pi@retropie:~ $ /opt/vc/bin/tvservice -d edid.dat;/opt/vc/bin/edidparser edid.dat
Nothing written!
Enabling fuzzy format match...
Failed to open edid.dat
edid_parser exited with code -1

I will try to understand and correct the problem with your link, but if you have any solution, I'm all ears!

[Malixx]

UP! I tried almost everything... Please I need help.

[BobHarris]

@malixx If it takes you this much time, isn't it easier to start with a fresh image and copy some of your old configs and roms to your new image?
Also always good practise to backup your image often so you won't have to deal with stuff like this.

I'm not tech savvy so all I can think of is this:
Have you tried both turning the tv on before turning the Pi on and turning the tv on a minute after turning the Pi on? This makes a difference in how the Pi boots up. If your tv is already on then it uses that resolution. If your tv is not on (and hdmi video is forced) then it will use a low resolution.

And have you used your hdmi port with another device to rule out your tv causing the issue?

[Malixx]

@bobharris Thanks for the reply, I have another SD Card with a fresh install and it does the same thing.

I also tried both turning the tv on and off!

I tried with different ports and also different cables... same result :(

[BobHarris]

@malixx said in [Help] My TV doesn't detect my RetroPie anymore? (HDMI):

@bobharris Thanks for the reply, I have another SD Card with a fresh install and it does the same thing.

Might be a hardware problem with your Pi then..

[Malixx]

@bobharris So yeah you were right, I tried with another Pi and it works... :(

[Malixx]

Ok just to be clear, the malfunction was because of my NESPI Case from Retroflag (I have the older version) maybe it drains too much power! Sorry I should have told you about the case, I thought it won't be the problem because it worked on another TV...