Jump to content

GA-EX58 and GA-X58A DSDT native power management modifications

d00d

By d00d,
in Power Management

 Share
1,771 posts in this topic

Recommended Posts

FUT1L1TY
FUT1L1TY
Posted
Posted
Warning: Using the modified MacPro4_1.plist, then applying an Apple Software Update like Bonjour Update 2010-001, can break things so that you have no mouse or keyboard control at the login GUI.

Move the original IOPlatformPluginFamily.kext back into place before you restart your machine, this will cause the OS to update it's extensions cache, and any helper partition ones as well.

If you are reading this from another computer because you have locked yourself out, assuming you have enabled Remote Login, ssh in and do the above.

 

d00d, thank you for the tip. Would you be so kind as to post the original unmodified IOPlatformPluginFamily.kext for 10.6.2? I was being sloppy and forgot to make a backup.

 

Also, while we're on the topic, what is lost by using the original kext? Is it just the 22x multiplier?

Link to comment
Share on other sites
d00d
d00d
Posted
  • Author
Posted
d00d, thank you for the tip. Would you be so kind as to post the original unmodified IOPlatformPluginFamily.kext for 10.6.2? I was being sloppy and forgot to make a backup.

 

Also, while we're on the topic, what is lost by using the original kext? Is it just the 22x multiplier?

I'm assuming it's against this site's policy to post that, but you can extract it from the updater using Pacifist.

What's lost is the downward multiples, commonly referred to as speed step.

Link to comment
Share on other sites
Josvdp
Josvdp
Posted
Posted
Added to post 1;

DSDT.aml and dsdt.dsl for i7 920 and Xeon W3520, derived from GA-EX58-UD5 and BIOS F9m, with fixes (added 16 and 17) and audio option B: DSDT_GA-EX58-UD5_F9m_S3_920_W3520_v2.zip

DSDT.aml and dsdt.dsl for i7 950 and Xeon W3550, derived from GA-EX58-UD5 and BIOS F9m, with fixes (added 16 and 17) and audio option B: DSDT_GA-EX58-UD5_F9m_S3_950_W3550_v2.zip

DSDT.aml and dsdt.dsl for i7 975 and Xeon W3580, derived from GA-EX58-UD5 and BIOS F9m, with fixes (added 16 and 17) and audio option B: DSDT_GA-EX58-UD5_F9m_S3_975_W3580_v2.zip

Thank you for the update, although I've actually found out that editing the DSDT isn't that hard if you have SL already running on one partition.

 

I didn't update the bonjour fix, because I suspected that it would give trouble! But I'm not using the speedstep fix so I guess I can safely update it.

 

By the way, could you see if you have some time to respond to my previous post? I'm very close to having a stable build ;) You can find it here.

Link to comment
Share on other sites
d00d
d00d
Posted
  • Author
Posted
Thank you for the update, although I've actually found out that editing the DSDT isn't that hard if you have SL already running on one partition.

 

I didn't update the bonjour fix, because I suspected that it would give trouble! But I'm not using the speedstep fix so I guess I can safely update it.

 

By the way, could you see if you have some time to respond to my previous post? I'm very close to having a stable build :pirate2: You can find it here.

1. You may be able to use Applications:Utilities:Audio MIDI Setup to configure more than two speakers.

2. I used to have that problem with BIOSs previous to F9h.

3. The System Profiler is correct, C2RC3 and 4 boots 64 bit by default, and so there's no need to add the flag to com.apple.boot.plist.

You will also see RELEASE_X86_64 and `Kernel is LP64' in kernel.log.

Use -m instead, -p is for processor architecture, type `man uname' for more details;

[mac05:~] me% uname -m

x86_64

[mac05:~] me%

Link to comment
Share on other sites
FUT1L1TY
FUT1L1TY
Posted
Posted
I'm assuming it's against this site's policy to post that, but you can extract it from the updater using Pacifist.

What's lost is the downward multiples, commonly referred to as speed step.

 

Yes, using Pacifist is the way to go. Sorry about that. Is it OK to reinstall the MacPro4,1.plist after the Bonjour update or are they incompatible with each other? If so, is this sort of incompatibility likely to happen often in your opinion?

Link to comment
Share on other sites
d00d
d00d
Posted
  • Author
Posted
Yes, using Pacifist is the way to go. Sorry about that. Is it OK to reinstall the MacPro4,1.plist after the Bonjour update or are they incompatible with each other? If so, is this sort of incompatibility likely to happen often in your opinion?
Looks like an incompatibility, and even if demong1 updates it there's no guarantee that an Apple Software Update won't break it again.

I can't post at that other site even though I'm a member, so I hope someone else can let him know that there's an issue.

