Jump to content
82 posts in this topic

Recommended Posts

Just did few test on 10.6.8 and 10.7.1 (MSI Z68MA-ED55 + i7-2600K) AMI UEFI

 

Using Chameleon without DSDT - only FakeSMC and SMBIOS iMac12,2

 

I have on my MB CPU Phase LED (6 phase power mode) - will include how they behave

 

10.6.8:

 

1. nullCPU.... 16,34 - all leds on - geekbench ~12300

2. patched AICPUPM (w/o plist) - 16,34 - leds changing - geekbench ~6000

3. patched AICPUPM (w/o plist and c-state in UEFI disable) - 16,34 - all leds on

4. patched AICPUPM + imac12,2 plist (c-state in UEFI disable) - 16,20,24,30,34,35 - all leds on - can't get more then 35 - geekbench ~12700

5. patched AICPUPM + imac12,2 plist (c-state enable) - 16,20,24,30,34,35,36,37,38 - leds changing - geekbench ~12900

6. patched AICPUPM + imac12,2 plist (c-state enable + EIST disable) - 16,34 - leds changing - low geekbench score (~6000)

7. patched AICPUPM + imac12,2 plist (c-state enable + EIST enable + IPB disable) - 16,20,24,30,34 - leds changing - geekbench ~12300

 

10.7.1:

 

1. nullCPU.... 16,34 - all leds on - geekbench ~12200

2. patched AICPUPM (c-state in UEFI disable) - 16,30,32,34,35 - all leds on - geekbench ~11200

3. patched AICPUPM - 16,30,32,34,35,36,37,38 - leds changing - geekbench ~11700

4. patched AICPUPM (c-state enable + EIST disable) - 16,34 - leds changing - geekbech ~12300

5. patched AICPUPM (smbios mbp8,3) - 16,20,24,30,32,34,35,36,37 - geekbench ~11400

6. patched AICPUPM (c-state enable + EIST enable + IPB disable) - 16,20,30,32,34 - leds changing - geekbech ~10700

  • 2 weeks later...

Hi I tried out the Mac Mini 5,1 SMbios so I don't have to mess with the graphics kexts to use integrated graphics. Everything works well with the exception of P/C states. With MSRdumper, I only achieve two P/C states. (16,34). With Macbook Pro 8,1 SMBIOS I achieved 6 states(16,19,23,28,33,34). Anyone else have similar issues or is it something on my side. Thanks.

 

My processor is i5-2500k and the rest of the hardware is in my sig below.

 

Also is this an issue of MSRdumper not recognizing the P/C states for mac mini smbios or them not existing at all. Thanks.

uhmm, I just tested it on my i7 950 . getting constant log as following.

 

ep 20 05:23:27 Amits-Mac-Pro kernel[0]: MSRDumper CoreMulti(0) 
Sep 20 05:23:27 Amits-Mac-Pro kernel[0]: MSRDumper PStatesReached: 
Sep 20 05:23:28 Amits-Mac-Pro kernel[0]: MSRDumper CoreMulti(0) 
Sep 20 05:23:28 Amits-Mac-Pro kernel[0]: MSRDumper PStatesReached: 
Sep 20 05:23:28 Amits-Mac-Pro kernel[0]: MSRDumper CoreMulti(0) 
Sep 20 05:23:28 Amits-Mac-Pro kernel[0]: MSRDumper PStatesReached: 
Sep 20 05:23:29 Amits-Mac-Pro kernel[0]: MSRDumper CoreMulti(0) 
Sep 20 05:23:29 Amits-Mac-Pro kernel[0]: MSRDumper PStatesReached: 
Sep 20 05:23:29 Amits-Mac-Pro kernel[0]: MSRDumper CoreMulti(0) 
Sep 20 05:23:29 Amits-Mac-Pro kernel[0]: MSRDumper PStatesReached: 
Sep 20 05:23:30 Amits-Mac-Pro kernel[0]: MSRDumper CoreMulti(0) 
Sep 20 05:23:30 Amits-Mac-Pro kernel[0]: MSRDumper PStatesReached: 
Sep 20 05:23:30 Amits-Mac-Pro kernel[0]: MSRDumper CoreMulti(0) 
Sep 20 05:23:30 Amits-Mac-Pro kernel[0]: MSRDumper PStatesReached

 

