Contribute
Register

SSDT for W3680?

Status
Not open for further replies.
Joined
Jun 8, 2012
Messages
23
Motherboard
ASUS Sabertooth X58
CPU
Intel Xeon W3680
Graphics
NVIDIA GeForce GTX TITAN X
Hello, can anyone suggest some edits (or even share their own SSDT.aml file) that functions well with a Xeon W3680? When I installed 10.7.4 I just installed the i7 SSDT and my Geekbench scores ended up being a little slower than they ought to be for this processor.

My current Geekbench scores are 11000-12000 and according to the geekbench website they should be more in the 14000 range. Any other potential suggestions of causes/fixes of this low bench score would be appreciated.

D

EDIT: I guess the SSDT is just for sandy bridge processors but for some reason before I installed in I was getting an extremely slow geekbench (like 6000) but after install it went back into a reasonable range. Any idea why this had this effect?
 
CurseTheGods said:
Hello, can anyone suggest some edits (or even share their own SSDT.aml file) that functions well with a Xeon W3680?

I was searching for a working SSDT for my W3680 also, but didn't find one anywhere. So I followed the guide posted here to create my own: viewtopic.php?f=295&t=61305

Since MSRDumper.kext doesn't work with non-SandyBridge processors, I installed the newest FakeSMC.kext, all the plugins for hardware monitoring, and the HWMonitor app that are included in the newest version of Multibeast. I then used the HWMonitor app to see which P-states my processor is reaching. It only reaches 3 P-states: 1596Mhz, 2128Mhz, and 3325Mhz, but that is better than reaching only two: 1596Mhz and 3325Mhz when using GeneratePStates=Yes. I took the time to add all the processors to the SSDT and not just have processor cores 2-12 report the same as processor core 1 as the guide suggests for ease. I also use an ASUS motherboard (Rampage III Formula), and the processor identities in the DSDT are P001-P016. Since a Mac Pro uses CPU0, CPU1, etc... in it's DSDT, I decided to use those identities in my SSDT, and then change the identities in my DSDT to match. So you need to change the processor values in your DSDT to match the values in my attached SSDT.

Here is my edited entry in the DSDT. You should just be able to replace your Scope (_PR) with this one, as I'm assuming they're exactly the same:

Scope (_PR)
{
Processor (CPU0, 0x01, 0x00000410, 0x06) {}
Processor (CPU1, 0x02, 0x00000410, 0x06) {}
Processor (CPU2, 0x03, 0x00000410, 0x06) {}
Processor (CPU3, 0x04, 0x00000410, 0x06) {}
Processor (CPU4, 0x05, 0x00000410, 0x06) {}
Processor (CPU5, 0x06, 0x00000410, 0x06) {}
Processor (CPU6, 0x07, 0x00000410, 0x06) {}
Processor (CPU7, 0x08, 0x00000410, 0x06) {}
Processor (CPU8, 0x09, 0x00000410, 0x06) {}
Processor (CPU9, 0x0A, 0x00000410, 0x06) {}
Processor (CPUA, 0x0B, 0x00000410, 0x06) {}
Processor (CPUB, 0x0C, 0x00000410, 0x06) {}
Processor (CPUC, 0x0D, 0x00000410, 0x06) {}
Processor (CPUD, 0x0E, 0x00000410, 0x06) {}
Processor (CPUE, 0x0F, 0x00000410, 0x06) {}
Processor (CPUF, 0x10, 0x00000410, 0x06) {}
}

This will make your DSDT more "Mac like", and will work with the SSDT I created. I set the SSDT to reach a maximum P-state of 3.6Ghz to account for the Turbo Boost this processor utilizes. I am also running the processor at stock speeds (no overclock) and I specifically created the SSDT for the processor running at stock speeds.

I also have GeneratePStates=No, GenerateCStates=Yes, and DropSSDT=Yes in org.chameleon.boot.plist.

By the way, I'm no expert with DSDT or SSDT editing, so if anyone notices anything wrong with what I've done, or has any advice to improve upon what I've done, please let me know!

Dil83

P.S. This SSDT should also work with the Core i7 980X since the Xeon w3680 is identical to it aside from supporting ECC memory.
 

Attachments

  • SSDT.aml
    6.7 KB · Views: 340
YES! THIS! You're a genius. Worked like a charm - I got an immediate jump in Geekbench score of about 4000. I was worried that no one was going to reply.

Nothing like getting great information right off the bat. I can't possibly thank you enough. Very very grateful for the help.

Do you have any plans to OC? I'm testing stable/cool now at 4.2ghz and scores around 18000-19000 after using this guide:

http://www.techreaction.net/2010/09/07/ ... -gulftown/

That's without having edited a custom SSDT with more steps, I'm stoked/surprised.

