Hdmi signal loss on raspberry pi 4 with 4k tv

mrfreester

I’m using the following 4k tv:

qn75q7daafxza

When booting, I’ll see the splash screen and then everything loads, but the signal goes out after a few seconds.

It should be 120hz as far as I know, but not sure if it’s the fake 120 that’s actually 60.

I used to get no signal but overclocking seemed to help it at least start.

I’ve tried setting hdmi settings in the config.txt file. Hdmi_group to 1 and the mode to 16, 63, 67. It seems to work best if I just leave those commented out as I don’t get anything when setting those values.

I’m grateful for any tips or direction, even if it’s just some guidance on how to debug 🙂

mrfreester

Also, no sound is coming through, but I’m new enough to not know if that’s supposed to come through the micro hdmi or not

mrfreester

I think this needs to be tagged in architecture/raspberry pi 4 but I don’t think I have rights to change it

Atari

Might need to do this: https://wiki.batocera.org/display_issues#force_any_specific_supported_resolution_in_es_instead_of_the_default_maximum_one

mrfreester

Thanks for the reply. It looks like I was missing this line:
hdmiignore*edid=0xa5000080

Trying that with hdmi_group=1 and hdmi*_mode=97 seemed to work. I still have an issue where my tv says incompatible hdmi group when I exit the game, but restarting seems to work fine.

Also, fixed the audio by explicitly specifying hdmi for the audio output and profile as has been mentioned by others.

mrfreester

I take it back, after restarting it, it’s back to it’s old issues.

I’ll keep tweaking it, but it’s very finicky. If I can get something more solid working I may create a github repo for the config files specific for my tv or something. For now I’m not sure what’s wrong.

I’m going to try reverting everything back to the default config.txt and batocera-boot.conf values and entering things one by one to try recreate whatever got it working before.

Atari

If you’ve discovered a genuine issue, I suggest you make an issue report. But from the sounds of this it really just seems like it’s your TV with the issues here.

mrfreester

Issue seems to be fixed with some cable changes

I was using a micro male to female HDMI cable, and hooked that into an 8k HDMI cable. I also tried using that micro adapter with a few other HDMI cables with no luck.

I swapped my adapter to a 4k male micro HDMI to male HDMI cable and now it seems to function perfectly without changing any config files.

My best guess is there was some issue with my male to female adapter cable that caused the pi to be confused about what mode to choose.