Jump to content

DSDT for Asus P8P67-M PRO


Time2Retire
 Share

834 posts in this topic

Recommended Posts

If you set

DEBUG_CPU = 1
DEBUG_CPU_TURBO_RATIO = 1

RevoBoot will output the actual Turbo Ratios set (or not set for that matter) in the BIOS.

That's the debug-output:

CPU: Max Turbo with 1 core: 3700MHz
CPU: Max Turbo with 2 core: 3600MHz
CPU: Max Turbo with 3 core: 3500MHz
CPU: Max Turbo with 4 core: 3400MHz

Sure enough in BIOS I set multiplier 41 42 43 44 ;)

So also with last revision of RevoBoot my issue don't want to go away...

Link to comment
Share on other sites

Sure enough in BIOS I set multiplier 41 42 43 44 ;)

So also with last revision of RevoBoot my issue don't want to go away...

Enter the numbers again, after every number press enter (not enter on the numpad). Click the first number with the mouse. In the information area above the maximum frequency should update. Enter, click, scroll until the yellow number above changes.

 

This seems to be a BIOS-bug.

 

And to clarify, the latest RevoBoot update does not include any new fixes regarding SpeedStep/Turbo, it just speeds up the boot process until AICPUPM gets loaded. Until now, RevoBoot would start with just x16, now it runs at the maximum Turbo Mode you specify.

Link to comment
Share on other sites

Enter the numbers again, after every number press enter (not enter on the numpad). Click the first number with the mouse. In the information area above the maximum frequency should update. Enter, click, scroll until the yellow number above changes.

I made this a lot fo times but nothing is changed ;)

This seems to be a BIOS-bug.

I'll re-made another test under Windows to see which is the max multiplier used by system later.

Someone can post my results @HardForum?

And to clarify, the latest RevoBoot update does not include any new fixes regarding SpeedStep/Turbo, it just speeds up the boot process until AICPUPM gets loaded. Until now, RevoBoot would start with just x16, now it runs at the maximum Turbo Mode you specify.

Ok, thanks for explanation :P

 

EDIT

Just re-made a test under Windows with multiplier 41 42 43 44 set in BIOS.

During system-stressing by Prime95 the max multiplier used by system was 37x.

So... Is a BIOS bug?

Link to comment
Share on other sites

So... Is a BIOS bug?

Do you know what I meant by information area? The text information above the Turbo Ratio settings.

Will that value for the CPU frequency change if you set it to 37 for example?

What will the value show if you set the Turbo Ratio back to Default (1234)?

 

I believe you can make screenshots of the BIOS with F12 and a connected Fat-formatted usb-stick.

Link to comment
Share on other sites

Well, my friend ;)

 

Let's just say it was good I demanded some screenshots, because you set the Turbo Rates in the wrong order!

 

1-core needs to be set to 44

2-core to 43 and so forth

Link to comment
Share on other sites

;)

AppleIntelCPUPowerManagement: Turbo Ratios 89AB

MSRDumper PStatesReached: 16 20 21 22 23 41 42 43 44

LOL

 

I'm wondering why I have these with the same CPU:

MSRDumper PStatesReached: 16 22 26 30 33 41 42 43 44

 

Are you using the original stepper program?

Link to comment
Share on other sites

What do you mean?

Please open the iMac12_2.plist in SMC_PlatformPlugin and post the content of

 

IOPlatformThermalProfile -> CtrlLoopArray -> Item 0 -> StepDataDict

 

(not the long data itself, just the name, I have SP13 there)

Link to comment
Share on other sites

