Added in 1 minute 11 seconds:
And what about without deinit?my machine not liking the INJECT ATI with deinit
when booted same way single monitor.. GPU fan full up, power bar on the card pulsates and I am using 200W at the wall instead of 120~
so clearly with macpro5,1 SMBIOS .. injecting is messing with GPU power management AND my luxmark scores are LOWER.. which makes no sense
I get the fan spinning up also only with InjectATI, but I take that as a good sign - because that was a known issue with the Vega 64 card, and possibly still is, at least with my Gigabyte OC which I have heard has its own fan controller.
Though in my case it is just the fan spinning up - not also an increase in power usage, at least not according to the stats put into IOKit, as read by HWMonitorSMC2. It's common for me to see 2600RPM fan, with 0% utilisation and ~20W power usage.
Ironically, the way to get the fan to stop spinning at full speed - at least for a time - is to put some load on the GPU, ie start playing a video. This is again a common experience from what I've read of other Vega 64 users, both Hack and real Mac Pro users. Though it was meant to be resolved in 10.14.5. So I am assuming the reason it is not resolved for me is my specific choice of Vega 64, as I found at least one site that mentioned the Gigabyte OC Vega 64s were an exception to the general fixes for fan spin, due to their proprietary fan controller.
Without InjectATI I get 25% lower GeekBench 4 scores, and one time I actually had the system freeze when I tried to run the Heaven UniEngine benchmark, which didn't happen with InjectATI
All I am setting is InjectATI - I don't set any of the other options in the same area. Which I believe means (though I may be wrong), that all InjectATI is doing is injecting the GPU name that Clover detects, which is "AMD Radeon RX Vega 64", versus the "Radeon RX Vega 64" that WEG puts in. Other settings, eg FBName, are all blank in my config.
If I'm correct about that, then that would mean that some part of the Apple drivers is looking for a particular GPU name and being affected by it? You'd think it would be based off the Vendor ID / Card ID. So maybe there's more to it than that.
I've never properly tried RadeonDeInit, so I don't really know what that does. I only tested it briefly, days ago, when I was seeing if there was any way to get rid of the need to sleep&wake. I had the impression it was an old param intended for much older cards/older versions of macOS/Clover, but who knows