Jump to content

DSDT - Vanilla Speedstep - Generic Scope (_PR)

FKA

By FKA,
in Power Management

 Share
1949 posts in this topic

Recommended Posts

FKA
FKA
Posted
  • Author
Posted
Hi to all. I have a question. My bios (p5q deluxe) has only this option for cstate: C1E The processor is a Q9400

 

Facp table: _CST Support : E3

C2 Latency : 0065

C3 Latency : 03E9

 

So, what cstate support my mobo? Only c1?

 

Thank you!

 

yes just C1

valv
valv
Posted
Posted
One other question. Is it nuts to think I might be able to use a real macs DSDT.aml on my system? Do you think it would be catastrophic to try?
Yes it is, u 'd not even be able to boot.

Greetz

00diabolic
00diabolic
Posted
Posted

Ok got a question.. I'm either really lucky or just missing something here. Please help me understand this stroke of good luck.

 

I have been able to remove the following kext from extra/extentions without doing the relevant DSDT fixes. Heres the list.

 

Nullcpupowermanagement.kext = Maybe its because I have vanilla kernal and system matches macbook 4,1 Is that enough to run native appleintelcpupowermgmt? Or would normally a DSDT fix be required for this?

 

IOATAfamily.kext modded by slice for 10.6.2. I replaced it with 10.6.2 vanilla and it just worked. No need to apply the kings DSDT patch that I found but could not seem to adapt to my system so I took a chance without it and it worked. How on earth is this possible? Could my DSDT be that good as is?

 

LegacyappleAHCIport.kext I simply dont need it anymore. Amazing.

 

Now the next on my list is voodoopowermini.kext but as we speak I am looking at voodoomonitor and I am seeing my CPU clock from a 6x to a 12.5x multipliers only. Nothing like it was before nullcpupowermagement was in place. I had it clocking as low as 3x = 600mhz. At 6x its at 1200mhz lowest point. Is voodoopowermini even being used right now? It is just for speedstep right (voodoopower)? If its not then that means my DSDT has 2 p-states already and all I have to do is add a few more. Right? Voodoomonitor shows 19 p-states. Is that what is read from my CPU?

 

Please help clear this up. I'm beside myself right now. I would really like to get a understanding of all of this.

 

Also I'm betting its impossible but are there DSDT fixes for getting rid of the following kext? Just tell me not at this time. Ive googled and I know its off topic but would be nice to hear someone say so that really knows.

 

VoodooBattery

fakeSmC

appleacpips2nub

appleps2controller

 

My system is almost vanilla.. THANKS Formerlyknownas!!!!!!!!

FKA
FKA
Posted
  • Author
Posted
moved and compiled without problems mate.

http://dl.dropbox.com/u/363153/method_moved_dsdt.dsl

 

but still the damn kp without null.

 

smbios: http://pastie.org/1019582

com.apple.boot.plist http://pastie.org/1019583

 

you are using rc4-aserebln-1.1.9 bootloader -

 

I presume you are taking this into account :-

 

  • Filenames configured in com.apple.Boot.plist (DSDT=..., SMBIOS=...) must be given with the full path. The Booter does not check automatically the Extra Folder. So if you used DSDT=mydsdt.aml and the mydsdt.aml file is in the Extra folder, then you must use now DSDT=/Extra/mydsdt.aml.

D

 

Nullcpupowermanagement.kext = Maybe its because I have vanilla kernal and system matches macbook 4,1 Is that enough to run native appleintelcpupowermgmt? Or would normally a DSDT fix be required for this?

 

simply loading the DSDT will allow you to boot and update without nullcpu kext.

 

As far as the others go, I'm not sure but would definatly check you cleared caches since you removed them.

 

snow lepoard cache cleaner is very handy tool!

 

D

00diabolic
00diabolic
Posted
Posted
simply loading the DSDT will allow you to boot and update without nullcpu kext.

 

As far as the others go, I'm not sure but would definatly check you cleared caches since you removed them.

 

snow lepoard cache cleaner is very handy tool!

 

D

 

Ohh yeah I have updated my cache. I used Kext utility for that. That is the first thing I did and I held my breath as I did it and rebooted. All seems fine. I also just got rid of voodoopowermini and appleintelcpupowermgmt is loaded. Thats vanilla speedstep right?

 

Take a look at this..

