Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
What are you using for your open core settings? I have a 27" mid 2010 iMac - seems to be the same as you have, but have had no luck getting OpenCore running. I'm guessing it's a matter of setting the right plist file?

edit: WX4310 graphics card
Here's my Opencore EFI folder for an iMac 2010 21,5'' with a WX4130. There will be no changes for a 27''.
 

Attachments

  • EFI AMD WX4130 iMac 2010 27'' Opencore 0.6.0.zip
    3.8 MB · Views: 230
Here's my Opencore EFI folder for an iMac 2010 21,5'' with a WX4130. There will be no changes for a 27''.

Progress, thank you!
I now get:
- load screen;
- my iMac screen actually lights up and I don't need to connect an external monitor (which would then light up the iMac - weird occurrence);

I am however now getting the iMac to completely shut down as soon as I launch Unigine for the performance test. I'm wondering if it's from the boost? maybe I can tone it down to the regular Polaris?

edit: I think I was thinking of that MAX option, which isn't what you have. So something else is going on. Where should I look for errors?
 
  • Like
Reactions: NOTNlCE
I have a working solution! So I ended up with a mix of the original config.AMD.plist and Pascal's. For now, the main thing I added was the black screen fix. I'm attaching it for the time being. I think there's a lot of work to be done, but for now I have:

