How did you get this: "CStateOverride boolean True"? Also note the lack of: "CSTinfo Number 0xsomething".
Do have C-State settings in your BIOS?
Can you please attach your dsdt.dsl and a dump from IORegistryExplorer?
Not sure about the Boolean message, wanted to look into that.
At this point I don't have a stable system. I had another lock-up whilst Carbon Copying to a backup partition - I was unable to reboot but have fixed that now.
I have 4 theories as to why my system is unstable:
1) My graphics card has incorrect device id (PCIO instead of GFX????)
2) My Cstates don't have a memory allocation (see my post #258)
3) I have incorrectly added my LPC device in my dsdt (PX40 is my LPC device-see attched LSPCI text)
4) My PState values have been incorectly calculated.
Further to number 4 my PState values were calculated from CPUi and P-State calculator.
The formula that CPUi uses to calculate voltage appears to be:
700 + VID x 16 (multiply before addition). This site Link
states a different calculation 800 + VID x 12.5 (for Core2 CPU's) but the results are very similar with either calculation.
In P-State calculator you enter a Core Voltage value under CPU Characteristics. If you reduce (or increase) this core voltage the result will be an increase or decrease the power required for the P-State, see example below (second value):
0x00000B0F, // 2831 Mhz in hex
0x00017318, // Power required for this PState
0x00004826 // FID=8.5, VID=38
So I believe that its hard to get these values wrong if using PState calculator (unless the accuracy of the Calculator itself is in question). So while its possible to have varying Core Voltage settings in P-State calculator (under CPU characteristics) this setting has an affect on the P-Sate value it generates, i.e. if you decrease the Core Voltage this will increase the power requirement for the P-State and vice versa.
What is in question though, as I don't know the answer (i intend to try it out) is the BIOS settings.
If I have set say 1.3v as my core voltage under CPU characteristics in P-State Calculator should my VCore voltage in BIOS be set to the same (and not set to Auto?) Could the interaction between BIOS under Auto settings and P-State settings in my dsdt under OSX result in the high voltages and be a reason for my instability? Or is it something in my setup?
All I am is a humble architect and not a programmer or coder. I have only been using OSX for about a year and my main working machine is currently an imac. when my hack is stable I intend to port everything across to my "G5".
In honesty I was ready to drop the C-State P-State additions as it was causing me too much grief (and I don't want to be a pain -- the ---- to anyone.
But hey, I built my hack into a G5 case, spent numerous hours getting to this point and enjoyed the ride but I think I've come as far as I can with my present knowledge.
I've attached appropriate files if anyone cares to check them for me. It would be appreciated.
Could my instability be caused by being on 10.5.8???
Should I use fakesmc instead of decrypt?
I get a free replacement @9550. Word!
WTF! Are they telling me that OS X includes technology to disable our CPUs?
Congrats on pulling that off! Awesome prcessor especially for overclocking.
I didn't know that disabling algorithms existed for processors!