Dil83 said:
I was searching for a working SSDT for my W3680 also, but didn't find one anywhere. So I followed the guide posted here to create my own: viewtopic.php?f=295&t=61305

Since MSRDumper.kext doesn't work with non-SandyBridge processors, I installed the newest FakeSMC.kext, all the plugins for hardware monitoring, and the HWMonitor app that are included in the newest version of Multibeast. I then used the HWMonitor app to see which P-states my processor is reaching. It only reaches 3 P-states: 1596Mhz, 2128Mhz, and 3325Mhz, but that is better than reaching only two: 1596Mhz and 3325Mhz when using GeneratePStates=Yes. I took the time to add all the processors to the SSDT and not just have processor cores 2-12 report the same as processor core 1 as the guide suggests for ease. I also use an ASUS motherboard (Rampage III Formula), and the processor identities in the DSDT are P001-P016. Since a Mac Pro uses CPU0, CPU1, etc... in it's DSDT, I decided to use those identities in my SSDT, and then change the identities in my DSDT to match. So you need to change the processor values in your DSDT to match the values in my attached SSDT.

Here is my edited entry in the DSDT. You should just be able to replace your Scope (_PR) with this one, as I'm assuming they're exactly the same:

Scope (_PR)
{
Processor (CPU0, 0x01, 0x00000410, 0x06) {}
Processor (CPU1, 0x02, 0x00000410, 0x06) {}
Processor (CPU2, 0x03, 0x00000410, 0x06) {}
Processor (CPU3, 0x04, 0x00000410, 0x06) {}
Processor (CPU4, 0x05, 0x00000410, 0x06) {}
Processor (CPU5, 0x06, 0x00000410, 0x06) {}
Processor (CPU6, 0x07, 0x00000410, 0x06) {}
Processor (CPU7, 0x08, 0x00000410, 0x06) {}
Processor (CPU8, 0x09, 0x00000410, 0x06) {}
Processor (CPU9, 0x0A, 0x00000410, 0x06) {}
Processor (CPUA, 0x0B, 0x00000410, 0x06) {}
Processor (CPUB, 0x0C, 0x00000410, 0x06) {}
Processor (CPUC, 0x0D, 0x00000410, 0x06) {}
Processor (CPUD, 0x0E, 0x00000410, 0x06) {}
Processor (CPUE, 0x0F, 0x00000410, 0x06) {}
Processor (CPUF, 0x10, 0x00000410, 0x06) {}
}

This will make your DSDT more "Mac like", and will work with the SSDT I created. I set the SSDT to reach a maximum P-state of 3.6Ghz to account for the Turbo Boost this processor utilizes. I am also running the processor at stock speeds (no overclock) and I specifically created the SSDT for the processor running at stock speeds.

I also have GeneratePStates=No, GenerateCStates=Yes, and DropSSDT=Yes in org.chameleon.boot.plist.

By the way, I'm no expert with DSDT or SSDT editing, so if anyone notices anything wrong with what I've done, or has any advice to improve upon what I've done, please let me know!

Dil83

P.S. This SSDT should also work with the Core i7 980X since the Xeon w3680 is identical to it aside from supporting ECC memory.
 
CurseTheGods said:
YES! THIS! You're a genius. Worked like a charm - I got an immediate jump in Geekbench score of about 4000. I was worried that no one was going to reply.

Nothing like getting great information right off the bat. I can't possibly thank you enough. Very very grateful for the help.

Do you have any plans to OC? I'm testing stable/cool now at 4.2ghz and scores around 18000-19000 after using this guide:

http://www.techreaction.net/2010/09/07/ ... -gulftown/

That's without having edited a custom SSDT with more steps, I'm stoked/surprised.

I'm am currently testing my w3680 at 4.6Ghz with another SSDT I created, but so far I'm only showing the processor running at 3.64Ghz in Lion, and also only getting two P-states again.

I have an ASUS Rampage III Formula with 24gb DDR3 1600 ram, 256Gb Samsung 830 SSD, and my Geekbench scores are still nowhere near what you're getting even with the 4.6Ghz over clock. I'm only getting around 15000. At stock speeds I get around 12500 so I'm not sure what the problem is. I'll continue working on the SSDT to see if I can get it working better, and will post back back with the results.

Dil83
 
