dmarshman

I've tried with multiple versions of [Unraid &] QEMU, Clover, WEG and Lilu over the past couple of months, **EDIT** and just verified I was using Lilu 1.4.0 and WEG 1.3.5. I also use MacPro1,1 as the machine ID. I just updated to Lilu 1.4.1 and WEG 1.3.6, but end up with the same result [Metal/OpenCL not supported]. **/EDIT** Since the RX 580 works with no issues with my current setup, I was hoping someone else had a success story with Unraid and a Radeon VII in order to evaluate if it's worth the continued effort or a waste of time trying to get the Radeon VII working with Metal / OpenCL. If nothing else comes up, I'll try and put some time aside this weekend to see if I can make any progress... As an aside, both the RX 580 and Radeon VII work perfectly as eGPUs using an external Thunderbolt 3 enclosure [Sonnet] with MacOS Catalina [10.15.0->.2] on a real Mac [2018 Macmini]. [Vanilla MacOS - no kexts, or anything].

Wondering if anyone successfully has a Radeon VII working with Metal / OpenCL acceleration in Catalina 10.15.2, or anyone has any advice? I have no graphics acceleration, and it is not recognized for Metal / OpenCL by GeekBench 4 or 5. I can successfully pass through the Radeon VII, it's recognized by the MacOS VM, is listed correctly with 16GB RAM in "About this Mac", and shows up as GFX0 using IORegistryExplorer. [I can post screenshots later if it helps]. When I swap the Radeon VII with a Radeon RX 580 - same VM, with exactly the same MacOS install and Clover install/settings - then I get full metal acceleration, and it is recognized by GeekBench 4/5 as a compute capable GPU. For background, I'm using the latest version of SpaceInvaderOne's Macinabox docker to create the VM, and using the version of Clover, Lilu and WEG that is contains. System: UnRAID 6.8.1 | ASRock Taichi X570 | AMD Ryzen 9 3950X | 64 GB RAM | GFX#1: Nvidia RTX 2070 | GFX#2: XFX Radeon VII

Are you running the 6.8.0 RC for that?

If you are not already, try using the "Q35-3.1" machine, rather than the "i440fx-3.1" machine to which the "Windows 10" template defaults. That fixed it for me - [ASRock X570 Taichi, Ryzen 9 3950X and Radeon Vega VII] - in conjunction with the boot flag "video=efifb:off" outlined above.