Index Refs Address	Size	   Wired	  Name (Version) <Linked Against>
  13   12 0x54f41000 0x4000	 0x3000	 com.apple.iokit.IOACPIFamily (1.3.0) <7 6 4 3>
  14   16 0x55133000 0x11000	0x10000	com.apple.iokit.IOPCIFamily (2.6) <7 5 4 3>
  15	2 0x551d3000 0x41000	0x40000	com.apple.driver.AppleACPIPlatform (1.3) <14 13 7 6 5 4 3>
  16	0 0x54f95000 0x5000	 0x4000	 com.superhai.driver.VoodooBattery (1.3.3) <13 5 4 3>
  17	0 0x54fa5000 0x4000	 0x3000	 com.mojodojo.driver.VoodooMonitor (1.1.1d1) <7 5 4 3>
  18	0 0x551a8000 0x1b000	0x1a000	com.apple.driver.AppleIntelCPUPowerManagement (96.0.0) <7 6 5 4 3 1> SEE!!!!!!!!!!!!
  19   10 0x55265000 0x18000	0x17000	com.apple.iokit.IOStorageFamily (1.6) <7 6 5 4 3 1>
  20	0 0x55197000 0x11000	0x10000	com.apple.driver.DiskImages (281) <19 7 6 5 4 3 1>
  21	0 0x552bf000 0x8000	 0x7000	 com.apple.nke.applicationfirewall (2.1.11) <7 6 5 4 3 1>
  22	2 0x5516c000 0x3000	 0x2000	 com.apple.kext.AppleMatch (1.0.0d1) <4 1>
  23	0 0x55254000 0x5000	 0x4000	 com.apple.security.quarantine (0) <22 7 6 5 4 2 1>
  24	0 0x552c7000 0x8000	 0x7000	 com.apple.security.sandbox (0) <22 7 6 5 4 2 1>
  25	0 0x551cd000 0x3000	 0x2000	 com.apple.security.TMSafetyNet (6) <7 6 5 4 2 1>
  26	0 0x551c3000 0x3000	 0x2000	 com.apple.driver.AppleAPIC (1.4) <4 3>
  27	0 0x55259000 0x4000	 0x3000	 com.apple.driver.AppleSMBIOS (1.4) <7 4 3>
  28	3 0x5af31000 0x3b000	0x3a000	com.apple.iokit.IOHIDFamily (1.6.1) <7 6 5 4 3 1>
  29	0 0x55190000 0x4000	 0x3000	 com.apple.driver.AppleACPIButtons (1.3) <28 15 13 7 6 5 4 3 1>
  30	0 0x5518d000 0x3000	 0x2000	 com.apple.driver.AppleHPET (1.4) <13 7 5 4 3>
  31	0 0x553ad000 0x6000	 0x5000	 com.apple.driver.AppleRTC (1.3) <13 5 4 3 1>
  32	0 0x55194000 0x2000	 0x1000	 com.apple.driver.AppleACPIPS2Nub (1.0.0d1) <13 7 4 3>
  33	0 0x55372000 0x4000	 0x3000	 org.netkas.fakesmc (2) <13 7 4 3>
  34	1 0x551d0000 0x3000	 0x2000	 com.apple.driver.AppleEFIRuntime (1.3.0) <7 5 4 3>
  35	8 0x5b039000 0x2f000	0x2e000	com.apple.iokit.IOUSBFamily (3.8.5) <14 7 5 4 3 1>
  36	0 0x5affd000 0x10000	0xf000	 com.apple.driver.AppleUSBUHCI (3.7.5) <35 14 7 5 4 3 1>
  37	1 0x553b3000 0x3000	 0x2000	 com.apple.iokit.IOSMBusFamily (1.1) <5 4 3>
  38	0 0x5afdd000 0x5000	 0x4000	 com.apple.driver.AppleACPIEC (1.3) <37 15 13 5 4 3>
  39	0 0x5b091000 0x14000	0x13000	com.apple.driver.AppleUSBEHCI (3.7.5) <35 14 7 5 4 3 1>
  40	0 0x5b00d000 0x5000	 0x4000	 com.apple.driver.ApplePS2Controller (2.0.0) <5 4 3>
  41	0 0x5b01b000 0x6000	 0x5000	 com.apple.driver.AppleEFINVRAM (1.3.0) <34 7 5 4 3>
  42	2 0x5afeb000 0xd000	 0xc000	 com.apple.iokit.IOATAFamily (2.5.0) <5 4 3 1>
  43	0 0x5b0bd000 0x9000	 0x8000	 com.apple.driver.AppleIntelPIIXATA (2.5.0) <42 14 5 4 3>
  44	2 0x5b158000 0x43000	0x42000	com.apple.iokit.IOFireWireFamily (4.1.7) <5 4 3 1>
  45	0 0x5b10e000 0x26000	0x25000	com.apple.driver.AppleFWOHCI (4.4.0) <44 14 7 6 5 4 3 1>
  46	2 0x5b0b6000 0x6000	 0x5000	 com.apple.iokit.IOAHCIFamily (2.0.2) <5 4 3 1>
  47	0 0x5b0a5000 0xe000	 0xd000	 com.apple.driver.AppleAHCIPort (2.0.1) <46 14 5 4 3 1>
  48	5 0x5b0d1000 0x1a000	0x19000	com.apple.iokit.IOSCSIArchitectureModelFamily (2.6.0) <5 4 3 1>
  49	0 0x5b105000 0x5000	 0x4000	 com.apple.iokit.IOATAPIProtocolTransport (2.5.0) <48 42 5 4 3 1>
  50	0 0x553fd000 0x3000	 0x2000	 com.apple.driver.ApplePS2Keyboard (2.0.0) <28 5 4 3>
  51	0 0x5b10a000 0x4000	 0x3000	 com.apple.driver.ApplePS2Trackpad (2.0.0) <28 5 4 3>
  53	0 0x5b25f000 0x13000	0x12000	com.apple.iokit.IOAHCIBlockStorage (1.6.0) <46 19 5 4 3 1>
  54	0 0x5b2a2000 0x3000	 0x2000	 com.apple.driver.XsanFilter (402.1) <19 5 4 3 1>
  55	3 0x5b2bd000 0x8000	 0x7000	 com.apple.iokit.IOCDStorageFamily (1.6) <19 5 4 3 1>
  56	2 0x5b2f5000 0x6000	 0x5000	 com.apple.iokit.IODVDStorageFamily (1.6) <55 19 5 4 3 1>
  57	1 0x5b30a000 0x5000	 0x4000	 com.apple.iokit.IOBDStorageFamily (1.6) <56 55 19 5 4 3 1>
  58	0 0x5b350000 0x18000	0x17000	com.apple.iokit.IOSCSIMultimediaCommandsDevice (2.6.0) <57 56 55 48 19 5 4 3 1>
  59	0 0x5b2d7000 0x7000	 0x6000	 com.apple.iokit.SCSITaskUserClient (2.6.0) <48 19 5 4 3 1>
  60	0 0x5b2a5000 0x2000	 0x1000	 com.apple.iokit.IOUSBUserClient (3.8.5) <35 7 5 4 3 1>
  61	0 0x5b33e000 0xf000	 0xe000	 com.apple.driver.AppleUSBHub (3.8.4) <35 5 4 3 1>
  62	0 0x5b323000 0x4000	 0x3000	 com.apple.driver.AppleUSBComposite (3.7.5) <35 4 3 1>
  63	1 0x5b416000 0x3d000	0x3c000	com.apple.iokit.IOBluetoothFamily (2.2.4f3) <7 5 4 3 1>
  64	0 0x5b3b2000 0x8000	 0x7000	 com.apple.driver.AppleUSBBluetoothHCIController (2.2.4f3) <63 35 7 5 4 3>
  65	0 0x5b3e2000 0xb000	 0xa000	 com.apple.iokit.IOUSBMassStorageClass (2.5.1) <48 35 19 5 4 3 1>
  66	0 0x5b3c6000 0x18000	0x17000	com.apple.iokit.IOSCSIBlockCommandsDevice (2.6.0) <48 19 5 4 3 1>
  67	0 0x5b34d000 0x3000	 0x2000	 com.apple.driver.AppleIntelCPUPowerManagementClient (96.0.0) <7 6 5 4 3 1>
  69	0 0x5b489000 0x6000	 0x5000	 com.apple.AppleFSCompression.AppleFSCompressionTypeZlib (1.0.0d1) <6 4 3 2 1>
  70	0 0x5b5e6000 0x5000	 0x4000	 com.apple.BootCache (31) <7 6 5 4 3 1>
  71	0 0x5b803000 0xa000	 0x9000	 com.apple.filesystems.autofs (2.1.0) <7 6 5 4 3 1>
  72	2 0x5b85b000 0x16000	0x15000	com.apple.iokit.IONetworkingFamily (1.9) <7 6 5 4 3 1>
  73	0 0x5b7f5000 0x9000	 0x8000	 com.apple.iokit.IOFireWireIP (2.0.3) <72 44 5 4 3 1>
  74	0 0x5b6fc000 0x3000	 0x2000	 com.apple.driver.AppleLPC (1.4.9) <14 5 4 3>
  75	1 0x5b89b000 0xb000	 0xa000	 com.apple.driver.IOPlatformPluginFamily (4.0.1d0) <6 5 4 3>
  76	3 0x5b8b1000 0xa000	 0x9000	 com.apple.driver.AppleSMC (3.0.1d2) <13 7 5 4 3>
  77	0 0x5b8c6000 0xf000	 0xe000	 com.apple.driver.ACPI_SMC_PlatformPlugin (4.0.1d0) <76 75 14 13 7 6 5 4 3>
  79	4 0x5b820000 0x1e000	0x1d000	com.apple.iokit.IOGraphicsFamily (2.0) <14 7 5 4 3>
  81	7 0x5ba10000 0x2c000	0x2b000	com.apple.iokit.AppleProfileFamily (41) <14 7 6 5 4 3 1>
  85	1 0x5b93a000 0xe000	 0xd000	 com.apple.iokit.IONDRVSupport (2.0) <79 14 7 5 4 3>
  86	0 0x5b9e2000 0x17000	0x16000	com.apple.driver.AppleIntelGMAX3100FB (6.0.6) <79 76 14 13 7 5 4 3 1>
  87	0 0x5bb25000 0x5b000	0x5a000	com.ZyDAS.driver.ZD1211USB (4.5.10d0) <72 35 5 4 3 1>
  88	1 0x5aff9000 0x4000	 0x3000	 com.apple.kext.OSvKernDSPLib (1.3) <5 4>
  89	2 0x5b9bd000 0x18000	0x17000	com.apple.iokit.IOAudioFamily (1.7.2fc1) <88 5 4 3 1>
  90	0 0x5bafe000 0x1f000	0x1e000	org.voodoo.driver.VoodooHDA (0.2.54) <89 14 7 5 4 3>
  91	0 0x5b789000 0x4000	 0x3000	 com.apple.driver.AudioIPCDriver (1.1.2) <89 5 4 3 1>
  93	0 0x5b7fe000 0x5000	 0x4000	 com.apple.driver.AppleUpstreamUserClient (3.1.0) <79 14 13 7 5 4 3 1>
  94	0 0x5be6e000 0xc6000	0xc5000	com.apple.driver.AppleIntelGMAX3100 (6.0.6) <85 79 14 7 5 4 3 1>
  96	0 0x5b2d1000 0x6000	 0x5000	 com.apple.Dont_Steal_Mac_OS_X (7.0.0) <76 7 4 3 1>
  97	0 0x5b9d5000 0x7000	 0x6000	 com.apple.driver.AppleIntelPenrynProfile (17) <81 6 4 3>
  98	1 0x5bbc0000 0x9000	 0x8000	 com.apple.iokit.IOSerialFamily (10.0.3) <7 6 5 4 3 1>
  99	0 0x5bbd5000 0x9000	 0x8000	 com.apple.iokit.IOBluetoothSerialManager (2.2.4f3) <98 7 5 4 3 1>
 101	0 0x5bacd000 0xb000	 0xa000	 com.apple.iokit.IOSurface (73.0) <7 5 4 3 1>
 102	0 0x5b76a000 0x3000	 0x2000	 com.x86dev.driver.lspcidrv (1.0) <11 10>
 103	0 0x5babe000 0x3000	 0x2000	 com.manycamllc.driver.ManyCamDriver (0.0.9) <11 10>
 104	0 0x5bab3000 0x3000	 0x2000	 com.apple.driver.AppleProfileCallstackAction (20) <81 5 4 3 1>
 105	0 0x54e14000 0x3000	 0x2000	 com.apple.driver.AppleProfileKEventAction (10) <81 4 3 1>
 106	0 0x54dfc000 0x3000	 0x2000	 com.apple.driver.AppleProfileRegisterStateAction (10) <81 4 3 1>
 108	0 0x54df8000 0x3000	 0x2000	 com.apple.driver.AppleProfileThreadInfoAction (14) <81 6 4 3 1>
 110	0 0x54e33000 0x3000	 0x2000	 com.apple.driver.AppleProfileTimestampAction (10) <81 5 4 3 1>
 111	0 0x54e2c000 0x3000	 0x2000	 com.apple.driver.AppleProfileReadCounterAction (17) <81 6 4 3>
 112	0 0x72eb4000 0x38000	0x37000	com.paragon-software.filesystems.ntfs (82) <7 5 4 1>
 113	1 0x5b975000 0x9000	 0x8000	 com.apple.filesystems.cd9660 (1.4.0) <7 6 5 4 3 1>
 114	0 0x5b937000 0x3000	 0x2000	 com.bresink.driver.BRESINKx86Monitoring (7.0) <12 11 10>

 

 