Yep.

            Name (APSN, 0x04)
           Name (APSS, Package (0x13)
           {
               Package (0x06) { /* 4400 MHz */ 0, 0, 10, 10, /* 44 */ 0x2C00, 0x2C00 },
               Package (0x06) { /* 4300 MHz */ 0, 0, 10, 10, /* 43 */ 0x2B00, 0x2B00 },
               Package (0x06) { /* 4200 MHz */ 0, 0, 10, 10, /* 42 */ 0x2A00, 0x2A00 },
               Package (0x06) { /* 4100 MHz */ 0, 0, 10, 10, /* 41 */ 0x2900, 0x2900 },              
               Package (0x06) { /* 3300 MHz */ 0, 0, 10, 10, /* 33 */ 0x2100, 0x2100 },
               Package (0x06) { /* 3200 MHz */ 0, 0, 10, 10, /* 32 */ 0x2000, 0x2000 }, 
               Package (0x06) { /* 3100 MHz */ 0, 0, 10, 10, /* 31 */ 0x1F00, 0x1F00 }, 
               Package (0x06) { /* 3000 MHz */ 0, 0, 10, 10, /* 30 */ 0x1E00, 0x1E00 }, 
               Package (0x06) { /* 2900 MHz */ 0, 0, 10, 10, /* 29 */ 0x1D00, 0x1D00 }, 
               Package (0x06) { /* 2800 MHz */ 0, 0, 10, 10, /* 28 */ 0x1C00, 0x1C00 }, 
               Package (0x06) { /* 2700 MHz */ 0, 0, 10, 10, /* 27 */ 0x1B00, 0x1B00 }, 
               Package (0x06) { /* 2600 MHz */ 0, 0, 10, 10, /* 26 */ 0x1A00, 0x1A00 }, 
               Package (0x06) { /* 2500 MHz */ 0, 0, 10, 10, /* 25 */ 0x1900, 0x1900 }, 
               Package (0x06) { /* 2400 MHz */ 0, 0, 10, 10, /* 24 */ 0x1800, 0x1800 }, 
               Package (0x06) { /* 2300 MHz */ 0, 0, 10, 10, /* 23 */ 0x1700, 0x1700 },
               Package (0x06) { /* 2200 MHz */ 0, 0, 10, 10, /* 22 */ 0x1600, 0x1600 }, 
               Package (0x06) { /* 2100 MHz */ 0, 0, 10, 10, /* 21 */ 0x1500, 0x1500 }, 
               Package (0x06) { /* 2000 MHz */ 0, 0, 10, 10, /* 20 */ 0x1400, 0x1400 }, 
               Package (0x06) { /* 1600 MHz */ 0, 0, 10, 10, /* 16 */ 0x1000, 0x1000 }
           })

Link to comment
Share on other sites

This topic has gone a bit off-topic lately, please keep it on P8P67-M PRO.

 

I will make a new thread purely about the P8P67, I suggest you do the same for other versions/boards. It will get confusing and convoluted otherwise.

 

I'll open a new thread about P8Z68-VPro as soon as I 'll get Revoboot installed, as I know that it works, now.

 

In the meantime, I'm happy to annonce I get it working fine, output taken running Cinebench (4 cores):

Jun  7 06:33:25 P8Z68-VPRO kernel[0]: MSRDumper CoreMulti(35) 
Jun  7 06:33:25 P8Z68-VPRO kernel[0]: MSRDumper PStatesReached: 16 35 36 37 
Jun  7 06:33:26 P8Z68-VPRO kernel[0]: MSRDumper CoreMulti(35) 
Jun  7 06:33:26 P8Z68-VPRO kernel[0]: MSRDumper PStatesReached: 16 35 36 37 
Jun  7 06:33:26 P8Z68-VPRO kernel[0]: MSRDumper CoreMulti(35) 
Jun  7 06:33:26 P8Z68-VPRO kernel[0]: MSRDumper PStatesReached: 16 35 36 37 
Jun  7 06:33:27 P8Z68-VPRO kernel[0]: MSRDumper CoreMulti(35) 
Jun  7 06:33:27 P8Z68-VPRO kernel[0]: MSRDumper PStatesReached: 16 35 36 37 
Jun  7 06:33:27 P8Z68-VPRO kernel[0]: MSRDumper CoreMulti(35) 
Jun  7 06:33:27 P8Z68-VPRO kernel[0]: MSRDumper PStatesReached: 16 35 36 37

 

My fault: I forgot to copy imac_12,2.plist... :D

 

Many thanks to get me running.

Link to comment
Share on other sites

flAked, i've modded your slimmed down DSDT for support on P8P67 Pro 1606

JMicron eSATA and Intel LAN support is enabled and working

 

Excellent. As suggested, could you please make a new topic for work on the P8P67 PRO? I think there are a lot of people following who are waiting for a slimmed down DSDT and SpeedStep support on this popular board (myself included ;-) )!

Link to comment
Share on other sites

Hi all! sorry for my English, I very need ioreg from imac 12,2.

there is one more option to get speedstep to work on this board, there is someone else?

 

Of Course! Read here http://www.insanelymac.com/forum/index.php?showtopic=258611

 

I'll open a new thread about P8Z68-VPro as soon as I 'll get Revoboot installed, as I know that it works, now.

 

In the meantime, I'm happy to annonce I get it working fine, output taken running Cinebench (4 cores):