Link to comment
Share on other sites
Josvdp
Josvdp
Posted
Posted
1. You may be able to use Applications:Utilities:Audio MIDI Setup to configure more than two speakers.

2. I used to have that problem with BIOSs previous to F9h.

3. The System Profiler is correct, C2RC3 and 4 boots 64 bit by default, and so there's no need to add the flag to com.apple.boot.plist.

You will also see RELEASE_X86_64 and `Kernel is LP64' in kernel.log.

Use -m instead, -p is for processor architecture, type `man uname' for more details;

[mac05:~] me% uname -m

x86_64

[mac05:~] me%

Thank you for the help again!

 

1. I can't choose anything other than 2 channel, which means (I guess) that Audio isn't installed properly? That is a bummer :/

 

2. Ok, looks like I'm going to have to live with that then. Maybe I'll google it later somehow.

 

3. uname -m gives 64-bit, ok thanks. I got it from an earlier post of you, in that post you told to use -p ;)

Link to comment
Share on other sites
d00d
d00d
Posted
  • Author
Posted
Thank you for the help again!

 

1. I can't choose anything other than 2 channel, which means (I guess) that Audio isn't installed properly? That is a bummer :/

 

2. Ok, looks like I'm going to have to live with that then. Maybe I'll google it later somehow.

 

3. uname -m gives 64-bit, ok thanks. I got it from an earlier post of you, in that post you told to use -p :D

I can only get stereo as well.

Audio was easier in 10.5.x, here's what I used then;

http://www.insanelymac.com/forum/index.php?showtopic=140941

It looks like tmongkol now has 10.6.x solutions there too.

You may be able to get more than stereo using VoodooHDA or one of it's forks.

Link to comment
Share on other sites
2006C6
2006C6
Posted
Posted
I can only get stereo as well.

Audio was easier in 10.5.x, here's what I used then;

http://www.insanelymac.com/forum/index.php?showtopic=140941

It looks like tmongkol now has 10.6.x solutions there too.

You may be able to get more than stereo using VoodooHDA or one of it's forks.

 

I am using your latest Bios with Audio option B and the ALC889a kext on the Extreme version of this board - I have full audio - Analog Digital etc - Is this and different than you guys are showing in your audio preferences?

Link to comment
Share on other sites
d00d
d00d
Posted
  • Author
Posted
I am using your latest Bios with Audio option B and the ALC889a kext on the Extreme version of this board - I have full audio - Analog Digital etc - Is this and different than you guys are showing in your audio preferences?
Can you configure more than 2 output channels (stereo) in Applications:Utilities:Audio MIDI Setup?

He's looking for something like 5.1 (5 channels plus subwoofer).

I use the stereo line out connection to an amplifier, and I connect the subwoofer and two speakers to that.

Link to comment
Share on other sites
2006C6
2006C6
Posted
Posted
Can you configure more than 2 output channels (stereo) in Applications:Utilities:Audio MIDI Setup?

He's looking for something like 5.1 (5 channels plus subwoofer).

I use the stereo line out connection to an amplifier, and I connect the subwoofer and two speakers to that.

 

Ahhh - I gotcha - In MIDI I get the 2 channel option - However I am using the Digital out to a 5.1 Cambridge soundworks system - I have full Digital Surround this way

Link to comment
Share on other sites
LocusOfControl
LocusOfControl
Posted
Posted

Hi d00d

 

Just a quickie question, my processor section of my DSDT resembles yours (straight cut & paste). HP

 

However I run in 64bit mode so I was wondering what the best tools are to verify the C & P State magic working?

 

I know that the common suggestion is to do ioreg | grep CPUPlimit but these never worked for me, but I'm not convinced

this is definitive (how is this conclusion arrived at)

 

Out of curiosity I ran i-mark and it seems to show fluctuating voltages and my fans speed up and slow down

over time - reports my cpu temp as 27-28C at 2.8GHz (I have a big cooler and fans)

 

Any thoughts on whats happening?

 

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=65 v=1.040000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=81 v=1.296000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=80 v=1.280000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=66 v=1.056000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=65 v=1.040000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=80 v=1.280000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=65 v=1.040000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=67 v=1.072000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=79 v=1.264000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=77 v=1.232000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=80 v=1.280000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=65 v=1.040000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=80 v=1.280000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=79 v=1.264000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=74 v=1.184000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=68 v=1.088000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=74 v=1.184000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=65 v=1.040000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=80 v=1.280000

Jan 12 10:34:11 LocusOfControl [0x0-0x26026].ru.mark.mark-i[19898]: REG=65 v=1.040000

 