A couple suggestions - first (as per that guide I posted) try a ratio with a high BCLK (if you haven't already), my current one is BCLK 200 with the CPU ratio at 21.

But here's a really weird thing that caused a 2000 PT jump when I changed it - make sure your DRAM bus is set to 1.65. Mine was at 1.5 because I wasn't overclocking the RAM so I didn't think I needed to do that but just for the hell of it I switched to 1.65 and got an immediate jump in performance. Also don't hesitate to boost the QPI/DRAM a few steps, I was just experimenting with going from 4.2 to 4.4GHZ and when I benched the score was low (like 16000) so I went into the bios and raised the QPI/DRAM two steps and then in benched about 19400 the next time I started-up.

Still working on stability at 4.4, raising the CPU voltage, etc. but I'm getting there - I just don't know if the boost from 18800 to 19400 is worth the extra heat. I'd also like to try underclocking one of these days which supposedly will boost this processor well over 20000 without very high voltages.

Hope that helps.

EDIT: Also make sure Load Line Calibration is enabled.
 
CurseTheGods said:
A couple suggestions - first (as per that guide I posted) try a ratio with a high BCLK (if you haven't already), my current one is BCLK 200 with the CPU ratio at 21.

But here's a really weird thing that caused a 2000 PT jump when I changed it - make sure your DRAM bus is set to 1.65. Mine was at 1.5 because I wasn't overclocking the RAM so I didn't think I needed to do that but just for the hell of it I switched to 1.65 and got an immediate jump in performance. Also don't hesitate to boost the QPI/DRAM a few steps, I was just experimenting with going from 4.2 to 4.4GHZ and when I benched the score was low (like 16000) so I went into the bios and raised the QPI/DRAM two steps and then in benched about 19400 the next time I started-up.

Still working on stability at 4.4, raising the CPU voltage, etc. but I'm getting there - I just don't know if the boost from 18800 to 19400 is worth the extra heat. I'd also like to try underclocking one of these days which supposedly will boost this processor well over 20000 without very high voltages.

Hope that helps.

EDIT: Also make sure Load Line Calibration is enabled.

Thanks for the advice! I haven't read the guide you posted yet, but will take a look at it. I think I've created about 30 or 40 SSDT's in different combinations using values from my SSDT dumped in Windows, and combining those with a Mac Pro 5,1 SSDT that I extracted along with the original SSDT I created. None seem to work as well as the original I created, so I am now back to the original SSDT I created above. I have now added P-State values all the way up to 4.2Ghz, and I just have CPU1-CPUA returning the same values as CPU0 because in all of my testing I found no advantage in specifying the exact same P-States for each core individually....it was just a lot more work. In the SSDT guide posted above, it recommends not adding any P-States higher than 4.2Ghz because the maximum value that OS X can report is 4.2Ghz. I tested this new SSDT on my system at stock speeds, and it still gives me 3 P-States as it did before, so it can be used in place of the original I posted above. I haven't tested with an overclock yet, but the P-State values are existing in the SSDT to allow for overclocking up to 4.2Ghz. The new SSDT is attached.

Dil83
 

Attachments

  • Dil83 4.2Ghz W3680 SSDT.aml
    1.1 KB · Views: 211
@CurseTheGods: Is OS X reporting the proper value for your processor speed? I've just tested my system overclocked to 4.2Ghz in the BIOS, but it reports a maximum of 3.5Ghz in OS X. It still gives me 3 P-States with this new SSDT while it's overclocked, but my Geekbench score is only ~12500!

Thanks,

Dil83
 
Yes, it seems to report the accurate clock speed - though I noticed when I tried different settings in the BIOS a low BCLK setting would result in an incorrect reading in the OS.

Here are the BIOS settings I was using to get a solid/stable 4.2Ghz with an accurate reading in the OS:

CPU RATIO= 21

BLCK=200

CPU = 1.3187 Volts
QPI/DRAM = 1.225
IOH = 1.12
DRAM BUS=1.65
LLC=enabled

That's with my ram at 1600 and the UCLK at 3200.

Got me a Geek Bench of 18500.

It could also be a patch from the newest Multibeast that fixed the clock speed reporting for me - I can't remember for sure. Make sure your patched are up to date (though I assume they probably are). Hope something here helps.
 
CurseTheGods said:
Yes, it seems to report the accurate clock speed - though I noticed when I tried different settings in the BIOS a low BCLK setting would result in an incorrect reading in the OS.

Here are the BIOS settings I was using to get a solid/stable 4.2Ghz with an accurate reading in the OS:

CPU RATIO= 21

BLCK=200

CPU = 1.3187 Volts
QPI/DRAM = 1.225
IOH = 1.12
DRAM BUS=1.65
LLC=enabled

That's with my ram at 1600 and the UCLK at 3200.

Got me a Geek Bench of 18500.

It could also be a patch from the newest Multibeast that fixed the clock speed reporting for me - I can't remember for sure. Make sure your patched are up to date (though I assume they probably are). Hope something here helps.

Awesome, thanks for saving me the time trying to figure those settings out. I noticed that my processor wouldn't even run at the proper speed in OS X when I used a multiplier greater than x25. So, I did start following the guide for overclocking you posted, and ended up with a 4.0Ghz overclock with x25 multiplier (I don't remember the BCLK), and now OS X is showing the proper CPU speed. I'll give your settings a try and see what happens.

Thanks again,

Dil83
 
Status
Not open for further replies.
Back
Top