tinush Posted June 29, 2010 Share Posted June 29, 2010 It looks like you don't have C-states, add C1E and your temps should be same as on Windows. Thanx for spotting that T Link to comment Share on other sites More sharing options...
FKA Posted June 29, 2010 Author Share Posted June 29, 2010 @ mm67 Hi there mm67, can i ask a question? My previous Gigabyte board died and got a asus p5q-em This board with a e8500 gives vanilla speedstep, but i'm not sure if all is OK (temps at idle 53c) Is there anything i can change to get the temps down (on windows it idles at 34c) Thnx T Check to see if AppleLPC.kext is loading. I have vanilla speedstep with my MSI board but gain between 5 and 10 deg whithout AppleLPC even though stepping is working. See 1st post for getting AppleLPC working with DSDT patch. D Link to comment Share on other sites More sharing options...
kdawg Posted June 29, 2010 Share Posted June 29, 2010 Using stock Vcore is by no means not necessary for stable overclock, it's just one more stupid Gigabyte bug that C-states don't work if you use a manually set Vcore value in bios. This is starting to veer off topic but I actually discovered if I keep my FSB below 460 I can set my VCore manually and keep C States. So far I've tried 444, and 450 they I still show voltage changes in mark-i. The second I go to 460 the voltage stoping changing and stays at max. I'm stable at 450 as far as mprime is concerned. I have my VCore set at around 1.36v. I notice a good 2-3 degree difference in temps when C States are working, idle temps are 38-39. Even when they're not working my temps idle are still around 40-41 degrees. Link to comment Share on other sites More sharing options...
mm67 Posted June 29, 2010 Share Posted June 29, 2010 Check to see if AppleLPC.kext is loading. I have vanilla speedstep with my MSI board but gain between 5 and 10 deg whithout AppleLPC even though stepping is working. See 1st post for getting AppleLPC working with DSDT patch. D I never even remember that ICH10R needs a fix for AppLPC, that seems to be missing since AppleLPC is not loaded on that IOregistry dump. Link to comment Share on other sites More sharing options...
kdawg Posted June 29, 2010 Share Posted June 29, 2010 I never even remember that ICH10R needs a fix for AppLPC, that seems to be missing since AppleLPC is not loaded on that IOregistry dump.I have to set my ID to 3A18 (ICH10). I'm sure once Apple updates the MacPros they'll add support for ICH10R as long as they keep using Intel processors. Link to comment Share on other sites More sharing options...
tinush Posted June 29, 2010 Share Posted June 29, 2010 I never even remember that ICH10R needs a fix for AppLPC, that seems to be missing since AppleLPC is not loaded on that IOregistry dump. it's it called different, i can remember the other name for asus board Found it a few day's ago on project osx site. i know that it is running T I have to set my ID to 3A18 (ICH10). I'm sure once Apple updates the MacPros they'll add support for ICH10R as long as they keep using Intel processors. i remember it's on 3A16 T edit > SBRG see pic Link to comment Share on other sites More sharing options...
mm67 Posted June 29, 2010 Share Posted June 29, 2010 it's it called different, i can remember the other name for asus board Found it a few day's ago on project osx site. i know that it is running T It's SBRG in your dsdt Link to comment Share on other sites More sharing options...
tinush Posted June 29, 2010 Share Posted June 29, 2010 It's SBRG in your dsdt posted a pic in the previous post. looks like SBRG is working T Link to comment Share on other sites More sharing options...
mm67 Posted June 29, 2010 Share Posted June 29, 2010 posted a pic in the previous post. looks like SBRG is working T Search for AppleLPC, not for SBRG. Link to comment Share on other sites More sharing options...
tinush Posted June 29, 2010 Share Posted June 29, 2010 Search for AppleLPC, not for SBRG. OK. my misunderstanding T Link to comment Share on other sites More sharing options...
mm67 Posted June 29, 2010 Share Posted June 29, 2010 This is starting to veer off topic but I actually discovered if I keep my FSB below 460 I can set my VCore manually and keep C States. So far I've tried 444, and 450 they I still show voltage changes in mark-i. The second I go to 460 the voltage stoping changing and stays at max. I'm stable at 450 as far as mprime is concerned. I have my VCore set at around 1.36v. I notice a good 2-3 degree difference in temps when C States are working, idle temps are 38-39. Even when they're not working my temps idle are still around 40-41 degrees. That's interesting, there must be some kind of difference in our bioses, I'm now trying with Vcore 1.225 and FSB 333 (both stock) and C-states don't work. For me only options are Vcore Normal or Vcore auto & FSB control disabled. Your cpu seems to really like volts, I can run 4.1 GHz, 483 * 8.5 with 1.38 volts, LLC disabled. Link to comment Share on other sites More sharing options...
msm Posted June 29, 2010 Share Posted June 29, 2010 This is starting to veer off topic... Sorry for the slightly off-topic (ok, mostly off-topic) questions, but if I could just close the loop on one of mine. Are you changing your dsdt p-state voltage values for each change in overclock? When I ran p-state changer to get values at both stock speed and overclocked (with a dsdt without any p-state info), the fid and vid numbers were identical at each speed. Is this your experience as well? The overclocking experience seems fairly fragmented on the forum and I haven't been able to get a clear idea about this in relation to p-states in the dsdt, especially for our processor. Thanks! Link to comment Share on other sites More sharing options...
mm67 Posted June 29, 2010 Share Posted June 29, 2010 Sorry for the slightly off-topic (ok, mostly off-topic) questions, but if I could just close the loop on one of mine. Are you changing your dsdt p-state voltage values for each change in overclock? When I ran p-state changer to get values at both stock speed and overclocked (with a dsdt without any p-state info), the fid and vid numbers were identical at each speed. Is this your experience as well? The overclocking experience seems fairly fragmented on the forum and I haven't been able to get a clear idea about this in relation to p-states in the dsdt, especially for our processor. Thanks! No, you don't need to change anything in dsdt when overclocking. Link to comment Share on other sites More sharing options...
kdawg Posted June 29, 2010 Share Posted June 29, 2010 That's interesting, there must be some kind of difference in our bioses, I'm now trying with Vcore 1.225 and FSB 333 (both stock) and C-states don't work. For me only options are Vcore Normal or Vcore auto & FSB control disabled. Your cpu seems to really like volts, I can run 4.1 GHz, 483 * 8.5 with 1.38 volts, LLC disabled. Out of curiosity you don't have any problem with FakeSMC and C states? Are you using the latest revision from the SVN? Link to comment Share on other sites More sharing options...
mm67 Posted June 29, 2010 Share Posted June 29, 2010 Out of curiosity you don't have any problem with FakeSMC and C states? Are you using the latest revision from the SVN? No I'm not using latest version. I'm using rev. 218 and SuperIO plugin. Link to comment Share on other sites More sharing options...
tinush Posted June 29, 2010 Share Posted June 29, 2010 Search for AppleLPC, not for SBRG. thnx mm67 got it working T dsdt.dsl_p5q_em_Final.zip Link to comment Share on other sites More sharing options...
kdawg Posted June 29, 2010 Share Posted June 29, 2010 No I'm not using latest version. I'm using rev. 218 and SuperIO plugin.If you're not having C-State issues with it could you send it to me with the plugins? Thanks. Link to comment Share on other sites More sharing options...
MiniHack Posted June 29, 2010 Share Posted June 29, 2010 Please help - Strange Scope (_PR) ! I am trying to fix up my Vostro 3500 DSDT (i5 430M processor) . I have made all the usual changes recommended and HPET, LPC kexts etc. are loading fine but I cannot get to a stage where removal of NullCpuPMManagement.kext is possible and that damn KP will just not go away. I think the problem may be that the DSDT has an unusual layout for Scope (_PR) which seems to call on the SSDTs for information and does not itself have the normal processor declarations. I'd be grateful if someone could take a look at the zip folder and point me in a good direction. In the zip are the vanilla DSDT and two SSDT tables and also my work in progress dsdt which is fine as far as it goes and has no errors, warnings or remarks. I tried adding the SSDTs into the DSDT to complete scope(_PR) but had no joy. Speedstep on my Zotac was a piece of cake compared to this.... StrangeDSDT.zip Sorry for the "bump". Won't do it again, but just wondered if anyone might be able to contribute to this..... If there's no reply then I'll just let it go. Thanks. Link to comment Share on other sites More sharing options...
mm67 Posted June 29, 2010 Share Posted June 29, 2010 If you're not having C-State issues with it could you send it to me with the plugins? Thanks. It's the one that you can download from project's front page. I just tried latest from svn, C-states work but SuperIO plugin doesn't seem to work. Link to comment Share on other sites More sharing options...
00diabolic Posted June 29, 2010 Share Posted June 29, 2010 131 error.. %$^@ Can someone help me here. i followed the guide but I cant get my DSDT to compile without errors. I followed all the steps exactly. Here is the code I input to give me 10 p-states for my t9300 Scope (_PR) { Processor (CPU0, 0x00, 0x00001010, 0x06) {} Processor (CPU1, 0x01, 0x00001010, 0x06) {} Scope (_PR.CPU0) { Method (_PSS, 0, NotSerialized) { Return (Package (0x10) { Package (0x06) { Zero, Zero, 0x10, 0x10, 0x4C22, Zero }, Package (0x06) { Zero, Zero, 0x10, 0x10, 0x4B21, One }, Package (0x06) { Zero, Zero, 0x10, 0x10, 0x4A1F, 0x02 }, Package (0x06) { Zero, Zero, 0x10, 0x10, 0x491D, 0x03 }, Package (0x06) { Zero, Zero, 0x10, 0x10, 0x481C, 0x04 }, Package (0x06) { Zero, Zero, 0x10, 0x10, 0x471A, 0x05 }, Package (0x06) { Zero, Zero, 0x10, 0x10, 0x4618, 0x06 }, Package (0x06) { Zero, Zero, 0x10, 0x10, 0x8A1B, 0x07 }, Package (0x06) { Zero, Zero, 0x10, 0x10, 0x881A, 0x08 }, Package (0x06) { Zero, Zero, 0x10, 0x10, 0x8619, 0x09 } }) } Method (_PSD, 0, NotSerialized) { Return (Package (0x05) { 0x05, Zero, Zero, 0xFC, 0x04 }) } Method (_CST, 0, NotSerialized) { Return (Package (0x02) { One, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, 0x9D, 0x03E8 } }) } } Scope (_PR.CPU1) { Method (_PSS, 0, NotSerialized) { Return (^^CPU0._PSS ()) } Method (_PSD, 0, NotSerialized) { Return (^^CPU0._PSD ()) } Method (_CST, 0, NotSerialized) { Return (Package (0x04) { 0x03, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address ,) }, One, Zero, 0x03E8 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000414, // Address ,) }, 0x02, One, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x08, // Bit Width 0x00, // Bit Offset 0x0000000000000415, // Address ,) }, 0x03, 0x55, 0xFA } }) } } What have I done wrong? Link to comment Share on other sites More sharing options...
kdawg Posted June 29, 2010 Share Posted June 29, 2010 131 error.. %$^@ Can someone help me here. i followed the guide but I cant get my DSDT to compile without errors. I followed all the steps exactly. Here is the code I input to give me 10 p-states for my t9300 What have I done wrong? Try this to start. Then add your other C States. Try and use [codeboxes] instead. Keep the threads shorter. Scope (_PR) { Processor (CPU0, 0x00, 0x00001010, 0x06) { Alias (PSS, _PSS) Alias (PSD, _PSD) Alias (CST, _CST) } Processor (CPU1, 0x01, 0x00001010, 0x06) { Alias (PSS, _PSS) Alias (PSD, _PSD) Alias (CST, _CST) } Name (PSS, Package (0x10){ Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x4C22, 0 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x4B21, 1 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x4A1F, 2 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x491D, 3 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x481C, 4 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x471A, 5 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x4618, 6 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x8A1B, 7 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x881A, 8 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x8619, 9 } }) Name (PSD, Package (0x05){0x05,Zero,Zero,0xFC,0x04}) Name (CST, Package (0x02){ 0x01, Package (0x04) {ResourceTemplate () {Register (FFixedHW, 0x01, 0x02, 0x000, ,)}, 0x01, 0x01, 0x03E8} }) } Link to comment Share on other sites More sharing options...
00diabolic Posted June 29, 2010 Share Posted June 29, 2010 Try this to start. Then add your other C States. Try and use [codeboxes] instead. Keep the threads shorter. Scope (_PR) { Processor (CPU0, 0x00, 0x00001010, 0x06) { Alias (PSS, _PSS) Alias (PSD, _PSD) Alias (CST, _CST) } Processor (CPU1, 0x01, 0x00001010, 0x06) { Alias (PSS, _PSS) Alias (PSD, _PSD) Alias (CST, _CST) } Name (PSS, Package (0x10){ Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x4C22, 0 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x4B21, 1 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x4A1F, 2 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x491D, 3 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x481C, 4 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x471A, 5 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x4618, 6 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x8A1B, 7 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x881A, 8 }, Package (0x06) { Zero, Zero, 0x0A, 0x0A, 0x8619, 9 } }) Name (PSD, Package (0x05){0x05,Zero,Zero,0xFC,0x04}) Name (CST, Package (0x02){ 0x01, Package (0x04) {ResourceTemplate () {Register (FFixedHW, 0x01, 0x02, 0x000, ,)}, 0x01, 0x01, 0x03E8} }) } OK thanks.. I added this as is to my DSDT replacing what I had and I get 15 errors.. I am wondering if this is going to work for me after reading that Thinkpad T60 owners go about getting speedstep to work completely differently then the formerlyknownas method... See here: http://forum.thinkpads.com/viewtopic.php?f=32&t=85344 I have a lenovo but i already tried to use what slicer has listed there to get c-states to work and it does not compile for me. I get 121 errors trying to use it. If you can help me figure this out Ill be soo grateful. Here is what MSR tools show for me right now. The CPU says 2700 but that is a bootloader detection issue I am working on with Valv. My CPU is 2500mhz. Anyway I get an error from the console that says this.. 6/30/10 1:26:27 AM kernel WARNING - ACPI_SMC_CtrlLoop::initCPUCtrlLoop - no sub-config match for MacBookPro4,1 with 6 p-states, using default stepper instead 6/30/10 3:32:13 AM DashboardClient[30175] WARNING: The current implementation has no specific code to support CPUs with signature template 67184! Here is my current kextstat also: 1 58 0 0 0 com.apple.kpi.bsd (10.2.0) 2 4 0 0 0 com.apple.kpi.dsep (10.2.0) 3 84 0 0 0 com.apple.kpi.iokit (10.2.0) 4 90 0 0 0 com.apple.kpi.libkern (10.2.0) 5 75 0 0 0 com.apple.kpi.mach (10.2.0) 6 24 0 0 0 com.apple.kpi.private (10.2.0) 7 46 0 0 0 com.apple.kpi.unsupported (10.2.0) 8 0 0 0 0 com.apple.kernel.6.0 (7.9.9) 9 0 0 0 0 com.apple.kernel.bsd (7.9.9) 10 3 0 0 0 com.apple.kernel.iokit (7.9.9) 11 3 0 0 0 com.apple.kernel.libkern (7.9.9) 12 1 0 0 0 com.apple.kernel.mach (7.9.9) 13 12 0x54f49000 0x4000 0x3000 com.apple.iokit.IOACPIFamily (1.3.0) <7 6 4 3> 14 16 0x5513b000 0x11000 0x10000 com.apple.iokit.IOPCIFamily (2.6) <7 5 4 3> 15 2 0x551db000 0x41000 0x40000 com.apple.driver.AppleACPIPlatform (1.3) <14 13 7 6 5 4 3> 16 0 0x4ed0d000 0x2000 0x1000 es.osx86.driver.EvOreboot (1.0.3) <4 3> 17 0 0x54f9d000 0x5000 0x4000 com.superhai.driver.VoodooBattery (1.3.3) <13 5 4 3> 18 0 0x54fad000 0x4000 0x3000 com.mojodojo.driver.VoodooMonitor (1.1.1d1) <7 5 4 3> 19 0 0x55198000 0x5000 0x4000 com.insanelymac.driver.VoodooPState (1.0.3) <7 5 4 3> 20 0 0x55238000 0x1b000 0x1a000 com.apple.driver.AppleIntelCPUPowerManagement (96.0.0) <7 6 5 4 3 1> 21 10 0x551af000 0x18000 0x17000 com.apple.iokit.IOStorageFamily (1.6) <7 6 5 4 3 1> 22 0 0x551c7000 0x11000 0x10000 com.apple.driver.DiskImages (281) <21 7 6 5 4 3 1> 23 0 0x552ca000 0x8000 0x7000 com.apple.nke.applicationfirewall (2.1.11) <7 6 5 4 3 1> 24 2 0x55195000 0x3000 0x2000 com.apple.kext.AppleMatch (1.0.0d1) <4 1> 25 0 0x5527d000 0x5000 0x4000 com.apple.security.quarantine (0) <24 7 6 5 4 2 1> 26 0 0x552dd000 0x8000 0x7000 com.apple.security.sandbox (0) <24 7 6 5 4 2 1> 27 0 0x551d8000 0x3000 0x2000 com.apple.security.TMSafetyNet (6) <7 6 5 4 2 1> 28 0 0x55282000 0x3000 0x2000 com.apple.driver.AppleAPIC (1.4) <4 3> 29 0 0x552d2000 0x4000 0x3000 com.apple.driver.AppleSMBIOS (1.4) <7 4 3> 30 3 0x5af57000 0x3b000 0x3a000 com.apple.iokit.IOHIDFamily (1.6.1) <7 6 5 4 3 1> 31 0 0x551a8000 0x4000 0x3000 com.apple.driver.AppleACPIButtons (1.3) <30 15 13 7 6 5 4 3 1> 32 0 0x551a5000 0x3000 0x2000 com.apple.driver.AppleHPET (1.4) <13 7 5 4 3> 33 0 0x5519d000 0x6000 0x5000 com.apple.driver.AppleRTC (1.3) <13 5 4 3 1> 34 0 0x551a3000 0x2000 0x1000 com.apple.driver.AppleACPIPS2Nub (1.0.0d1) <13 7 4 3> 35 0 0x553d2000 0x4000 0x3000 org.netkas.fakesmc (2) <13 7 4 3> 36 1 0x551ac000 0x3000 0x2000 com.apple.iokit.IOSMBusFamily (1.1) <5 4 3> 37 0 0x553dc000 0x5000 0x4000 com.apple.driver.AppleACPIEC (1.3) <36 15 13 5 4 3> 38 8 0x5b021000 0x2f000 0x2e000 com.apple.iokit.IOUSBFamily (3.8.5) <14 7 5 4 3 1> 39 0 0x553e1000 0x10000 0xf000 com.apple.driver.AppleUSBUHCI (3.7.5) <38 14 7 5 4 3 1> 40 0 0x5afeb000 0x14000 0x13000 com.apple.driver.AppleUSBEHCI (3.7.5) <38 14 7 5 4 3 1> 41 2 0x553c5000 0xd000 0xc000 com.apple.iokit.IOATAFamily (2.5.0) <5 4 3 1> 42 0 0x553f1000 0x9000 0x8000 com.apple.driver.AppleIntelPIIXATA (2.5.0) <41 14 5 4 3> 43 2 0x553fa000 0x6000 0x5000 com.apple.iokit.IOAHCIFamily (2.0.2) <5 4 3 1> 44 0 0x5afc5000 0xe000 0xd000 com.apple.driver.AppleAHCIPort (2.0.1) <43 14 5 4 3 1> 45 0 0x5afe4000 0x5000 0x4000 com.apple.driver.ApplePS2Controller (2.0.0) <5 4 3> 46 1 0x5afd3000 0x3000 0x2000 com.apple.driver.AppleEFIRuntime (1.3.0) <7 5 4 3> 47 2 0x5b13f000 0x43000 0x42000 com.apple.iokit.IOFireWireFamily (4.1.7) <5 4 3 1> 48 0 0x5b0f5000 0x26000 0x25000 com.apple.driver.AppleFWOHCI (4.4.0) <47 14 7 6 5 4 3 1> 49 0 0x5b079000 0x6000 0x5000 com.apple.driver.AppleEFINVRAM (1.3.0) <46 7 5 4 3> 50 5 0x5b11b000 0x1a000 0x19000 com.apple.iokit.IOSCSIArchitectureModelFamily (2.6.0) <5 4 3 1> 51 0 0x5b0ba000 0x5000 0x4000 com.apple.iokit.IOATAPIProtocolTransport (2.5.0) <50 41 5 4 3 1> 52 0 0x5b0de000 0x13000 0x12000 com.apple.iokit.IOAHCIBlockStorage (1.6.0) <43 21 5 4 3 1> 53 0 0x5b296000 0x3000 0x2000 com.apple.driver.XsanFilter (402.1) <21 5 4 3 1> 54 0 0x5b29f000 0x3000 0x2000 com.apple.driver.ApplePS2Keyboard (2.0.0) <30 5 4 3> 55 0 0x5b28d000 0x4000 0x3000 com.apple.driver.ApplePS2Trackpad (2.0.0) <30 5 4 3> 57 3 0x5b2a7000 0x8000 0x7000 com.apple.iokit.IOCDStorageFamily (1.6) <21 5 4 3 1> 58 2 0x5b2e7000 0x6000 0x5000 com.apple.iokit.IODVDStorageFamily (1.6) <57 21 5 4 3 1> 59 1 0x5b2fc000 0x5000 0x4000 com.apple.iokit.IOBDStorageFamily (1.6) <58 57 21 5 4 3 1> 60 0 0x5b342000 0x18000 0x17000 com.apple.iokit.IOSCSIMultimediaCommandsDevice (2.6.0) <59 58 57 50 21 5 4 3 1> 61 0 0x5b2c9000 0x7000 0x6000 com.apple.iokit.SCSITaskUserClient (2.6.0) <50 21 5 4 3 1> 62 0 0x5b285000 0x2000 0x1000 com.apple.iokit.IOUSBUserClient (3.8.5) <38 7 5 4 3 1> 63 0 0x5b330000 0xf000 0xe000 com.apple.driver.AppleUSBHub (3.8.4) <38 5 4 3 1> 64 0 0x5b2d0000 0x4000 0x3000 com.apple.driver.AppleUSBComposite (3.7.5) <38 4 3 1> 65 1 0x5b42e000 0x3d000 0x3c000 com.apple.iokit.IOBluetoothFamily (2.2.4f3) <7 5 4 3 1> 66 0 0x5b3ca000 0x8000 0x7000 com.apple.driver.AppleUSBBluetoothHCIController (2.2.4f3) <65 38 7 5 4 3> 67 0 0x5b3bd000 0xb000 0xa000 com.apple.iokit.IOUSBMassStorageClass (2.5.1) <50 38 21 5 4 3 1> 68 0 0x5b3de000 0x18000 0x17000 com.apple.iokit.IOSCSIBlockCommandsDevice (2.6.0) <50 21 5 4 3 1> 69 0 0x5b2d4000 0x3000 0x2000 com.apple.driver.AppleIntelCPUPowerManagementClient (96.0.0) <7 6 5 4 3 1> 71 0 0x5b5e9000 0x6000 0x5000 com.apple.AppleFSCompression.AppleFSCompressionTypeZlib (1.0.0d1) <6 4 3 2 1> 72 0 0x5b5ef000 0x5000 0x4000 com.apple.BootCache (31) <7 6 5 4 3 1> 73 0 0x5b7cb000 0xa000 0x9000 com.apple.filesystems.autofs (2.1.0) <7 6 5 4 3 1> 74 4 0x5b893000 0x1e000 0x1d000 com.apple.iokit.IOGraphicsFamily (2.0) <14 7 5 4 3> 75 3 0x5b7bd000 0xa000 0x9000 com.apple.driver.AppleSMC (3.0.1d2) <13 7 5 4 3> 76 0 0x5b85c000 0x17000 0x16000 com.apple.driver.AppleIntelGMAX3100FB (6.0.6) <75 74 14 13 7 5 4 3 1> 77 7 0x5b95f000 0x2c000 0x2b000 com.apple.iokit.AppleProfileFamily (41) <14 7 6 5 4 3 1> 79 1 0x5b7f2000 0xe000 0xd000 com.apple.iokit.IONDRVSupport (2.0) <74 14 7 5 4 3> 80 1 0x5b7d5000 0xb000 0xa000 com.apple.driver.IOPlatformPluginFamily (4.0.1d0) <6 5 4 3> 81 0 0x5b87a000 0xf000 0xe000 com.apple.driver.ACPI_SMC_PlatformPlugin (4.0.1d0) <80 75 14 13 7 6 5 4 3> 84 2 0x5b80b000 0x16000 0x15000 com.apple.iokit.IONetworkingFamily (1.9) <7 6 5 4 3 1> 87 0 0x5b92c000 0x9000 0x8000 com.apple.iokit.IOFireWireIP (2.0.3) <84 47 5 4 3 1> 88 0 0x55131000 0x3000 0x2000 com.apple.driver.AppleLPC (1.4.9) <14 5 4 3> 89 0 0x5ba99000 0x5b000 0x5a000 com.ZyDAS.driver.ZD1211USB (4.5.10d0) <84 38 5 4 3 1> 91 0 0x5be23000 0xc6000 0xc5000 com.apple.driver.AppleIntelGMAX3100 (6.0.6) <79 74 14 7 5 4 3 1> 92 0 0x5b2be000 0x5000 0x4000 com.apple.driver.AppleUpstreamUserClient (3.1.0) <74 14 13 7 5 4 3 1> 93 1 0x5afe0000 0x4000 0x3000 com.apple.kext.OSvKernDSPLib (1.3) <5 4> 94 2 0x5ba5d000 0x18000 0x17000 com.apple.iokit.IOAudioFamily (1.7.2fc1) <93 5 4 3 1> 95 0 0x5bbf4000 0x1f000 0x1e000 org.voodoo.driver.VoodooHDA (0.2.54) <94 14 7 5 4 3> 96 0 0x5b718000 0x4000 0x3000 com.apple.driver.AudioIPCDriver (1.1.2) <94 5 4 3 1> 97 0 0x5b84a000 0x7000 0x6000 com.apple.driver.AppleIntelPenrynProfile (17) <77 6 4 3> 98 0 0x5ba47000 0x6000 0x5000 com.apple.Dont_Steal_Mac_OS_X (7.0.0) <75 7 4 3 1> 100 1 0x5ba4d000 0x9000 0x8000 com.apple.iokit.IOSerialFamily (10.0.3) <7 6 5 4 3 1> 101 0 0x5bc1f000 0x9000 0x8000 com.apple.iokit.IOBluetoothSerialManager (2.2.4f3) <100 7 5 4 3 1> 102 0 0x5bd8c000 0xb000 0xa000 com.apple.iokit.IOSurface (73.0) <7 5 4 3 1> 103 0 0x5b76d000 0x3000 0x2000 com.x86dev.driver.lspcidrv (1.0) <11 10> 105 0 0x5ba42000 0x3000 0x2000 com.manycamllc.driver.ManyCamDriver (0.0.9) <11 10> 106 0 0x54e4a000 0x3000 0x2000 com.apple.driver.AppleProfileCallstackAction (20) <77 5 4 3 1> 108 0 0x54e23000 0x3000 0x2000 com.apple.driver.AppleProfileKEventAction (10) <77 4 3 1> 110 0 0x54e26000 0x3000 0x2000 com.apple.driver.AppleProfileRegisterStateAction (10) <77 4 3 1> 111 0 0x54e38000 0x3000 0x2000 com.apple.driver.AppleProfileThreadInfoAction (14) <77 6 4 3 1> 112 0 0x54e41000 0x3000 0x2000 com.apple.driver.AppleProfileTimestampAction (10) <77 5 4 3 1> 113 0 0x54e1e000 0x3000 0x2000 com.apple.driver.AppleProfileReadCounterAction (17) <77 6 4 3> 114 0 0x5bc33000 0x38000 0x37000 com.paragon-software.filesystems.ntfs (82) <7 5 4 1> 115 0 0x73142000 0x3000 0x2000 com.bresink.driver.BRESINKx86Monitoring (7.0) <12 11 10> 118 0 0x5b2b9000 0x4000 0x3000 com.mojodojo.driver.CPUi (1.0.6b1) <7 5 4 3> 119 0 0x5b6db000 0x3000 0x2000 info.olofsson.driver.CMSRToolsDriver (1.0.1d1) <5 4 3 1> Youl notice I have all the apple vanilla kext loaded that I need just missing pstate values to make it all work. Hope you can help me.. Link to comment Share on other sites More sharing options...
kdawg Posted June 29, 2010 Share Posted June 29, 2010 OK thanks.. I added this as is to my DSDT replacing what I had and I get 15 errors.. I am wondering if this is going to work for me after reading that Thinkpad T60 owners go about getting speedstep to work completely differently then the formerlyknownas method... See here: http://forum.thinkpads.com/viewtopic.php?f=32&t=85344 Youl notice I have all the apple vanilla kext loaded that I need just missing pstate values to make it all work. Hope you can help me.. When you say errors are they compile errors from your DSDT? Or boot errors? Link to comment Share on other sites More sharing options...
00diabolic Posted June 29, 2010 Share Posted June 29, 2010 When you say errors are they compile errors from your DSDT? Or boot errors? compile errors in DSDTSE sorry Link to comment Share on other sites More sharing options...
kdawg Posted June 29, 2010 Share Posted June 29, 2010 compile errors in DSDTSE sorry Ok you'll need to post your DSDT and the compile log. Link to comment Share on other sites More sharing options...
Recommended Posts