kextstat
Index Refs Address            Size       Wired      Name (Version) <Linked Against>
   1   60 0                  0          0          com.apple.kpi.bsd (10.2.0)
   2    4 0                  0          0          com.apple.kpi.dsep (10.2.0)
   3   85 0                  0          0          com.apple.kpi.iokit (10.2.0)
   4   91 0                  0          0          com.apple.kpi.libkern (10.2.0)
   5   71 0                  0          0          com.apple.kpi.mach (10.2.0)
   6   28 0                  0          0          com.apple.kpi.private (10.2.0)
   7   45 0                  0          0          com.apple.kpi.unsupported (10.2.0)
   8   13 0xffffff7f80600000 0x4000     0x4000     com.apple.iokit.IOACPIFamily (1.3.0) <7 6 4 3>
   9   22 0xffffff7f80604000 0x12000    0x12000    com.apple.iokit.IOPCIFamily (2.6) <7 5 4 3>
  10    1 0xffffff7f80616000 0x44000    0x44000    com.apple.driver.AppleACPIPlatform (1.3) <9 8 7 6 5 4 3>
  11    0 0xffffff7f8065a000 0x1b000    0x1b000    com.apple.driver.AppleIntelCPUPowerManagement (96.0.0) <7 6 5 4 3 1>
  12    3 0xffffff7f80675000 0x1a000    0x1a000    com.apple.iokit.IOStorageFamily (1.6) <7 6 5 4 3 1>
  13    0 0xffffff7f8068f000 0x12000    0x12000    com.apple.driver.DiskImages (281) <12 7 6 5 4 3 1>
  14    0 0xffffff7f806a1000 0x3000     0x3000     com.apple.driver.AppleIntelCPUPowerManagementClient (96.0.0) <7 6 5 4 3 1>
  15    0 0xffffff7f806a4000 0x8000     0x8000     com.apple.nke.applicationfirewall (2.1.11) <7 6 5 4 3 1>
  16    2 0xffffff7f806ac000 0x3000     0x3000     com.apple.kext.AppleMatch (1.0.0d1) <4 1>
  17    0 0xffffff7f806af000 0x4000     0x4000     com.apple.security.quarantine (0) <16 7 6 5 4 2 1>
  18    0 0xffffff7f806b3000 0x8000     0x8000     com.apple.security.sandbox (0) <16 7 6 5 4 2 1>
  19    0 0xffffff7f806bb000 0x3000     0x3000     com.apple.security.TMSafetyNet (6) <7 6 5 4 2 1>
  20    0 0xffffff7f806be000 0x3000     0x3000     com.apple.driver.AppleAPIC (1.4) <4 3>
  21    0 0xffffff7f806c1000 0x4000     0x4000     com.apple.driver.AppleSMBIOS (1.4) <7 4 3>
  22    0 0xffffff7f806c5000 0x3000     0x3000     com.apple.driver.AppleHPET (1.4) <8 7 5 4 3>
  23    0 0xffffff7f806c8000 0x6000     0x6000     com.apple.driver.AppleRTC (1.3) <8 5 4 3 1>
  24    7 0xffffff7f806ce000 0x42000    0x42000    com.apple.iokit.IOHIDFamily (1.6.1) <7 6 5 4 3 1>
  25    0 0xffffff7f80710000 0x4000     0x4000     com.apple.driver.AppleACPIButtons (1.3) <24 10 8 7 6 5 4 3 1>
  26    1 0xffffff7f80714000 0x3000     0x3000     com.apple.driver.AppleEFIRuntime (1.3.0) <7 5 4 3>
  27   10 0xffffff7f80717000 0x34000    0x34000    com.apple.iokit.IOUSBFamily (3.8.5) <9 7 5 4 3 1>
  28    0 0xffffff7f8074b000 0x10000    0x10000    com.apple.driver.AppleUSBUHCI (3.7.5) <27 9 7 5 4 3 1>
  29    3 0xffffff7f8075b000 0x7000     0x7000     com.apple.iokit.IOAHCIFamily (2.0.2) <5 4 3 1>
  30    0 0xffffff7f80762000 0xf000     0xf000     com.apple.driver.AppleAHCIPort (2.0.1) <29 9 5 4 3 1>
  32    0 0xffffff7f80773000 0x5000     0x5000     com.apple.AppleFSCompression.AppleFSCompressionTypeZlib (1.0.0d1) <6 4 3 2 1>
  33    0 0xffffff7f80778000 0x14000    0x14000    com.apple.driver.AppleUSBEHCI (3.7.5) <27 9 7 5 4 3 1>
  34    0 0xffffff7f8078c000 0x4000     0x4000     org.netkas.fakesmc (2) <8 7 4 3>
  35    2 0xffffff7f80790000 0x4b000    0x4b000    com.apple.iokit.IOFireWireFamily (4.1.7) <5 4 3 1>
  36    0 0xffffff7f807db000 0x28000    0x28000    com.apple.driver.AppleFWOHCI (4.4.0) <35 9 7 6 5 4 3 1>
  37    0 0xffffff7f80803000 0x4000     0x4000     com.apple.BootCache (31) <7 6 5 4 3 1>
  38    0 0xffffff7f80807000 0x7000     0x7000     com.apple.driver.AppleEFINVRAM (1.3.0) <26 7 5 4 3>
  39    0 0xffffff7f8080e000 0x2000     0x2000     com.apple.iokit.IOUSBUserClient (3.8.5) <27 7 5 4 3 1>
  40    0 0xffffff7f80810000 0xf000     0xf000     com.apple.driver.AppleUSBHub (3.8.4) <27 5 4 3 1>
  41    0 0xffffff7f8081f000 0x14000    0x14000    com.apple.iokit.IOAHCIBlockStorage (1.6.0) <29 12 5 4 3 1>
  42    0 0xffffff7f80833000 0x3000     0x3000     com.apple.driver.XsanFilter (402.1) <12 5 4 3 1>
  43    1 0xffffff7f80836000 0x4000     0x4000     com.apple.driver.AppleUSBComposite (3.7.5) <27 4 3 1>
  44    0 0xffffff7f8083a000 0x4000     0x4000     com.apple.driver.AppleUSBMergeNub (3.8.5) <43 27 4 3 1>
  45    4 0xffffff7f8083e000 0x42000    0x42000    com.apple.iokit.IOBluetoothFamily (2.2.4f3) <7 5 4 3 1>
  46    1 0xffffff7f80880000 0x8000     0x8000     com.apple.driver.AppleUSBBluetoothHCIController (2.2.4f3) <45 27 7 5 4 3>
  47    0 0xffffff7f80888000 0x6000     0x6000     com.apple.driver.BroadcomUSBBluetoothHCIController (2.2.4f3) <46 45 27 4 3>
  48    1 0xffffff7f8088e000 0x2000     0x2000     com.apple.driver.AppleHIDKeyboard (1.2.0a3) <24 4 3>
  49    1 0xffffff7f80890000 0x5000     0x5000     com.apple.iokit.IOUSBHIDDriver (3.8.4) <27 24 5 4 3 1>
  50    0 0xffffff7f80895000 0x2000     0x2000     com.apple.driver.AppleUSBHIDKeyboard (1.2.0a3) <49 48 24 4 3>
  51    1 0xffffff7f80897000 0x19000    0x19000    com.apple.iokit.IOSCSIArchitectureModelFamily (2.6.0) <5 4 3 1>
  52    0 0xffffff7f808b0000 0x9000     0x9000     com.apple.iokit.IOAHCISerialATAPI (1.2.1) <51 29 5 4 3 1>
  53    0 0xffffff7f808b9000 0xa000     0xa000     com.apple.filesystems.autofs (2.1.0) <7 6 5 4 3 1>
  54    1 0xffffff7f808c3000 0x58000    0x58000    com.apple.filesystems.ntfs (3.1) <7 6 5 4 1>
  55    0 0xffffff7f8091b000 0x3000     0x3000     com.apple.driver.AppleLPC (1.4.9) <9 5 4 3>
  56    0 0xffffff7f8091e000 0x2000     0x2000     com.apple.driver.AppleSMBusPCI (1.0.4d0) <9 5 4 3>
  57    2 0xffffff7f80920000 0xc000     0xc000     com.apple.driver.IOPlatformPluginFamily (4.0.1d0) <6 5 4 3>
  58    2 0xffffff7f8092c000 0xb000     0xb000     com.apple.driver.AppleSMC (3.0.1d2) <8 7 5 4 3>
  59    0 0xffffff7f80937000 0x11000    0x11000    com.apple.driver.ACPI_SMC_PlatformPlugin (4.0.1d0) <58 57 9 8 7 6 5 4 3>
  60    2 0xffffff7f80948000 0x8000     0x8000     com.apple.iokit.IOHDAFamily (1.7.9a4) <5 4 3 1>
  61    9 0xffffff7f80950000 0x23000    0x23000    com.apple.iokit.IOGraphicsFamily (2.0) <9 7 5 4 3>
  62    1 0xffffff7f80973000 0x14000    0x14000    com.apple.driver.AppleHDAController (1.7.9a4) <61 60 9 5 4 3 1>
  63    7 0xffffff7f80987000 0x34000    0x34000    com.apple.iokit.AppleProfileFamily (41) <9 7 6 5 4 3 1>
  65    2 0xffffff7f809c3000 0x1a000    0x1a000    com.apple.iokit.IONetworkingFamily (1.9) <7 6 5 4 3 1>
  66    0 0xffffff7f809dd000 0x9000     0x9000     com.apple.iokit.IOFireWireIP (2.0.3) <65 35 5 4 3 1>
  68    2 0xffffff7f80a04000 0x2d000    0x2d000    com.apple.kext.ATISupport (6.0.6) <61 9 8 7 5 4 3 1>
  69    0 0xffffff7f80a31000 0x98000    0x98000    com.apple.kext.ATI4800Controller (6.0.6) <68 61 9 8 5 4 3 1>
  70    1 0xffffff7f80ac9000 0x2000     0x2000     com.apple.iokit.IOSMBusFamily (1.1) <5 4 3>
  71    0 0xffffff7f80acb000 0xb000     0xb000     com.apple.driver.AppleSMBusController (1.0.4d0) <70 9 8 5 4 3>
  72    2 0xffffff7f80ad6000 0x5000     0x5000     com.apple.kext.OSvKernDSPLib (1.3) <5 4>
  73    3 0xffffff7f80adb000 0x1b000    0x1b000    com.apple.iokit.IOAudioFamily (1.7.2fc1) <72 5 4 3 1>
  74    0 0xffffff7f80af6000 0x4000     0x4000     com.apple.driver.AudioIPCDriver (1.1.2) <73 5 4 3 1>
  75    2 0xffffff7f80afa000 0xf000     0xf000     com.apple.iokit.IONDRVSupport (2.0) <61 9 7 5 4 3>
  76    1 0xffffff7f80b09000 0x7c000    0x7c000    com.apple.driver.DspFuncLib (1.7.9a4) <73 72 5 4 3 1>
  77    0 0xffffff7f80b85000 0xb3000    0xb3000    com.apple.driver.AppleHDA (1.7.9a4) <76 75 73 62 61 60 5 4 3 1>
  78    0 0xffffff7f80c38000 0x8000     0x8000     com.apple.driver.AppleIntelNehalemProfile (11) <63 6 4 3>
  79    0 0xffffff7f80c40000 0x15000    0x15000    com.apple.driver.Intel82574L (1.0.4b1) <65 9 5 4 3 1>
  80    0 0xffffff7f80c55000 0x5000     0x5000     com.apple.Dont_Steal_Mac_OS_X (7.0.0) <58 7 4 3 1>
  83    0 0xffffff7f80c64000 0x177000   0x177000   com.apple.ATIRadeonX2000 (6.0.6) <75 61 9 7 6 5 4 3 1>
  84    1 0xffffff7f80ddb000 0xa000     0xa000     com.apple.iokit.IOSerialFamily (10.0.3) <7 6 5 4 3 1>
  85    0 0xffffff7f80de5000 0xa000     0xa000     com.apple.iokit.IOBluetoothSerialManager (2.2.4f3) <84 7 5 4 3 1>
  86    1 0xffffff7f80def000 0x9000     0x9000     com.apple.driver.AppleMultitouchDriver (204.9) <24 7 6 5 4 3 1>
  87    1 0xffffff7f80df8000 0xd000     0xd000     com.apple.driver.IOBluetoothHIDDriver (2.2.4f3) <45 24 4 3>
  88    0 0xffffff7f80e05000 0xa000     0xa000     com.apple.driver.AppleBluetoothMultitouch (30.9) <87 86 45 24 5 4 3>
  89    0 0xffffff7f80e0f000 0x12000    0x12000    com.apple.kext.ATIFramebuffer (6.0.6) <68 61 9 8 7 5 4 3 1>
  90    0 0xffffff7f80e21000 0xc000     0xc000     com.apple.iokit.IOSurface (73.0) <7 5 4 3 1>
  91    0 0xffffff7f80e2d000 0x5000     0x5000     com.apple.driver.AppleUpstreamUserClient (3.1.0) <61 9 8 7 5 4 3 1>
  92    0 0xffffff7f80e32000 0x4000     0x4000     com.apple.iokit.KLog (3.7.5) <27 4 3 1>
  93    0 0xffffff7f80e36000 0x4000     0x4000     com.evosx86.driver.lspcidrv (1.0) <4 3>
  94    0 0xffffff7f80e3a000 0x3000     0x3000     com.apple.driver.AppleProfileCallstackAction (20) <63 5 4 3 1>
  96    0 0xffffff7f80e42000 0x2000     0x2000     com.apple.driver.AppleProfileKEventAction (10) <63 4 3 1>
  97    0 0xffffff7f80e44000 0x5000     0x5000     com.apple.driver.AppleHWSensor (1.9.2d0) <5 4 3>
  98    0 0xffffff7f80e49000 0x9000     0x9000     com.apple.driver.AGPM (100.9.3) <61 9 5 4 3>
  99    0 0xffffff7f80e52000 0x9000     0x9000     com.apple.driver.AppleTyMCEDriver (1.0.1d8) <57 9 8 7 6 5 4 3 1>
 100    0 0xffffff7f80e5b000 0x2000     0x2000     com.apple.driver.AppleProfileRegisterStateAction (10) <63 4 3 1>
 101    0 0xffffff7f80e5d000 0x2000     0x2000     com.apple.driver.AppleProfileThreadInfoAction (14) <63 6 4 3 1>
 102    0 0xffffff7f80e5f000 0x2000     0x2000     com.apple.driver.AppleProfileTimestampAction (10) <63 5 4 3 1>
 103    0 0xffffff7f80e61000 0x3000     0x3000     com.apple.driver.AppleProfileReadCounterAction (17) <63 6 4 3>
 105    0 0xffffff7f809bb000 0x4000     0x4000     ru.mark.driver.RingAccess (0.41) <7 5 4 3>

