@gupsterg
I don’t think there is a problem in posting about this AMD signature in this thread. After all, there is no point in offering a modded VBIOS if it can’t be used. Having said that, it would have been better for the concerned Polaris users to come here and express their desire for testing, instead of using you as a relay. You have already done the most important test, now it’s just porting that change to drivers. I am starting to think that I am cursed or something, for every time I see a group of users complaining about a limitation and I find a workaround for it, there is hardly anyone interested in testing my patches. The last time it happened with <a patched BUpdater>, although there isn’t a week passing by without someone asking for exactly this sort of solution.
Hopefully, this time it will be different, as I already saw <a volunteer on OCN>. Since I am the one offering a solution for their problem and not the other way around, it is advisable for the discussion to take place on this thread. The patched driver for the user <generaleramon> is attached. It must be tested like this:
- disable driver signature enforcement. There are guides all over the web, one example being <this one>. The permanent solution is required, for as long as the patched driver is used. Reboot and make sure the Test Mode message is present in lower right corner.
- reboot in safe mode and replace original atikmdag.sys with the patched one.
- boot in normal mode and flash any custom VBIOS.
- reboot and test driver loading.
- report the result.
There are several hashing functions in this driver, some of them being used for COPP content. I might not have found the responsible one in the first try. If this is the case, testers should be armed with patience, as this isn’t a walk in the park.
atikmdag.rar (6.29 MB)