I did all of this without adding a single thing related to speedstep to my DSDT. Am I just lucky or what? I added my DSDT if you want to take a look at it.

 

So all I have to do is add it some more p-states to get a few more clocks to my CPU right since it does not match a mac CPU exactly. I'm also wondering now if voodoomonitor is not giving me correct info because it does not read apple speedstep or does it. What app can I use to see if its clocking? Maybe I dont have to add anything to my DSDT at all.

 

Let me know.. This is exciting..

dsdt.zip

FKA
FKA
Posted
  • Author
Posted
I did all of this without adding a single thing related to speedstep to my DSDT. Am I just lucky or what? I added my DSDT if you want to take a look at it.

 

So all I have to do is add it some more p-states to get a few more clocks to my CPU right since it does not match a mac CPU exactly. I'm also wondering now if voodoomonitor is not giving me correct info because it does not read apple speedstep or does it. What app can I use to see if its clocking? Maybe I dont have to add anything to my DSDT at all.

 

Let me know.. This is exciting..

 

if you cpu is changing p-states using whatever method - voodoomonitor will show this.

If voodoomonitor is not showing changes then appleICPUPM may be loading but it isn't working!

 

with my MSI board I am also very lucky as p-states are working natively for me.

AppleLPC was also loading natively up until 10.6.4 - but I now have to inject device id (this may not be related to 10.6.4 as I've been messing around with some other things ... much check this!!)

 

I have to inject cst data or I get cst related errors at boot.

 

Although my cpu isn't native Apple, voodoomonitor shows I have correct FiD and Vid values - probably advisable for me to actually bother to add _pss data but I haven and all seems ok for me!

 

In short - if you're not seeing changes in voodoomonitor, appleICPUPM aint working and you'll have to make the nessesary edits to your DSDT.

 

Great news on the other benefits from loading DSDT!!

 

:(

 

EDIT - what model id do you use - MacBookPro 4,1 or macBook 4,1 ??

00diabolic
00diabolic
Posted
Posted
Great news on the other benefits from loading DSDT!!

 

:)

 

EDIT - what model id do you use - MacBookPro 4,1 or macBook 4,1 ??

 

I am using MacBook4,1 as its like a 90% match to that system. The sound chip and like CPU are the only differences I think. I'm still a bit of a noob with this stuff but catching on quickly.

 

Looks like I gotta add just more p-states is all I have what looks like 2 that work now. VoodooMonitor shows my cpu clocking from 1200-2500mhz and nothing in between or below that. So it looks like I just need to add a few more. On your guide you add only 3. Can I add as many as I want? I think 4-5 would be good.

 

Also on the p-states tab in voodoomonitor I see 19 p-states. Are those all that the CPU can support? Also its odd but on the p-states tab it goes upto a multiplier of 13.5 but my max multipler is 12.5. Where is that information coming from? Is that from the DSDT or read from the CPU (cant be)? Any idea why it has the 13.5 in there?

 

VID = voltage identifier and FID is freq identifier right?

 

How do I see if I have CST errors.. I dont see them in console, I searched. Is there another place?

 

Thanks

FKA
FKA
Posted
  • Author
Posted
I am using MacBook4,1 as its like a 90% match to that system. The sound chip and like CPU are the only differences I think. I'm still a bit of a noob with this stuff but catching on quickly.

 

Looks like I gotta add just more p-states is all I have what looks like 2 that work now. VoodooMonitor shows my cpu clocking from 1200-2500mhz and nothing in between or below that. So it looks like I just need to add a few more. On your guide you add only 3. Can I add as many as I want? I think 4-5 would be good.

 

 

VID = voltage identifier and FID is freq identifier right?

 

How do I see if I have CST errors.. I dont see them in console, I searched. Is there another place?

 

Thanks

 

correct on FiD and Vid you should see them both change in voodoomonitor.

 

You should try MacBookPro4,1 as model id as it has the same cpu as you. Try this before you add _pss values to DSDT.

 

Also on the p-states tab in voodoomonitor I see 19 p-states. Are those all that the CPU can support? Also its odd but on the p-states tab it goes upto a multiplier of 13.5 but my max multipler is 12.5. Where is that information coming from? Is that from the DSDT or read from the CPU (cant be)? Any idea why it has the 13.5 in there?

 

your p-states aren't working properly at the moment so don't trust what you see in voodoomonitor.

And check CPU specks to find out how many p-states you should have.

mm67
mm67
Posted
Posted
@mm67

 

Were you ever able to get C1E, C2E and C4E to work?

 

Check out this guys post.

 

He suggests patching ACPI_SMC_PlatformPlugin to get C-States working.

 

Defining method CST like this does seem to enable lower C-states:

		Method (CST, 0, NotSerialized)
	{
		Return (Package (0x4)
		{
			0x3, 
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x000,0x0,)},One,One,0x3E8}, 
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x010,0x1,)},0x2,One,0x1F4}, 
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x030,0x3,)},0x4,0x39,0x64}, 
		})
	}

 