Link to comment
Share on other sites
d00d
d00d
Posted
  • Author
Posted
Hi d00d

 

Just a quickie question, my processor section of my DSDT resembles yours (straight cut & paste). HP

 

However I run in 64bit mode so I was wondering what the best tools are to verify the C & P State magic working?

 

I know that the common suggestion is to do ioreg | grep CPUPlimit but these never worked for me, but I'm not convinced

this is definitive (how is this conclusion arrived at)

 

Out of curiosity I ran i-mark and it seems to show fluctuating voltages and my fans speed up and slow down

over time - reports my cpu temp as 27-28C at 2.8GHz (I have a big cooler and fans)

 

Any thoughts on whats happening?

I'm unfamiliar with i-mark, and a casual search doesn't locate it, but one way to check that the [P|C]States are working is that there are no related errors in kernel.log;

kernel[0]: ACPI_SMC_PlatformPlugin::gatherCStateOverrides - failed to set c-state demotion data: -1

kernel[0]: ACPI_SMC_PlatformPlugin::pushCPU_CSTData - _CST evaluation failed

kernel[0]: ACPI_SMC_PlatformPlugin::getCPU_PSSData - _PSS evaluation failed

kernel[0]: WARNING: ACPI_SMC_CtrlLoop::initCPUCtrlLoop - turbo enabled but no turbo P-state found

 

