CPU: AMD FX-8350
GPU: Radeon R7 240 (R7240-2GD3-L)
Motherboard: AsRock 970 Pro3
OpenCore 1.0.2
Good afternoon!
The following situation occurred. Monterey, not without issues, but still, was installed. I had to tinker with fine-tuning the plist and removing some RAM sticks in order for the installation to complete successfully. However, I couldn’t get past the setup screen because there simply wasn’t enough video memory. Acceleration just didn’t work. I spent about a day struggling with this problem and eventually switched to Big Sur. With this system, things went more smoothly: I managed to reach the desktop and even the App Store was working. But I still couldn’t get acceleration to work.
After studying the topic and spending another day tinkering with Big Sur, I found out that the Oland family is not so easy to spoof. But there’s catastrophically little information about device-id spoofing, and those who managed to do it either no longer respond or don’t want to share any details.
So I’m asking for help here — maybe someone could help me understand and figure out how exactly to make acceleration work on the R7 240.
Yes, I perfectly understand that the simplest solution would be to buy another graphics card secondhand or something like that, but unfortunately, I just don’t have that option at the moment. Besides, for me it’s extremely irrational. The computer is already very old, even though it has a decent 8-core processor. Upgrading it, even for little money, would just be throwing money away.
From what I’ve already tried — SSDT-GPU-SPOOF, changing the device-id, adding no-gpu-spoof, different bootargs from the Dortania guide. The method from the guide didn’t help at all.
For some reason, the device-id doesn’t change at all, no matter whether I set it in config.plist or in the SSDT. It always remains the same — 6613.
It’s possible that I messed up the ACPI path, I don’t rule that out.
But judging by Hackintool, IORegistryExplorer, and gfxutil — they all show the same path, which is already written in the SSDT, yet the device-id doesn’t change. On one of the forums, something similar was mentioned. In that case, the person didn’t have access to GFX0, and somehow, by adding gfx-no-spoof in device properties, he managed to change the device-id, but ran into another error. It seemed to me that there wasn’t much to take away from that case. Besides, I tried a similar procedure, and it didn’t work.
GPU: Radeon R7 240 (R7240-2GD3-L)
Motherboard: AsRock 970 Pro3
OpenCore 1.0.2
Good afternoon!
The following situation occurred. Monterey, not without issues, but still, was installed. I had to tinker with fine-tuning the plist and removing some RAM sticks in order for the installation to complete successfully. However, I couldn’t get past the setup screen because there simply wasn’t enough video memory. Acceleration just didn’t work. I spent about a day struggling with this problem and eventually switched to Big Sur. With this system, things went more smoothly: I managed to reach the desktop and even the App Store was working. But I still couldn’t get acceleration to work.
After studying the topic and spending another day tinkering with Big Sur, I found out that the Oland family is not so easy to spoof. But there’s catastrophically little information about device-id spoofing, and those who managed to do it either no longer respond or don’t want to share any details.
So I’m asking for help here — maybe someone could help me understand and figure out how exactly to make acceleration work on the R7 240.
Yes, I perfectly understand that the simplest solution would be to buy another graphics card secondhand or something like that, but unfortunately, I just don’t have that option at the moment. Besides, for me it’s extremely irrational. The computer is already very old, even though it has a decent 8-core processor. Upgrading it, even for little money, would just be throwing money away.
From what I’ve already tried — SSDT-GPU-SPOOF, changing the device-id, adding no-gpu-spoof, different bootargs from the Dortania guide. The method from the guide didn’t help at all.
For some reason, the device-id doesn’t change at all, no matter whether I set it in config.plist or in the SSDT. It always remains the same — 6613.
It’s possible that I messed up the ACPI path, I don’t rule that out.
But judging by Hackintool, IORegistryExplorer, and gfxutil — they all show the same path, which is already written in the SSDT, yet the device-id doesn’t change. On one of the forums, something similar was mentioned. In that case, the person didn’t have access to GFX0, and somehow, by adding gfx-no-spoof in device properties, he managed to change the device-id, but ran into another error. It seemed to me that there wasn’t much to take away from that case. Besides, I tried a similar procedure, and it didn’t work.