Jun  7 06:33:25 P8Z68-VPRO kernel[0]: MSRDumper CoreMulti(35) 
Jun  7 06:33:25 P8Z68-VPRO kernel[0]: MSRDumper PStatesReached: 16 35 36 37 
Jun  7 06:33:26 P8Z68-VPRO kernel[0]: MSRDumper CoreMulti(35) 
Jun  7 06:33:26 P8Z68-VPRO kernel[0]: MSRDumper PStatesReached: 16 35 36 37 
Jun  7 06:33:26 P8Z68-VPRO kernel[0]: MSRDumper CoreMulti(35) 
Jun  7 06:33:26 P8Z68-VPRO kernel[0]: MSRDumper PStatesReached: 16 35 36 37 
Jun  7 06:33:27 P8Z68-VPRO kernel[0]: MSRDumper CoreMulti(35) 
Jun  7 06:33:27 P8Z68-VPRO kernel[0]: MSRDumper PStatesReached: 16 35 36 37 
Jun  7 06:33:27 P8Z68-VPRO kernel[0]: MSRDumper CoreMulti(35) 
Jun  7 06:33:27 P8Z68-VPRO kernel[0]: MSRDumper PStatesReached: 16 35 36 37

 

My fault: I forgot to copy imac_12,2.plist... :)

 

Many thanks to get me running.

 

Great job! But you can get other 5 P-States work.

Link to comment
Share on other sites

Sorry, you have probably got me wrong, I need ioreg from the original Imac 12,2

This link you followed is not the solution, the first update will get the Kernel Panic, it is possible to alter the processor section of the native, which is in our DSDT, but this requires ioreg from the original Imac 12,2

Link to comment
Share on other sites

In the meantime, I'm happy to annonce I get it working fine, output taken running Cinebench (4 cores):

This seems to me like only the turbo states are working.

 

 

This link you followed is not the solution, the first update will get the Kernel Panic, it is possible to alter the processor section of the native, which is in our DSDT, but this requires ioreg from the original Imac 12,2

This patch is for a specific version yes. I'll update the patcher if a new version comes out.

I'm also working on a BIOS mod.

 

The KP has nothing to do with missing DSDT components, it is a BIOS lock.

Link to comment
Share on other sites

Hi made some tests regarding Turbo Ratios & sleep/wake.

Results are interesting.

With Turbo Ratios 89AB (41x 42x 43x 44x) my sleep doesn't work.

Like we can see on /usr/bin/pmset -g log:

 * Domain: sleep
 - Message: Sleep: Platform Failure - AC
 - Time: 07/06/11 15.32.17 GMT+02.00 
 - Signature: Platform Failure
 - UUID: BF32DFCA-48C5-4734-A9B8-502CE0778B69
 - Result: Failure

If I put my PC in Stop all appears to be ok; indeed monitor and fans shutdown correctly and led start to flash on and off. But if I try to wake up the system I get a black monitor also if fans re-start. I have to shutdown PC by holding power button because if I try to hold reset button I get 3 beeps (on manual board I can read anything regarding 3 beeps).

Interesting is that if I use Turbo Ratios 1234 (34x 35x 36x 37x) my sleep/wake works correctly like we can see on /usr/bin/pmset -g log:

 * Domain: sleep
- Message: Sleep: Success - AC - Software Sleep
- Time: 07/06/11 15.21.37 GMT+02.00 
- Signature: Success
- UUID: CFE4A12F-A9F7-4E95-B593-63F0654B17F8
- Result: Success
- Sleep count : 1

* Domain: wake
- Message: Wake: Success - AC - EHC1
- Time: 07/06/11 15.21.37 GMT+02.00 
- Signature: Success
- UUID: CFE4A12F-A9F7-4E95-B593-63F0654B17F8
- Result: Success

* Domain: hibernatestats
- Message: Hibernate Statistics
- Time: 07/06/11 15.21.37 GMT+02.00 
- Signature: hibernatemode=0
- UUID: CFE4A12F-A9F7-4E95-B593-63F0654B17F8

* Domain: sleep
- Message: Sleep: Success - AC - Software Sleep
- Time: 07/06/11 15.22.29 GMT+02.00 
- Signature: Success
- UUID: 97A69EFA-E36B-41B1-8E5B-6EFA9D94F66B
- Result: Success
- Sleep count : 2

* Domain: wake
- Message: Wake: Success - AC - EHC1
- Time: 07/06/11 15.22.29 GMT+02.00 
- Signature: Success
- UUID: 97A69EFA-E36B-41B1-8E5B-6EFA9D94F66B
- Result: Success

* Domain: hibernatestats
- Message: Hibernate Statistics
- Time: 07/06/11 15.22.29 GMT+02.00 
- Signature: hibernatemode=0
- UUID: 97A69EFA-E36B-41B1-8E5B-6EFA9D94F66B

 

UUID: 97A69EFA-E36B-41B1-8E5B-6EFA9D94F66B

UUID: CFE4A12F-A9F7-4E95-B593-63F0654B17F8

UUID: BF32DFCA-48C5-4734-A9B8-502CE0778B69

 

Why UUID change any time thta I put system in Stop? Is it normal?

Link to comment
Share on other sites

 Share

×
×
  • Create New...