Boot 32 bit and use Chrysaor's MSR Tools.

This will show you the turbo and plus one turbo ratios if you're using turbo, and the speed step downward ratios if you're using demong1's MacPro4_1.plist (see Bonjour Update 2010-001 warning at bottom of post 1).

 

In ioreg at IOService:/AppleACPIPlatformExpert/CPU0@0/AppleACPICPU/ACPI_SMC_PlatformPlugin you will see the CState's CSTinfo and the PState's PerformanceStateArray.

 

For the speed step downward ratios, in ioreg at IOService:/AppleACPIPlatformExpert/CPU0@0/AppleACPICPU/ACPI_SMC_PlatformPlugin you will see CPUPLimit with a value of 0x0, a different value if it's not activated, or not there at all if not enabled.

Link to comment
Share on other sites
LocusOfControl
LocusOfControl
Posted
Posted
I'm unfamiliar with i-mark, and a casual search doesn't locate it, but one way to check that the [P|C]States are working is that there are no related errors in kernel.log;

kernel[0]: ACPI_SMC_PlatformPlugin::gatherCStateOverrides - failed to set c-state demotion data: -1

kernel[0]: ACPI_SMC_PlatformPlugin::pushCPU_CSTData - _CST evaluation failed

kernel[0]: ACPI_SMC_PlatformPlugin::getCPU_PSSData - _PSS evaluation failed