does that mean speedstep is not working? here is the chameleon log

SSDT with CPU C-States generated successfully
P-States: min 0xc, max 0x17
SSDT with CPU P-States generated successfully
RSDT: Added 2 SSDT table(s)

 

I have my DSDT as well. Do I still need to install any drivers for this? I am clueless!

  • 2 weeks later...

I'm on a L502x i7 2630QM 2nd-MacBookPro8,3

 

MSRDumper PStatesReached: 8 11 12 13 14 16 17 18 19 20 
MSRDumper CoreMulti(18) 
MSRDumper PStatesReached: 8 11 12 13 14 16 17 18 19 20 
MSRDumper CoreMulti(20) 
MSRDumper PStatesReached: 8 11 12 13 14 16 17 18 19 20 
MSRDumper CoreMulti(18)

 

Left it for about 20minutes, multitasking like hell... do those lines represent Speed Stepping being functional?

 

Edit: Used a generic SSDT.aml found in the revoboot thread these are my results now

 

 

10/3/11 6:54:57.000 AM kernel: MSRDumper CoreMulti(24) 
10/3/11 6:54:57.000 AM kernel: MSRDumper PStatesReached: 8 11 16 22 24 25 26 27 28 
10/3/11 6:54:57.000 AM kernel: MSRDumper CoreMulti(24) 
10/3/11 6:54:57.000 AM kernel: MSRDumper PStatesReached: 8 11 16 22 24 25 26 27 28 
10/3/11 6:54:58.000 AM kernel: MSRDumper CoreMulti(25) 
10/3/11 6:54:58.000 AM kernel: MSRDumper PStatesReached: 8 11 16 22 24 25 26 27 28 
10/3/11 6:54:58.000 AM kernel: MSRDumper CoreMulti(24)

.....

10/3/11 7:18:34.000 AM kernel: MSRDumper PStatesReached: 8 11 12 16 21 22 24 25 26 27 28 
10/3/11 7:18:34.000 AM kernel: MSRDumper CoreMulti(29) 
10/3/11 7:18:34.000 AM kernel: MSRDumper PStatesReached: 8 11 12 16 21 22 24 25 26 27 28 29 
10/3/11 7:18:35.000 AM kernel: MSRDumper CoreMulti(29) 
10/3/11 7:18:35.000 AM kernel: MSRDumper PStatesReached: 8 11 12 16 21 22 24 25 26 27 28 29 
10/3/11 7:18:35.000 AM kernel: MSRDumper CoreMulti(26) 
10/3/11 7:18:35.000 AM kernel: MSRDumper PStatesReached: 8 11 12 16 21 22 24 25 26 27 28 29

  • 2 weeks later...

Curiosity got the better of me after having problems with a friends AMD system and P-states, so I decided to see how my system is running.

 

iMac12,2 SMBios.plist

Fully edited DSDT with no SS edits

 

Bansakus-iMac kernel[0]: MSRDumper PStatesReached: 16 20 35 36 37

 

Like what others have posted, I know I had a few more P-states in SL, including the missing "34". As well, shouldn't I have "38" as well? Perhaps my tests did not take advantage of the single CPU core?

 

Looks like everything is working (almost) great. :)

  • 1 month later...

Hi,

 

I just tested out the MSRDumper and not sure if these results are correct for my 2600K (Not Overclocked):

 

CoreMulti(16)

PStatesReached: 16 + 34.

 

 

I have not yet installed a SSDT. My system is an Asus Z68 Deluxe with patched bios to allow native AICPUPM (no speedstepper patch).

