Search results

I'm happy that I could help! No that string just tells chimera to boot with the nvda drivers. Full speed, in some programs a notch better, in others a noth worse performance, but nothing really mentionable. Greetings from Germuch muelleimer98

<string> nvda_drv=1</string>

I didn't disable nvidia drivers, I had them activated, updated to 10.9.3, after the reboot nvda manager said that there was a driver update -> I updated the nvda driver and everything worked. I couldn't be more happy with the 660 in my hackintosh :thumbup: greetings from Gerplenty muelleimer98

yes!

Why are there so few people who can read and use this ability? Changing the agpm.plist does not change anything, the clock bug is only related to the badly implemented opencl - the power management does not have to do anything with that.

Here, 10.9.2 didn't change anything. gtx 660 Gigabyte overclocked I even tried editing agpm, which does not have anything to do with opencl and preview.app which causes the 1.03ghz Greetings muelleimer98

developer program, 99usd per year

I also thought that SpeedStep would not work but then I tried that tool and looked at the power consumption i put my computer into. It showed that there were more than two states and the Intel tool proved me right.

Do not trust hwmonitor about the CPU states. You should use the Intel Power Gadged, it is much better and tells you the real power consumption (which differs a lot from the hwmonitor one) and the real clock. My hwmonitor also shows it clocks between 792 and 3.5, but the Intel app shows it is...

Exactly what I thought.

I do not even know what exactly the agpm would do if it worked because my GPU is clocking like a charm as long as I don't open preview.app. I doubt that making the AGPM would change anything about this. As I understood it, the whole problem is caused by the framework. Greetings and happy...

Does editing the agpm change the clock being stuck? @jamdox Do you have a DSDT.aml file?

No, I did not do anything with DSDT, SSDT or something like that. there was no need to because I have a Gigabyte board.

Here it is not loaded. It never was loaded, I tried Mac Pro 5.1 and many iMacs, now I am on iMac 14.2. Jamdox, what did you exactly edit in your agpm?

No, the AGPM.kext can't be edited because of the signature. If it is edited, it will not be loaded because of the missing signature. -> useless EDIT: The throttling always works as long as you don't open preview.app.

Is somebody here who can tell me the right efi string for a 4600? I did nor find anything about this on the internet... Greetings muelleimer98

Well, the 660 stays at 324 always now if I use IGPEnabler=Yes and plug it into the motherboard. BUT the 660 won't be used for games, benchmarks... Greetings muelleimer98

At first thanks for your answer, but how do I get the code for my card? And what difference does it make to put the cable to the mainboard (I have it in my 660 because I had artifacts when having it plugged to the iGPU)? Greetings muelleimer98

Here it is starting and idling with 324, but when I click on the HWSensors menu bar or if I open something with Preview, it clocks @1,03 and stays there. I don't quite often look at pics with Preview and I have the clock in the menu bar, so it does not bother me that much :D Greetings muelleimer98

Opening the attached pics makes my GPU clock up again...