kernel[0]: WARNING: ACPI_SMC_CtrlLoop::initCPUCtrlLoop - turbo enabled but no turbo P-state found

 

Boot 32 bit and use Chrysaor's MSR Tools.

This will show you the turbo and plus one turbo ratios if you're using turbo, and the speed step downward ratios if you're using demong1's MacPro4_1.plist (see Bonjour Update 2010-001 warning at bottom of post 1).

 

In ioreg at IOService:/AppleACPIPlatformExpert/CPU0@0/AppleACPICPU/ACPI_SMC_PlatformPlugin you will see the CState's CSTinfo and the PState's PerformanceStateArray.

 

For the speed step downward ratios, in ioreg at IOService:/AppleACPIPlatformExpert/CPU0@0/AppleACPICPU/ACPI_SMC_PlatformPlugin you will see CPUPLimit with a value of 0x0, a different value if it's not activated, or not there at all if not enabled.

 

 

A quick check shows that no errors since Nov 27th which sounds about the time I started fixing this

 

kernel.log.4:Nov 27 23:17:38 LocusOfControl kernel[0]: ACPI_SMC_PlatformPlugin::pushCPU_CSTData - _CST evaluation failed

 

No errors since ...

 

I got the i-mark link from the gigabyte thread

http://www.insanelymac.com/forum/index.php...p;#entry1377246

 

