Most likely another purchase of CCC!
Not knowing the product but my bet is that it's not providing a correct EDID.
So checking the EDID, exporting it to a .bin, having that loaded via kernel command line video mode should sort such issue.
I've made various postings here on the forum on how that can be achieved so will not repeat myself.
Connect the display to a source which let it show a correct output, extract the EDID reported by that machine and you have your starting point set.
Note: all your config.txt settings are only active as long FW is in control. As soon as KMS kicks in durimg the boot process they will get ignored.
What is the output of the command below (make sure your display is connected to HDMI next to USB-C)
Not knowing the product but my bet is that it's not providing a correct EDID.
So checking the EDID, exporting it to a .bin, having that loaded via kernel command line video mode should sort such issue.
I've made various postings here on the forum on how that can be achieved so will not repeat myself.
Connect the display to a source which let it show a correct output, extract the EDID reported by that machine and you have your starting point set.
Note: all your config.txt settings are only active as long FW is in control. As soon as KMS kicks in durimg the boot process they will get ignored.
What is the output of the command below (make sure your display is connected to HDMI next to USB-C)
Code:
edid-decode /sys/class/drm/card?-HDMI-A-1/edidStatistics: Posted by aBUGSworstnightmare — Thu Apr 25, 2024 5:38 am