Before I was able to see that temps dropped 1-2 degrees with C4 working but my current cpu cooler is so good that I really don't see any difference in temps anymore, idling temps look like this:

post-375259-1277578604_thumb.png

 

And that's running with only C1E and cpu overclocked to 3.91 GHz. That's pretty much as low as temps can get considering that ambient temperature is about 24. Can't really get cooler than ambient using air cooling.

kdawg
kdawg
Posted
Posted
Before I was able to see that temps dropped 1-2 degrees with C4 working but my current cpu cooler is so good that I really don't see any difference in temps anymore, idling temps look like...

 

 

Out of curiosity how did you come about this CST setup?

		Method (CST, 0, NotSerialized)
	{
		Return (Package (0x4)
		{
			0x3, 
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x000,0x0,)},[color="#FF0000"]One[/color],One,0x3E8}, 
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x010,0x1,)},[color="#FF0000"]0x2[/color],One,0x1F4}, 
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x030,0x3,)},[color="#FF0000"]0x4[/color],0x39,0x64}, 
		})
	}

 

Also are the values in red the actual C state number? I was under the assumption It should go sequentially 1-3 regardless of what C-State. I also assume you have defined here C1, C2 and C4.

mm67
mm67
Posted
Posted
Out of curiosity how did you come about this CST setup?

		Method (CST, 0, NotSerialized)
	{
		Return (Package (0x4)
		{
			0x3, 
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x000,0x0,)},[color="#FF0000"]One[/color],One,0x3E8}, 
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x010,0x1,)},[color="#FF0000"]0x2[/color],One,0x1F4}, 
			Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x030,0x3,)},[color="#FF0000"]0x4[/color],0x39,0x64}, 
		})
	}

 

