@dragonmel,
WEG has always injected a GenericFramebuffer with AMD GPU's .... its not an issue, you do not loose any performance or features .. it's just the way WEG does things.
I did know that the MacPro5,1 SMBIOS uses PSXx@x as a ACPI device name/path for a dGPU ...
However I've never personally used the MacPro5,1 SMBIOS so cant really advise you on if having it renamed as GFX0 is an issue or not .. I guess if the Vega 56 is working in MacOS with a ACPI name of GFX0 then it's not an issue.
The WEG devs are pretty hot on AMD support, after all WEG was originally only for AMD GPU's so they must have their reasons for doing it ...
Cheers
Jay
thanks Jay..
right now.. things look improved.. but I am using a big hammer.. lots of hot patches and renames are by default turned on during the clover install
I had a restart causing a power off sudo cmos reset looking event but it didn't clear cmos settings but did bring up a cmos failures to boot message. I have reuse FFFF, fixRTC, apple RTC, gen P/C states etc turned on
seems like changing the shutdown/reset values to the PCI rail might have fixed that up. and if I recall I was doing that with my previous install
don't know if I should leave generate P/C states on since the w3680 is a known proc, and the x58 chipset are both used in real Mac Pro 5,1
I let it sleep over night and I got a clean wakeup 7 hours later. I am seeing less stop sign events at boot...
its odd that I can now use NVRAM with just the clover driver and no RC. scripts... I am convinced this is somehow related to how the apple update might have written or partially written a firmware update to my board.
so many things change... so little FORMAL documentation and a lot of questionable data in threads
so I am indeed just letting clover and LILU / plugins do their thing. there were a couple built in renames turned on by default most of which clover is telling me didn't execute. I had to modify SAT to SATA as my board has SAT1 SAT2 I think and the second sat I don't believe is supported and I have it disabled in bios..
funny that I don't think that clover really abides by some of these settings
for example I have ECC memory (non buffered) which should permit me to enable ECC in bios but it always shows as disabled in System Information. If I enable ECC in bios clover boot log tells me that turbo boost and other features of the cpu are disabled so I leave ECC disabled in bios..
however I am not using the required TyMce disable patch which is required for mac pro5,1 SMBIOS definitions to avert a kernel panic without ECC ram.. but I never get that panic or TyMCE messages in the logs.. so even though BIOS has ECC disabled and system profiler says its disabled.. it must be enabled
the standard install of clover has almost all DSDT hot patches active so I am sure that there are some that I don't need.
so you don't think having the generic frambuffer is going to cause performance or reboot/wake issues?
right now I have a 42" Seiki 4k monitor attached to a DP with a Club3d DP1.2 to HDMI adapter and a gateway .. old gateway 1920x1200 FDH monitor attached to HDMI. it did wake from sleep this am so a couple more wakes like that and perhaps we are out of the woods.
I wonder if I should buy a DP 1.4 adapter instead?
on my previous setup with the gtx660 I had to generate custom profiles for the Seiki 4k in El Cap to get it working.. and 4k60 had to stay around 530 for total bandwidth otherwise it wouldn't work.. sound over HDMI would only work at frame rates below 50. 4k60 would garble the audio
in Mojave I still have switchresx installed, but I deleted the custom resolutions and the standard 4k60 profile with a bandwidth of 599ish seems to work fine and HDMI audio is clean even at 60.
I have not tested switching the display framerate to 30 and 24 since re-installing clove from scratch but it was not working before
switching framerate would horribly corrupt the video picture, sometimes switching inputs back and forth or power cycle the Seiki would fix it ... seems like the Windows crowd also has issues with the Vega .. similar type issues of black screen and not fetching the EDID properly at display switching, sleep/wake etc..
I think that perhaps that might be some of our issues on OS X as well..