You are right; I think you need to downgrade your Clover. Go to that page :
Clover Bootloader Page and you'll see that the developers propose not all the versions but only some, the most important and the most reliable.
For instance, I know that
Clover_v2.3k_r3577 is for El Capitan and by experience if I install the next version Clover_v2.3k_r3911 on this site, I need to upgrade to Sierra or High Sierra.
On my son's hackintosh which is under Clover 3577 and El Capitan, Lily and Whatevergreen work well. You should give them a try.
jcds83
thanks man... wish that there were a more concerted effort by the actual dev's of clover and the other patches to keep a more proactive WIKI with meaningful documentation on which version cap at what hardware / macos versions
I am pretty much convinced I will be caping this board at Mojave.. if not for hardware limitations.. because with the loss of 32bit applications .. I will be up the creek on several packages that I either don't want to buy again or are just not available any longer but I have years worth of ongoing records in ..and will have to maintain
as far as you know .. what is the MINIMUM stable clover for 10.14.6?
right now I think that the only issues I am having are all VEGA related.. and it seems that the windows crowd and real macpro5,1 guys are all having issues with VEGA too.. all seem to stem from the same failure to either signal sync properly, maintain that signal sync, or fails to init and or init and get proper EDID values...
compound the VEGA's poor firmware with apples less than stellar and certainly 'closed' drivers that are really no longer open enough to fully support reference layouts with current patches and hacks that I have found and I think that is where the limitations will stay
there are no real Mac products, save the Mac Pro 5,1, that are advertised to work with the VEGA card with DP and HDMI connections.. the imacpro does all external monitors over TB3 and every other mac only works the reference VEGA cards as eGPU over TB ...
I think perhaps we need some kind of hack for spoofing internal dGPU cards as installed in eGPU enclosures provided there are no operating limitation on a eGPU that would keep it from operating as the primary and only display drivers for systems that don't have intel CPU graphics
another possible issue is that my HDMI monitor is a really old gateway FDH2400 from like more than 10 years ago.. and my 4k@60 tv is a el cheapo SEIKI . and when I had that monitor running 4k60 with the same DP1.2 active adapter on the gtx660 on el capitan .. I had to use switchresx to custom profile 4k60.. and at 60 it would not do audio over HDMI .. it would be garbled.. had to run it at 50, 30, 24 hz if I wanted to use audio.. it also capped out at a pixel clock of 533 anything higher and it would not work..
currently I think that WEG/apple drivers are driving the pixel clock of 4k60 at 599 .. and that might be overdriving my display.. not sure... seems to display fine at 60, sometimes at 30. but 4k@24 is all distorted
the HDMI blanking might be that the drivers are only trying to push a higher version of HDMI than the monitor is capable of ? not sure.. but it seems like there are now dozens upon dozens of people posting black screen issues like this using the HDMI port..
hope the WEG folks look into it..