Also are the values in red the actual C state number? I was under the assumption It should go sequentially 1-3 regardless of what C-State. I also assume you have defined here C1, C2 and C4.

 

That's pretty much an exact replica of my MSI board's CST, only change is that number 4 on C4 definition, on MSI that was numbered as 3 even though it is defining C4. Using 3 just won't trigger C4, I got the idea to define it with actual state number from MacPro 4,1 SSDT, there C-states are also defined with real state numbers.

keeza
keeza
Posted
Posted
I actually upgraded to a Q9550 and was wondering if you managed to make any progress.

Different time zone, what a bummer! Since been covered but here's my findings:

This is what I use:

	Scope (_PR)
  {
	  Name (PSS, Package (0x06)   // <--- Number of P-States as counted below
	  {
		  Package (0x06){Zero,Zero,0x0A,0x0A,0x4820,Zero},
		  Package (0x06){Zero,Zero,0x0A,0x0A,0x081E,One},
		  Package (0x06){Zero,Zero,0x0A,0x0A,0x471C,0x02},
		  Package (0x06){Zero,Zero,0x0A,0x0A,0x071A,0x03},
		  Package (0x06){Zero,Zero,0x0A,0x0A,0x4618,0x04},
		  Package (0x06){Zero,Zero,0x0A,0x0A,0x0616,0x05}
	  })

	  Name (PSD, Package (0x05)
	  {0x05,Zero,Zero,0xFC,0x04})

	  Name (CST, Package (0x05)
	  {
		  0x04,   //<--number of C-States C1,C2,C4
		  Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x000,0x1,)},One,One,0x3E8},	 //<--C!E
		  Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x010,0x1,)},0x2,0x01,0x1F4},	//<--C2E
		  Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x020,0x3,)},0x3,0x55,0xFA},	//<--C3 N/A
		  Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x030,0x3,)},0x4,0x96,0x64}	  //<--C4E
	  })

 