- Boot loader;
- iMac screen turning on;
- Unigine went from 300 score to 800~ish. Still below reported values, but looking a lot better!
- No complete crash when slightly using the GPU (would crash on the first 2 seconds of Unigine using Pascal's settings;

I'll come back with more details on my experience so far, I'm sure someone else will appreciate it, as I sure have appreciated the help and details of all the people here. Thank you!
 

Attachments

  • WX4310_27_mid2010.zip
    2.5 MB · Views: 270
  • Like
Reactions: iPlasm
I have a working solution! So I ended up with a mix of the original config.AMD.plist and Pascal's. For now, the main thing I added was the black screen fix. I'm attaching it for the time being. I think there's a lot of work to be done, but for now I have:

- Boot loader;
- iMac screen turning on;
- Unigine went from 300 score to 800~ish. Still below reported values, but looking a lot better!
- No complete crash when slightly using the GPU (would crash on the first 2 seconds of Unigine using Pascal's settings;

I'll come back with more details on my experience so far, I'm sure someone else will appreciate it, as I sure have appreciated the help and details of all the people here. Thank you!
Try to uncheck PolarisBoost in config.plist to see if it's related.
 
... I currently have a machine with a bad skin sensor (waiting for a replacement off eBay). It causes the CPU to throttle, resulting in a noticeable sluggishness. Geekbench is nearly 1/2 of what is normal. ...
The cable arrived, and resolved the issue. GeekBench5 and Valley benchmarks (results uploaded) now are as expected. This iMac was originally @dubyadubya 's, and after replacing the logic board, power supply and now the sensor cable, Scrappy-Doo is "feeling" much less like scrap. :)

1599330462803.png
 
  • Like
Reactions: Ausdauersportler
everything okay for all with other cards! Fine GREAT!

But who help for pps with K3000M! with right vbios. i got 3 card and stuck with wrong bios.
 
We are nearly neighbors; I was born in Ann Arbor, but live in KY now. It sounds like you just need your K610M flashed, right? I have a CH341A and clip, and have done several K2000M/K2100M/WX7100 cards with that method. If you don't find anyone closer, I can take care of it. I'd only need you to provide the card and a return shipping label. Shoot me a PM to proceed.
 
  • Like
Reactions: wa9im
I have a working solution! So I ended up with a mix of the original config.AMD.plist and Pascal's. For now, the main thing I added was the black screen fix. I'm attaching it for the time being. I think there's a lot of work to be done, but for now I have:

- Boot loader;
- iMac screen turning on;
- Unigine went from 300 score to 800~ish. Still below reported values, but looking a lot better!
- No complete crash when slightly using the GPU (would crash on the first 2 seconds of Unigine using Pascal's settings;

I'll come back with more details on my experience so far, I'm sure someone else will appreciate it, as I sure have appreciated the help and details of all the people here. Thank you!
It would be great if you could share your hardware configuration in your signature.
 
  • Like
Reactions: jinx.pt
Try to uncheck PolarisBoost in config.plist to see if it's related.

PolarisBoost is checked on both mine and your configuration - so that shouldn't be the issue.
You do have a - lot - of additional drivers. I wonder if it's one of those? For all I know, the crash may not be GPU related, but sound instead, or something else entirely. I only have OpenCanopy and OpenRuntime for the time being.

I've in the meanwhile updated my signature - thank you!

Edit: one other major difference is the OS version, of course. I'm not yet ready to upgrade the version: one step at a time :)
 
PolarisBoost is checked on both mine and your configuration - so that shouldn't be the issue.
You do have a - lot - of additional drivers. I wonder if it's one of those? For all I know, the crash may not be GPU related, but sound instead, or something else entirely. I only have OpenCanopy and OpenRuntime for the time being.

I've in the meanwhile updated my signature - thank you!

Edit: one other major difference is the OS version, of course. I'm not yet ready to upgrade the version: one step at a time :)
Mac OS version do not have to be important, because OpenCore has to be able to boot High Sierra, Mojave, Catalina, soon Big Sur, Windows etc ... Specific kexts for an OS have to be injected by the OS itself (in S/L/E), not by Opencore.
Others EFi drivers are present in drivers folder but are not loaded. I only use OpenCanopy and OpenRuntime too.
Kexts not used are present too in kext folder but not used.
 
Just download mac fan control and set a custom limit for the hdd sensor, this is the setup that I run:
View attachment 938899

Note that my settings are based in the safety data from WD.
The original HDD had a custom fw/sensors from apple that reported the info to the system so the new ssd/hdd doesn't have it, don't buy any new sensor-cable just use the mac fan control.
And suddenly - quiet - thank god! Thank you.
 
Mac OS version do not have to be important, because OpenCore has to be able to boot High Sierra, Mojave, Catalina, soon Big Sur, Windows etc ... Specific kexts for an OS have to be injected by the OS itself (in S/L/E), not by Opencore.
Others EFi drivers are present in drivers folder but are not loaded. I only use OpenCanopy and OpenRuntime too.
Kexts not used are present too in kext folder but not used.
Looking roughly at the plist files, the main differences I see are:

DeviceProperties:
- an extra device-id in there; don't really know what it does, but I'm guessing that wouldn't cause the computer to shut down;

Kernel:
- FakeSMCGPUSensors enabled on mine;
- Lilu and WhateverGreen have a minKernel set (shouldn't impact?);
- I've added your black screen fix to the block into my .plist (same). Then you have some disabled patches, so shouldn't impact either;

Misc:
- mine is mostly empty. But I'm guessing these ones are mostly to control boot options, etc? - I did like yours to be honest, so I'll likely have a look at these later on;
- my security options are all also empty;

NVRAM:
- minor differences here and there. Boot-args are the same; You have some boot configs on another uuid for uiscale, etc, I'm guessing those wouldn't have an impact; I don't think these ones are likely impacting;

UEFI, some minor differences:
- "SanitiseClearScreen" in Output;
- AppleAudio in ProtocolOverride;

I think I'll quickly test the FakeSMCGPUSensors...
 
Looking roughly at the plist files, the main differences I see are:

DeviceProperties:
- an extra device-id in there; don't really know what it does, but I'm guessing that wouldn't cause the computer to shut down;

Kernel:
- FakeSMCGPUSensors enabled on mine;
- Lilu and WhateverGreen have a minKernel set (shouldn't impact?);
- I've added your black screen fix to the block into my .plist (same). Then you have some disabled patches, so shouldn't impact either;

Misc:
- mine is mostly empty. But I'm guessing these ones are mostly to control boot options, etc? - I did like yours to be honest, so I'll likely have a look at these later on;
- my security options are all also empty;

NVRAM:
- minor differences here and there. Boot-args are the same; You have some boot configs on another uuid for uiscale, etc, I'm guessing those wouldn't have an impact; I don't think these ones are likely impacting;

UEFI, some minor differences:
- "SanitiseClearScreen" in Output;
- AppleAudio in ProtocolOverride;

I think I'll quickly test the FakeSMCGPUSensors...

The PolarisBoost version i sent you has PolarisBoostMax behavior for all AMD WXxxxx except WX7100. It means memory and GPU clocks are max out. I use it for my WX4130 and it do not go over 75 degrees doing Valley Benchmark.
Here's a Polarisboost version not forcing memory and gpu clocks to maximum.
 

Attachments

  • PolarisBoost_soft.kext.zip
    6 KB · Views: 272
The PolarisBoost version i sent you has PolarisBoostMax behavior for all AMD WXxxxx except WX7100. It means memory and GPU clocks are max out. I use it for my WX4130 and it do not go over 75 degrees doing Valley Benchmark.
Here's a Polarisboost version not forcing memory and gpu clocks to maximum.

I can now confidently state it's not a kext issue. It's some configuration. I just tried simply replacing my plist with yours and I get the shutdown. Kept the same files.
 
I can now confidently state it's not a kext issue. It's some configuration. I just tried simply replacing my plist with yours and I get the shutdown. Kept the same files.
Do you use iMacPro1,1 ID in your config.plist?
It could be a poor GPU heat dissipation. Which GPU temp do you get on load? What heatsink do you use, 3 pipes? Does GPU make a flat and plain contact with the heatsink?
 
Last edited:
Do you use iMacPro1,1 ID in your config.plist?
It could be a poor GPU heat dissipation. Which GPU temp do you get on load? What heatsink do you use, 3 pipes? Does GPU make a flat and plain contact with the heatsink?

Not sure what that is (iMac Pro1,1, ID)?

I have 2 pipes, but that shouldn't be an issue for the 4310.

Not sure what you mean with flat and plain contact? It looks similar to the one I had on previously, including the glue and those soft black protections the previous one had are also present.

HWMonitor shows 55degrees (Celcius) on start.

I do not get any shutdowns with my plist - none at all. The shutdown only happens with your plist and is literally after ~2 seconds of starting up the Unigine Valley banchmark - always exactly at the same spot - which is terribly weird and precise.

Edit: I do notice I have both the CPU and GPU proximity sensors set at 129 degrees. Doesn't look right.
 
Last edited:
Not sure what that is (iMac Pro1,1, ID)?

I have 2 pipes, but that shouldn't be an issue for the 4310.

Not sure what you mean with flat and plain contact? It looks similar to the one I had on previously, including the glue and those soft black protections the previous one had are also present.

HWMonitor shows 55degrees (Celcius) on start.

I do not get any shutdowns with my plist - none at all. The shutdown only happens with your plist and is literally after ~2 seconds of starting up the Unigine Valley banchmark - always exactly at the same spot - which is terribly weird and precise.

Edit: I do notice I have both the CPU and GPU proximity sensors set at 129 degrees. Doesn't look right.
129 degrees means: No data from sensor.
 
129 degrees means: No data from sensor.

What/where's this sensor exactly?
In the case of GPU, I have:
- GPU Die (50);
- GPU Heatsink (42);
- GPU Proximity (129);

In the case of CPU:
- 4x CPU Cores (~50);
- then I have another two CPU Cores listed (?????) (~50 as well)
- CPU Heatsink (47)
- CPU Proximity (129)

edit: I'm wondering if those proximity sensors simply do not exist? Every other temperature in there seems relatively ok? Other then the disk I suppose, which may not be quite right?
 

Attachments

  • Screen Shot 2020-09-06 at 15.13.48.png
    Screen Shot 2020-09-06 at 15.13.48.png
    132.6 KB · Views: 210
Last edited:
What/where's this sensor exactly?
In the case of GPU, I have:
- GPU Die (50);
- GPU Heatsink (42);
- GPU Proximity (129);

In the case of CPU:
- 4x CPU Cores (~50);
- then I have another two CPU Cores listed (?????) (~50 as well)
- CPU Heatsink (47)
- CPU Proximity (129)
You should rely on gpu heatsink and cpu heatsink temp values, when we change Apple graphic cards for unsupported ones internal values may be not available most of the time. For internal cpu values it should be available I believe.
 
For Nvidia Users booting with OpenCore(k1100M/k2100M/ETC)/ native booting K3100M/K4100M & 780M

I have Updated the ApplebacklightFixup.kext to include the proper Backlight stepping-levels for the 2009-2011 27" iMac. You can replace the one in your OpenCore loader with this or install it Natively to System/Library/Extensions. This actually makes my Previous guide irrelevant unless you really like the Native Kext feeling.

Lilu.kext will be needed for the kext to be listed as 'loaded' but it's still working for me without it.
Usual Verbiage below....
If installing to System/Library/Extensions. Catalina users need to Unlock their System Partition using Hackintool first. Then install with Kext Utility. Finally Open Terminal and enter "sudo reboot" as sometimes Catalina will hang on the Desktop.

For those out there using the impossible combination of 780M and 21.5" 2010 iMac, here is my fix for the backlight levels to work again using highvoltage12v fixup kext, this should be added to the info.plist of the fixup, in the ApplePanels dict section:
Code:
<key>F10T9cde</key>
<data>ABEABgC9ANIA5AEcAVQBjAHEAgACVQL/A6kEUwT9BacGUQb7</data>

I made the string using the instructions from this Stackoveflow post in combination with this highvoltage12v post, which would work with any model. Bare in mind that the panel models and brightness levels change even in the same model.

Thanks to all you people keeping up with this wonderful GPU hack.
 
  • Like
Reactions: m0bil
Hi guys,
i bought a Dell GTX770M, modified the cooler and flashed it with the bios of Nick (I thought so). The problem is, if i insert the graphics card, theres a blank screen but i can hear the chime. The motherboard status leds 1 and 2 are on, 3 and 4 are off. That means that the graphics card is not detected properly. I flashed with a CH341A. But I cant find the right chip there and it says chip main memory with the contents are in disagreement. I have a PM25LD020 (CE1320, =669XG) thats whats written on the bios chip, but in the programmer software I can't find a chip with PM25LD020. Can you help me fixing this? Thanks and with best regards. Its a Mid2011 27inch Imac with I7 2600 and 16GB RAM. The bios i tried to flash is attached.
 

Attachments

  • Unbenannt.PNG
    Unbenannt.PNG
    124.7 KB · Views: 223
  • Kepler Beta3.zip
    562.9 KB · Views: 206
What/where's this sensor exactly?
In the case of GPU, I have:
- GPU Die (50);
- GPU Heatsink (42);
- GPU Proximity (129);

In the case of CPU:
- 4x CPU Cores (~50);
- then I have another two CPU Cores listed (?????) (~50 as well)
- CPU Heatsink (47)
- CPU Proximity (129)

edit: I'm wondering if those proximity sensors simply do not exist? Every other temperature in there seems relatively ok? Other then the disk I suppose, which may not be quite right?
The most important temperature will be shown by the "GPU_Monitor_AMD" script, located in the same folder as HWMonitor. That temperature should be shown by HWMonitor as well, might be the one named "GPU Die" in your case. The GPU itself is specified for temperatures up to 90°C under full load.
In case your screenshot was taken when you haven't been doing any GPU intensive things for let's say 10 minutes, the difference between "GPU Die" and "GPU heatsink" seems too high (should be near to 0° difference then) - that would indicate a bad heatsink installation (this IS difficult to get right with the WX41x0s).
 
Hi guys,
i bought a Dell GTX770M, modified the cooler and flashed it with the bios of Nick (I thought so). The problem is, if i insert the graphics card, theres a blank screen but i can hear the chime. The motherboard status leds 1 and 2 are on, 3 and 4 are off. That means that the graphics card is not detected properly. I flashed with a CH341A. But I cant find the right chip there and it says chip main memory with the contents are in disagreement. I have a PM25LD020 (CE1320, =669XG) thats whats written on the bios chip, but in the programmer software I can't find a chip with PM25LD020. Can you help me fixing this? Thanks and with best regards. Its a Mid2011 27inch Imac with I7 2600 and 16GB RAM. The bios i tried to flash is attached.
use the usb method to flash provided by @xanderon :)

led 3 off means no communication with the graphic card
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.