Lion 10.7.2 install...

 

Thanks.

  • 1 month later...

Hello, i've got my hackintosh running really smooth and nice (asus p8z68-v pro - i5-2500k - gtx 260 - 8gb ram) and thanks to Flaked's steedstepper i managed to get sleep to work as well as couple p-states. This was achieved by running the system without a DSDT.aml, and once i've started using a slightly edited one in order to get my hdmi audio working properly it messed up my p-states which now are just two, the lowest and the highest (16 and 40). Does anyone have any clue on why this happens once you start using a DSDT ? Thanks in advance

  • 2 weeks later...

hy.. I like it. but.. this tool is only to debug/disover if pstate is running fine?

I don't understand if.. within the output.. I have to use those data for other scope..

 

can you explain?

  • 4 weeks later...

Hi,

 

I just tested out the MSRDumper and not sure if these results are correct for my 2600K (Not Overclocked):

 

CoreMulti(16)

PStatesReached: 16 + 34.

 

 

I have not yet installed a SSDT. My system is an Asus Z68 Deluxe with patched bios to allow native AICPUPM (no speedstepper patch).

Lion 10.7.2 install...

 

Thanks.

 

 

I'm getting a similar response with my 2500k, ASUS P8P67 Pro, with the BIOS hacked to allow native AICPUPM. Lion 10.7.3

I have the BIOS set to clock at 44x multiplier, so my P-states are just 16 and 44, there are no states in between.

Tried this tool on my Core i5 430m (don't know if this is a sandy bridge CPU).

 

Does not work for me :( I only get CoreMulti(0) with PstatesReached: <nothing displayed>.

I did dump my SSDT from chameleon with pstates=yes and cstates=yes (got message that SSDT was dumped fine).

 

Can anybody enlighten me if there is a fix to show whether speedstep is working or not?

I also tried MSR Tool in x86 mode, there it says my freq is changing (but program shuts down very quickly).

 

I use 64-bit Lion 10.7.3

 

Thanks!

  • 2 weeks later...

MSRDumper working.

 

Specs:

P8H67-M PRO B3

Core i5-2400 3.1Ghz -System reports 3.2Ghz - with turbo so it should go to 3.4Ghz

Generate C&P-states in com.apple.boot.plist

Using patched DSDT

 

01-03-12 20:55:13,000 kernel: MSRDumper CoreMulti(16)
01-03-12 20:55:13,000 kernel: MSRDumper PStatesReached: 16 19 32 33 34
01-03-12 20:55:14,000 kernel: MSRDumper CoreMulti(16)
01-03-12 20:55:14,000 kernel: MSRDumper PStatesReached: 16 19 32 33 34

 

Are these values correct? I only see the above generated lines.

Don't know if it enters 3.4Ghz?

 

Thanks. :)

Tried this tool on my Core i5 430m (don't know if this is a sandy bridge CPU).

 

Does not work for me :( I only get CoreMulti(0) with PstatesReached: <nothing displayed>.

I did dump my SSDT from chameleon with pstates=yes and cstates=yes (got message that SSDT was dumped fine).

 

Can anybody enlighten me if there is a fix to show whether speedstep is working or not?

I also tried MSR Tool in x86 mode, there it says my freq is changing (but program shuts down very quickly).

 

I use 64-bit Lion 10.7.3

 

Thanks!

 

I found a solution for my problem. So I thought to post it here for anybody else this workaround may work.

 

I downloaded IntelCPUMonitor.kext and SMCMonitor app and could check my frequencies and P, C states.

Good news! Speedstep is working :)

 

Nice job on the MSRDumper.kext though! Keep up the good work!

  • 2 weeks later...
  • 3 weeks later...

Hi Insanely MacSage, My birthday's coming up and I'm going to get the hardware for a hackintosh (thanks Dad!). Aside from Xcode, what other languages should I learn to use MSRDumper and RevoBoot? Thanks.

×
×
  • Create New...