I use FFixedHW addresses to declare CStates - SystemIO addresses simply don't work for me. My opinion is that SystemIO addresses result in CState parity i.e. C1 only.

 

Use 4 for C4 (not 3, 3 didn't work). CState number must equal actual CState i.e. C2=2 etc.

 

Is your Q9550 the E0 revision? This is the one that supports C4.

 

Edit:

Legacy Kext Removed

00diabolic
00diabolic
Posted
Posted
correct on FiD and Vid you should see them both change in voodoomonitor.

 

You should try MacBookPro4,1 as model id as it has the same cpu as you. Try this before you add _pss values to DSDT.

 

Holly {censored} i never saw this before but i found a MacBookPro 4,1 with my exact cpu the t9300. I thought the closest I could get was a t8300. Both the macbook 4,1 and pro have that.

 

http://www.everymac.com/ultimate-mac-looku...s=MacBookPro4,1

 

Anyway now the only difference between

 

the macbook 4,1 and my system is the CPU and sound.

 

& the Macbookpro 4,1 is the Sound and Video card.

 

So I'm guessing it does not matter if my video matches right? I thought matching the video was a good idea as video can be so troublesome when updating. Please let me know...

 

Thanks

00D

 

Update I went ahead with switching the model to a MacBookPro4,1 and it seems to run good. So I guess matching video is of no concern. I still would like confirmation on that. Anyway it does not seem to give me the p-states I was hoping for even though there is a Macbookpro4,1 with my exact CPU. See link above.

 

So here is what I see in voodoomonitor

 

CPU0 800Mhz x4.0 1,000v

CPU1 800Mhz x4.0 1,000v

 

Its as if I have no p-states at all and its defaulted to the lowest or something. So same problem as using MacBook4,1. I will attempt to stumble through this with your guide but is there anything else I need to do to besides adding p-states to my DSDT? Is there an alternative perhaps? I'll keep looking. Seems like even though I have the same CPU as the MacBookPro4,1 its not seeing that and applying the proper speedstep to my CPU. Should I edit my system info to better help ID my cpu?

 

Also I read in this thread around post 79 Masterchef help a guy with a t9300 Dell but I cant figure out if that CST table issue is my problem or not.

post-155458-1277615776_thumb.png

dsdt.zip

kdawg
kdawg
Posted
Posted
Different time zone, what a bummer! Since been covered but here's my findings:

This is what I use...

So you use the CST patch in conjunction with the legacy kext? My understanding is that unsupported processors OSX won't natively support C-states unless you add support for them with the legacy kext.

 

Thanks for the tip.

keeza
keeza
Posted
Posted
So you use the CST patch in conjunction with the legacy kext? My understanding is that unsupported processors OSX won't natively support C-states unless you add support for them with the legacy kext.

 

Thanks for the tip.

I use just CST in DSDT - Legacy kext either didn't work or made no difference as its only injecting macpro3,1 data anyway.

 

I'm running cool and stable. :wacko:

kdawg
kdawg
Posted
Posted
There also seems to be some E0 chips that don't do C2E: http://www.chiplist.com/Intel_Core_2_Quad_...section--2401-/

Look at that! I have SLB8V so says the box. So it appears I only have C1 and C4? Ill have to move over to windows and see what CPU-Z says. Which ones do you guys have?

 

I imagine if my CPU didnt support C2 then it wouldnt show up in the BIOS as an option. Would you agree?

mm67
mm67
Posted
Posted
Look at that! I have SLB8V so says the box. So it appears I only have C1 and C4? Ill have to move over to windows and see what CPU-Z says. Which ones do you guys have?

 

I also have SLB8V, then there is also this Intel datasheet : http://download.intel.com/design/processor...updt/318727.pdf . That one says that we have C1E, C3E and C4E but it says nothing about C2E. Don't know what to think.

Smith@@™
Smith@@™
Posted
Posted
Different time zone, what a bummer! Since been covered but here's my findings:

This is what I use:

	Scope (_PR)
 {
	 Name (PSS, Package (0x06)   // <--- Number of P-States as counted below
	 {
		 Package (0x06){Zero,Zero,0x0A,0x0A,0x4820,Zero},
		 Package (0x06){Zero,Zero,0x0A,0x0A,0x081E,One},
		 Package (0x06){Zero,Zero,0x0A,0x0A,0x471C,0x02},
		 Package (0x06){Zero,Zero,0x0A,0x0A,0x071A,0x03},
		 Package (0x06){Zero,Zero,0x0A,0x0A,0x4618,0x04},
		 Package (0x06){Zero,Zero,0x0A,0x0A,0x0616,0x05}
	 })

	 Name (PSD, Package (0x05)
	 {0x05,Zero,Zero,0xFC,0x04})

	 Name (CST, Package (0x05)
	 {
		 0x04,   //<--number of C-States C1,C2,C4
		 Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x000,0x1,)},One,One,0x3E8},	 //<--C!E
		 Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x010,0x1,)},0x2,0x01,0x1F4},	//<--C2E
		 Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x020,0x3,)},0x3,0x55,0xFA},	//<--C3 N/A
		 Package (0x4){ResourceTemplate (){Register (FFixedHW,0x01,0x02,0x030,0x3,)},0x4,0x96,0x64}	  //<--C4E
	 })

 

