I needed to extend the HDMI cable to the Pi SBC. The supplied original cable did not suit my desk and Monitor setup. A new 2m cable was purchased and installed, but upon boot I get an “Out of Range” warning.
The packaging said it was a 4k HDMI cable. Is this a problem? Do I need to get something else?
https://www.rasppishop.de/Raspberry-Pi-Micro-HDMI-zu-HDMI-Kabel-schwarz-2m
and https://www.welches-hdmi-kabel.de/hdmi-kabel-4k-ultra-hd-unterstuetzung/
Translate with Firefox-app: https://addons.mozilla.org/de/firefox/addon/traduzir-paginas-web/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search
No. The issue is with the hdmi cable whether it is too long or an inferior cable. You did not specify what you were using for a monitor or if it was the same monitor used with the short cable and the long one but you might.
There is a config called config_hdmi_boost=? that is put in config.txt but it seems that it is ignored on the pi4 at this time.
Hmmm. It does not look good. I am using the Raspberry Pi 4B and yes it is the same monitor. I wanted to switch the short (supplied) cable out and fit a longer version. Darn!
Update: A new HDMI cable has been puchased at the usual excessive cost, and installed on the Pi. The Monitor returned similar “Out of Range” warnings, but showed signs of life. The screen would flash before going blank. A lot of testing and Googling similar posts took place. The most recent attempt at solving this took 16 reboots. The end result is Manjaro booting to the login screen at the correct resolution. Yay!
The settings applied to config.txt that worked here are as follows.
hdmi_ignore_edid=0xa5000080
hdmi_drive=2
hdmi_group=2
hdmi_mode=82 - for my resolution 1920x1080
I had a similar sounding problem after installing the recent new Raspberry Pi OS release:
I have a Raspberry Pi branded micro-HDMI to HDMI cable and that worked fine, but I wanted to use a micro-HDMI to HDMI adaptor + an (older and longer) HDMI cable.
With my preferred cable the monitor showed a blank screen.
I found that adding either of these to /boot/config.txt allowed the monitor to work again: core_freq=600
or hdmi_enable_4kp60=1
I’m about to try out the current Manjaro, maybe it will be helpful here too
I have seen that work around also. Something must have changed with their firmware either with the kernel or RPi’s depending on if you are using kms or fkms. I have noticed some changes here lately. I have a VIZIO tv and have always had to manually specify the display resolution or get a blank screen with the pi4’s. With the other pi devices my tv works just fine.