I notice in ioreg I have what appear to be 10 p-states, Thus is what I translated the data from ioreg to be

 

Name (_PSS, Package (0x0A)

{

Package (0x06)

{

0x00000A65,

0x0001FBD0,

0x0000000A,

0x0000000A,

0x00000015,

0x00000015

},

 

etc, but I don't see any c-state info (yet the error in the log is gone and there is no CPUPLimit)

 

strange ? Is it possible there are differences between C0 & D0 i7's?

 

 

(by the way I took the bonjour update as soon as it came out - bonjour always worked out of the box for me and

I've subsequently replaced the onboard NIC's with an apple gig-e card)

post-383752-1263311246_thumb.png

Link to comment
Share on other sites
mm67
mm67
Posted
Posted
A quick check shows that no errors since Nov 27th which sounds about the time I started fixing this

 

kernel.log.4:Nov 27 23:17:38 LocusOfControl kernel[0]: ACPI_SMC_PlatformPlugin::pushCPU_CSTData - _CST evaluation failed

 

No errors since ...

 

I got the i-mark link from the gigabyte thread

http://www.insanelymac.com/forum/index.php...p;#entry1377246

 

I notice in ioreg I have what appear to be 10 p-states, Thus is what I translated the data from ioreg to be

 

Name (_PSS, Package (0x0A)

{

Package (0x06)

{

0x00000A65,

0x0001FBD0,

0x0000000A,

0x0000000A,

0x00000015,

0x00000015

},

 

etc, but I don't see any c-state info (yet the error in the log is gone and there is no CPUPLimit)

 

strange ? Is it possible there are differences between C0 & D0 i7's?

 

 

(by the way I took the bonjour update as soon as it came out - bonjour always worked out of the box for me and

I've subsequently replaced the onboard NIC's with an apple gig-e card)

 

That CSTInfo line tells that you have some kind of valid CST table loaded.

Link to comment
Share on other sites
LocusOfControl
LocusOfControl
Posted
Posted
That CSTInfo line tells that you have some kind of valid CST table loaded.

 

 

I have 0x1240105 - doesn't seem to correspond to anything in DSDT (or SSDT)

Do I just assume it is OK?

 

 

Incidentally , in FakeSMC you have REV=ATkPAAAF how do you translate this to get 1.39f5 ???????

 

"Modify fakesmc.kext/Contents/Info.plist in two places with MacPro4,1 specific information (1.30f3 and smc-napa changed to 1.39f5 and smc-thurley)."

 

In FakeSMC Revision=<01 39 0f 00 00 05> shown in plist editor. I have ATkPAAAF set via vi

 

AppleSMC has smc-version 1.39f5, I assume they are not equal?

 

Do these have to match? Is this important?

post-383752-1263313026_thumb.png

Link to comment
Share on other sites
mm67
mm67
Posted
Posted
I have 0x1240105 - doesn't seem to correspond to anything in DSDT (or SSDT)

Do I just assume it is OK?

 

We all have that same value with 10.6.2, including real Mac's. It only seems to tell that you have a valid table.

Link to comment
Share on other sites
LocusOfControl
LocusOfControl
Posted
Posted
We all have that same value with 10.6.2, including real Mac's. It only seems to tell that you have a valid table.

 

 

Thanks,

 

Any confirmation that the SMC key is correct d00d ? ie what language is that and does 01 39 0f 00 00 05

some how translate to 1.39f5 ?

 

the first 4 numbers seem a straight fit to 1.39 but the next 8 seem an odd fit to f5

Link to comment
Share on other sites
LocusOfControl
LocusOfControl
Posted
Posted
I have 0x1240105 - doesn't seem to correspond to anything in DSDT (or SSDT)

Do I just assume it is OK?

 

 

Incidentally , in FakeSMC you have REV=ATkPAAAF how do you translate this to get 1.39f5 ???????

 

"Modify fakesmc.kext/Contents/Info.plist in two places with MacPro4,1 specific information (1.30f3 and smc-napa changed to 1.39f5 and smc-thurley)."

 

In FakeSMC Revision=<01 39 0f 00 00 05> shown in plist editor. I have ATkPAAAF set via vi

 

AppleSMC has smc-version 1.39f5, I assume they are not equal?

 

Do these have to match? Is this important?

 

 

out of curiosity, I changed the value of revision to <0139f5000000>

 

On reboot I got an error in kernel log

Jan 12 17:25:55 localhost kernel[0]: FakeSMC: key REV has wrong length 3, should be 4, not adding

 

I notice though that AppleSMC no longer has an attribute called smc-version set but still says smc-thurley

 

I haven't noticed anything different ie no extra info

Link to comment
Share on other sites
LocusOfControl
LocusOfControl
Posted
Posted
I have 0x1240105 - doesn't seem to correspond to anything in DSDT (or SSDT)

Do I just assume it is OK?

 

 

Incidentally , in FakeSMC you have REV=ATkPAAAF how do you translate this to get 1.39f5 ???????

 

"Modify fakesmc.kext/Contents/Info.plist in two places with MacPro4,1 specific information (1.30f3 and smc-napa changed to 1.39f5 and smc-thurley)."

 

In FakeSMC Revision=<01 39 0f 00 00 05> shown in plist editor. I have ATkPAAAF set via vi

 

AppleSMC has smc-version 1.39f5, I assume they are not equal?

 

Do these have to match? Is this important?

 

 

In case anyone is curious

 

<01 39 0f 00 00 05> is hex encoded to ATkPAAAF in base 64 :unsure:

Link to comment
Share on other sites
Josvdp
Josvdp
Posted
Posted
Ahhh - I gotcha - In MIDI I get the 2 channel option - However I am using the Digital out to a 5.1 Cambridge soundworks system - I have full Digital Surround this way

Oh that is very good news! So, even though system profiler, nor the midi setup shows more than 2 channel, it is possible? That's a nice future prospect.

 

Anyway, the reason why I was posting again here was that I seem to get KP's now and then. It has to do with my VMware installation for sure, because that's when they happen (sometimes when I start VMware). I'm just wondering if it is theoretically possible to run VMware without problems on OSX86. If not, then at least I know where I stand.

 

Here's the KP, does anybody understand what's happening here?

post-541676-1263387646_thumb.jpg

Link to comment
Share on other sites
d00d
d00d
Posted
  • Author
Posted
In case anyone is curious

 

<01 39 0f 00 00 05> is hex encoded to ATkPAAAF in base 64

Thanks LocusOfControl.

 

Oh that is very good news! So, even though system profiler, nor the midi setup shows more than 2 channel, it is possible? That's a nice future prospect.

 

Anyway, the reason why I was posting again here was that I seem to get KP's now and then. It has to do with my VMware installation for sure, because that's when they happen (sometimes when I start VMware). I'm just wondering if it is theoretically possible to run VMware without problems on OSX86. If not, then at least I know where I stand.

 

Here's the KP, does anybody understand what's happening here?

I'm running several VMware 3.0.1 images successfully without panic.

The KP looks like what I get with an unstable over clock, does any other high CPU activity application cause a KP?

Run `top -ocpu' in Terminal.

Link to comment
Share on other sites
Josvdp
Josvdp
Posted
Posted
Thanks LocusOfControl.

 

I'm running several VMware 3.0.1 images successfully without panic.

The KP looks like what I get with an unstable over clock, does any other high CPU activity application cause a KP?

Run `top -ocpu' in Terminal.

Mmh, that's funny! Because I have actually thought about these KP's being caused by my overclock. But since my overclock is not very spectacular (3,4 gHz without higher Vcore) and since it doesn't happen randomly, but rather when I start VMware. I thought it didn't have to do anything with it. But you might be right! Maybe I'll put mprime on tonight to check the stability.

 

Is there a way to interpret these KP's? Because to me it just looks like a big pile of error codes. If I could understand these KP's a bit more, I can see the relationship between them in the future myself. In that case, I will log all the KP's and see if they have the same cause.

 

I guess I could read something like this or this.

Link to comment
Share on other sites
kdawg
kdawg
Posted
Posted
Mmh, that's funny! Because I have actually thought about these KP's being caused by my overclock. But since my overclock is not very spectacular (3,4 gHz without higher Vcore) and since it doesn't happen randomly, but rather when I start VMware. I thought it didn't have to do anything with it. But you might be right! Maybe I'll put mprime on tonight to check the stability.

 

Is there a way to interpret these KP's? Because to me it just looks like a big pile of error codes. If I could understand these KP's a bit more, I can see the relationship between them in the future myself. In that case, I will log all the KP's and see if they have the same cause.

Be sure the voltage for your RAM is high enough. I had to up mine to 2.1v before it ran stable. Auto was only giving it 1.8v. Check the specs for your RAM. Make sure you set the timings too. You can check out my BIOS settings in my signature however I have a P45 MOBO some of it will apply to you.
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...