I use FFixedHW addresses to declare CStates - SystemIO addresses simply don't work for me. My opinion is that SystemIO addresses result in CState parity i.e. C1 only.

 

Use 4 for C4 (not 3, 3 didn't work). CState number must equal actual CState i.e. C2=2 etc.

 

Is your Q9550 the E0 revision? This is the one that supports C4.

 

Here's my leagacy kext - my first one so any feedback appreciated.

 

But i don't understand, this is the problem that i wrote some post ago. What is the difference? You are inserting with legacy the same parameters or no? I would say that i don't see the difference except the change to MacPro3,2 obviously.

If you see voodoomonitor, the voltages drop together pstates? Or voltages remain always the higher value?

 

Because otherwise i don't see the difference.

 

 

Ti conosco capire smith@@

 

I really do not like football but at this point i feel the need to say I'm sorry for Italy ...

if it's any help ... i very much doubt England will beat the German football machine :P

 

D

 

Oh ;) my friend! My italy played as a team of amateurs. Chiellini is the defensor more poor that i have seen ever play, in absolute. And not only him. I was very disappointed after 2006 and I still have not completely disposed of anger. By the way... uffff

Enough for me that the world will not be defeated from France (already out, i'm enjoying, i hate France), the Germany ( I hate Germany--grosso, del piero-2006), and Brazil (a world cup than Italy): footballing talking, obviously.

 

This is it... :)

 

