- Joined
- Jun 19, 2011
- Messages
- 2
- Motherboard
- motherboard OR system make and model # > See Rules!
- CPU
- i7-2600K
- Graphics
- HD 6870
- Mac
- Mobile Phone
mumstead said:Strange. With the overclock SSDT I am only reaching Pstates 16 17 18 19 20 42. I am using a 2600k @ 4200 with a Z68X-UD3H-B3 and MacPro3,1. Why am I not getting anything between 20 and 42?
Well, it's power management related for sure. I'm not too sure what is causing it though. I have no SSDT.aml, no nullcpupwn or sleepenabler kext. Only third party kexts are for Audio and FakeSMC. I'm just thinking (or typing) out loud but I can't think of anything that would make it KP.haggle said:H8TR- well unfortunately that experiment failed miserably.. I tried your dsdt. Installed with dsdtse. Compiled with no errors, and installed. It crashed immediately and won't even boot with rboot. I had to go into terminal from the lion installer and rename the old backup dsdt and yours to get to be able to booting back w/ rboot. Could it be a different setting in our bios settings or something? The only thing I think I've changed from default are sata to ahci mode (speedstep and turbo were already enabled). Here's a screen shot of verbose.. Whatcha think??
I didn't copy anything from the SSDT. I edited my DSDT as I saw fit using this guide. It's a guide for editing the SSDT but I guess would apply if your SSDT table is in your DSDT.vnephos said:@FishCow, @H8TR What exactly are you guys copying from the SSDT to your DSDT? Do you mind providing some more specifics? I'm stuck with just two P-States on my P8P67 Deluxe since I have a 2xxx series BIOS. Thanks!
vnephos said:@FishCow, @H8TR What exactly are you guys copying from the SSDT to your DSDT? Do you mind providing some more specifics? I'm stuck with just two P-States on my P8P67 Deluxe since I have a 2xxx series BIOS. Thanks!
Package (0x06)
{
0x0F3C,
Zero,
0x0A,
0x0A,
0x2700,
0x2700
},
Package (0x06)
{
0x0ED8,
Zero,
0x0A,
0x0A,
0x2600,
0x2600
},
Package (0x06)
{
0x0E74,
Zero,
0x0A,
0x0A,
0x2500,
0x2500
},
Package (0x06)
{
0x0E10,
Zero,
0x0A,
0x0A,
0x2400,
0x2400
},
Package (0x06)
{
0x0DAC,
Zero,
0x0A,
0x0A,
0x2300,
0x2300
},
Package (0x06)
{
0x0D48,
Zero,
0x0A,
0x0A,
0x2200,
0x2200
},
Package (0x06)
{
0x0CE4,
Zero,
0x0A,
0x0A,
0x2100,
0x2100
},
Package (0x06)
{
0x0C80,
Zero,
0x0A,
0x0A,
0x2000,
0x2000
},
Package (0x06)
{
0x0C1C,
Zero,
0x0A,
0x0A,
0x1F00,
0x1F00
},
Package (0x06)
{
0x0BB8,
Zero,
0x0A,
0x0A,
0x1E00,
0x1E00
},
Package (0x06)
{
0x0B54,
Zero,
0x0A,
0x0A,
0x1D00,
0x1D00
},
Package (0x06)
{
0x0AF0,
Zero,
0x0A,
0x0A,
0x1C00,
0x1C00
},
Package (0x06)
{
0x0A8C,
Zero,
0x0A,
0x0A,
0x1B00,
0x1B00
},
Package (0x06)
{
0x0A28,
Zero,
0x0A,
0x0A,
0x1A00,
0x1A00
},
Package (0x06)
{
0x09C4,
Zero,
0x0A,
0x0A,
0x1900,
0x1900
},
Package (0x06)
{
0x0960,
Zero,
0x0A,
0x0A,
0x1800,
0x1800
},
Package (0x06)
{
0x08FC,
Zero,
0x0A,
0x0A,
0x1700,
0x1700
},
Package (0x06)
{
0x0898,
Zero,
0x0A,
0x0A,
0x1600,
0x1600
},
Package (0x06)
{
0x0834,
Zero,
0x0A,
0x0A,
0x1500,
0x1500
},
Package (0x06)
{
0x07D0,
Zero,
0x0A,
0x0A,
0x1400,
0x1400
},
Package (0x06)
{
0x076C,
Zero,
0x0A,
0x0A,
0x1300,
0x1300
},
Package (0x06)
{
0x0708,
Zero,
0x0A,
0x0A,
0x1200,
0x1200
},
Package (0x06)
{
0x06A4,
Zero,
0x0A,
0x0A,
0x1100,
0x1100
},
Package (0x06)
{
0x0640,
Zero,
0x0A,
0x0A,
0x1000,
0x1000
}
Name (APSS, Package (0x10) to -----> Name (APSS, Package (0x18)
samisnake said:thanks for the tips h8tr, fishcow and xxmacmanxx
fishcow, does your system sleep alright with that added to scope_pr?
H8TR said:Well, it's power management related for sure. I'm not too sure what is causing it though. I have no SSDT.aml, no nullcpupwn or sleepenabler kext. Only third party kexts are for Audio and FakeSMC. I'm just thinking (or typing) out loud but I can't think of anything that would make it KP.