Search results

It's the 0x73BF device ID from the regular 6900XT. We compared and found that this ID is available and supported in the driver, while the one from the XTXH version (which has a slightly different device ID) is not.

Which is why I provided the pre-built binary here. Also, the easy way of doing this is to just fork the WEG repo and manually trigger the CI job, which builds this for you without any setup being required. You get 2000 build minutes for free on any GitHub account, so this is quite handy.

Oh yeah, if anybody wants to give it a try, here's the pre-built WEG kext. I built it from "master" this morning and figured it'd save some people a few steps by providing it here.

Can confirm, this works like a charm! No further need for FakePCIID shenanigans.

Seems to me to just be a renaming issue anyway. I get the same "compute prototype" name in i.e. Photoshop's settings. It also says gpu-controller for me in System Info. As such I doubt it has anything to do with anything special in your setup, this is just the way a somewhat-unsupported card is...

Can confirm that this worked for me as well. It's a bit strange since I did the exact same thing some Betas prior. Maybe something changed internally in how this is handled which somehow made this possible recently. Alternatively maybe I just overlooked something obvious and that's why it didn't...

Potentially because getting a 6900XT is not that simple in a lot of cases. Also, price.

Would you mind explaining what this does? Or at least what it's supposed to do.

Alas, my first try at this did not yield a functioning result. This is most likely due to what @Pavo mentioned, since the new breed of GPU's do not appear to offer ATY,bin_image at all, even when genuine. This made it impossible to extract the working, flashed VBIOS from a running system...

Interesting! I'll try to give this a shot with my setup and if it works I'll post the results here.

It might not be needed, but at least in my testing I was unable to get ATIFlash to enumerate the GPU on Windows, while on Linux it did. The Windows versions are also lacking the "force" flag which is required to flash a VBIOS (in my case it's technically an older version, so we need to force it...

I'm not aware of OpenCore supporting any kind of VBIOS shenanigans. It would be rather concerning if it did, imho. Flashing/modifying a VBIOS should be a rather deliberate act in all cases. Anyway, to replicate my results you need: A live USB stick with Ubuntu on it (or any other Linux distro...

This is a VBIOS flash. Turns out that there is currently no way to flash self-modified VBIOS versions because we need a version of atiflash which ignores the RSA check. Both the official version and the one from IgorsLab still have this check in this particular configuration, which makes it...

Hahaha, never underestimate a dedicated mad man! It friggin' works!

Nah, I ain't giving up that easily :) On that note: Progress! On Linux, atiflash actually recognizes the XTXH card properly, device ID, VBIOS version and all, so I'm a bit more hopeful now. I'm gonna transfer my modified VBIOS over to the live image and I'll attempt a flash tonight.

I believe you may have confused what these arguments do here. According to the help text, invoking atiflash with -pa and -padevid governs which devices the VBIOS is written to. It does not, however, modify anything about the card itself, as these arguments are simply selectors so you can more...

No change, unfortunately. Casey and I already tried the FakePCIID route a bit earlier on as well, with the same result. The RM,device-id property does attach, but the actual device-id refuses to change. Since I was able to dump the VBIOS of my GPU now, I've modified the ID in there with a hex...

Removing the rom-revision unfortunately does not make a difference. I did try spoofing via DeviceProperties before and it didn't work back then, either, so this is not surprising, I suppose. It's strange, since I *can* modify other parts of the device's properties, such as APPL,slot-name and the...

I've tried this without the RX 580, which allowed me to boot into macOS but without acceleration. The ID remains 0x73AF and no kext is loaded, unfortunately.

Are you sure about the PCI path? The one in your file points towards my RX580, and when applied as-is leads to getting stuck somewhere along the boot process (which seems sensical to me). Changing the PCI path to my actual RX 6900 XT allows me to boot, but does not modify the ID. It remains at...