Common Capello!

 

:)

kdawg
kdawg
Posted
Posted
But i don't understand, this is the problem that i wrote some post ago. What is the difference? You are inserting with legacy the same parameters or no? I would say that i don't see the difference except the change to MacPro3,2 obviously.

If you see voodoomonitor, the voltages drop together pstates? Or voltages remain always the higher value?

 

Because otherwise i don't see the difference.

After running a quick initial test using Keeza's DSDT patch, the voltage now is locked at maximum while my P states work normally. I need to run a few more tests to determine what happened. Using the CST from my earlier post C and P states seemed to work well even when overclocked.

mm67
mm67
Posted
Posted
After running a quick initial test using Keeza's DSDT patch, the voltage now is locked at maximum while my P states work normally. I need to run a few more tests to determine what happened. Using the CST from my earlier post C and P states seemed to work well even when overclocked.

 

How are you monitoring the voltage ? VoodooMonitor does not show Vcore changes, mark-i and iStat with new Fakesmc will show the real Vcore that changes when C-states are working.

Smith@@™
Smith@@™
Posted
Posted
After running a quick initial test using Keeza's DSDT patch, the voltage now is locked at maximum while my P states work normally. I need to run a few more tests to determine what happened. Using the CST from my earlier post C and P states seemed to work well even when overclocked.

 

Ok, hence the problem about voltage could be given from cstate code?

 

Another thing, but what is the advantage of using a legacy here, having to still enter the cstate code in the DSDT ?

 

Thanks

 

 

How are you monitoring the voltage ? VoodooMonitor does not show Vcore changes, mark-i and iStat with new Fakesmc will show the real Vcore that changes when C-states are working.

 

voodoomonitor show me the vcore changes. istamenu with new fakesmc with plugin (rev 250) show me always the vcore higher (1,32v) like in bios.

 

How do you do to see in voodoomonitor not vcore changes and in istat the drop of vcore together pstates? For me is completely the opposite.

kdawg
kdawg
Posted
Posted
Ok, hence the problem about voltage could be given from cstate code?

 

Another thing, but what is the advantage of using a legacy here, having to still enter the cstate code in the DSDT ?

 

Thanks

 

voodoomonitor show me the vcore changes. istamenu with new fakesmc with plugin (rev 250) show me always the vcore higher (1,32v) like in bios.

 

How do you do to see in voodoomonitor not vcore changes and in istat the drop of vcore together pstates? For me is completely the opposite.

@mm67 and Smith,

I'm not using the legacy kext just the DSDT patch. I use mark-i exclusively for voltage because the current releases of FakeSMC tend to break C-States.

 

I also tend to loose C-States when overclocking. Although until just recently overclocking and C-States were working. I need to find out what I did to loose them.

mm67
mm67
Posted
Posted
Ok, hence the problem about voltage could be given from cstate code?

 

Another thing, but what is the advantage of using a legacy here, having to still enter the cstate code in the DSDT ?

 

Thanks

 

 

 

 

voodoomonitor show me the vcore changes. istamenu with new fakesmc with plugin (rev 250) show me always the vcore higher (1,32v) like in bios.

 

How do you do to see in voodoomonitor not vcore changes and in istat the drop of vcore together pstates? For me is completely the opposite.

 

VoodooMonitor only shows the VID, on iStat I see real Vcore changing like this, idle:

post-375259-1277646053_thumb.png

 

On full load:

post-375259-1277646076_thumb.png

Smith@@™
Smith@@™
Posted
Posted
@mm67 and Smith,

I'm not using the legacy kext just the DSDT patch. I use mark-i exclusively for voltage because the current releases of FakeSMC tend to break C-States.

 

I also tend to loose C-States when overclocking. Although until just recently overclocking and C-States were working. I need to find out what I did to loose them.

 

 

Can you attach your version of mark-i? All that i try don't work well on my series p5q.

 Share
Go to topic listing
×
×
  • Create New...