1945 replies to this topic

[FKA]

oldnapalm, on Sep 30 2009, 05:17 PM, said:

Thank you FormerlyKnownAs for the topic, you were right, maybe if I had took the time to read the whole thread I wouldn't need to ask and create more pollution, sorry for that.

No worries - glad you got it sorted

On another note - with Snow I haven't needed to edit APCI_SMC to get p-states and get rid of cst evaluation errors (using original method of adding ist and cst to DSDT).

OT - I have lost deep sleep though but I think this is as I was using slice's patched USB kext for 10.5.8 (and yes I have added EHCI patch to DSDT.)

D.

[Master Chief]

I continued my testing today, and this time I used MacPro4,1 data to find the following error in kernel.log:

ACPI_SMC_GPU_CtrlLoop::controlRegistered - unexpected control ID 16

The reason I got this error was because my model identifier is set to P5K PRO and thus there's nothing in AppleGraphicsPowerMangement.kext to match with.   Enter a quick and dirty LegacyAGPM.kext (see attachments).  Now my NVIDIA 9600GT (10de:0622) is recognized, and thus no more error.  Oh and here's a handy link to lookup PCI vendor and device ID's.

Next thing is to work on a LegacyACPI_SMC_PlatformPlugin.kext – no more /S*/L*/Extensions hacks for me – to enable NVIDIA throttling since that now only works with MacPro4,1   And I am not going to use this identifier but the one of a MacPro3,1 instead.

Attached Files

•  LegacyAGPM.kext.zip   2.35K   468 downloads

[harshw]

I have an i7 oc'ed to 3.5 GHz. Model identifier is set to MacPro 4,1.

I get this in the ACPI_SMC_Plugin

 Screen_shot_2009_09_30_at_23_20_27.png   76.47K   314 downloads

And of course my board being ASUS, I have the usual section for CPU

Quote

DefinitionBlock ("dsdt.aml", "DSDT", 1, "A1279", "A1279001", 0x00000001)
{
    Scope (_PR)
    {
        Processor (P001, 0x01, 0x00000810, 0x06) {}
        Alias (P001, CPU1)
        Processor (P002, 0x02, 0x00000000, 0x00) {}
        Alias (P002, CPU2)
        Processor (P003, 0x03, 0x00000000, 0x00) {}
        Alias (P003, CPU3)
        Processor (P004, 0x04, 0x00000000, 0x00) {}
        Alias (P004, CPU4)
        Processor (P005, 0x05, 0x00000000, 0x00) {}
        Alias (P005, CPU5)
        Processor (P006, 0x06, 0x00000000, 0x00) {}
        Alias (P006, CPU6)
        Processor (P007, 0x07, 0x00000000, 0x00) {}
        Alias (P007, CPU7)
        Processor (P008, 0x08, 0x00000000, 0x00) {}
        Alias (P008, CPU8)
        Processor (P009, 0x09, 0x00000000, 0x00) {}
        Alias (P009, CPU9)
        Processor (P010, 0x0A, 0x00000000, 0x00) {}
        Processor (P011, 0x0B, 0x00000000, 0x00) {}
        Processor (P012, 0x0C, 0x00000000, 0x00) {}
        Processor (P013, 0x0D, 0x00000000, 0x00) {}
        Processor (P014, 0x0E, 0x00000000, 0x00) {}
        Processor (P015, 0x0F, 0x00000000, 0x00) {}
        Processor (P016, 0x10, 0x00000000, 0x00) {}
    }

MSR tools running under 32bit 10.6 tells me the CPU runs at 3.5GHz. What is surprising is that idle temps are 44c ~ 45c. Granted I have a TRUE-120, but shouldn't they be higher ? I get temps of 43c ~ 44c under Windows, so not much of a difference. And my Windows idle is at 2000 MHz ( 12x mult )

 Screen_shot_2009_09_30_at_23_33.png   37.34K   99 downloads

So what's going on ? Does OSX idle at 3.5 GHz so efficiently that the temps are comparable to 2.0 GHz ? And do I have to replace the P-State array and create new C-states for the 3.5 GHz overclock ?

[Beerkex'd]

Master Chief, on Oct 1 2009, 06:21 PM, said:

The reason I got this error was because my model identifier is set to P5K PRO and thus there's nothing in AppleGraphicsPowerMangement.kext to match with.   Enter a quick and dirty LegacyAGPM.kext (see attachments).  Now my NVIDIA 9600GT (10de:0622) is recognized, and thus no more error.

That's pretty cool, thanks!
I deleted the two other Nvidia IDs in the kext, and changed yours to 0612 to match my 9800GTX+ and it loads.
This ought to be more compatible than having my 9800GTX+ identified as an IGP (I use iMac9,1 for model identifier).
Do you know what the "control-id" corresponds to? GPU class/family?
And the thresholds, are they degrees centigrade or a percentage of something?
IOReg screenshot:
 LegacyAGPM.png   63.56K   306 downloads

Master Chief, on Oct 1 2009, 06:21 PM, said:

Next things is to work on a LegacyACPI_SMC_PlatformPlugin.kext – no more /S*/L*/Extensions hacks for me – to enable NVIDIA throttling since that now only works with MacPro4,1 And I am not going to use this identifier but the one of a MacPro3,1 instead.

Wow Good luck on that.

[THe KiNG]

harshw, on Oct 2 2009, 01:36 AM, said:

So what's going on ? Does OSX idle at 3.5 GHz so efficiently that the temps are comparable to 2.0 GHz ? And do I have to replace the P-State array and create new C-states for the 3.5 GHz overclock ?

Well you have rev D0 on CPU, that is known as cooler then C0/C1.
Anyway I don't know how much trust you can have on MSRTools on temps...
There is a better tool for reading temps and fans Mark-i be aware that thread is in rusian and for snow only
If your sensor chip is Winbond W83667HG(check with Lavalys Everest) it should work with it.

[Master Chief]

Beerkex'd, on Oct 2 2009, 03:39 AM, said:

That's pretty cool, thanks!
I deleted the two other Nvidia IDs in the kext, and changed yours to 0612 to match my 9800GTX+ and it loads.
This ought to be more compatible than having my 9800GTX+ identified as an IGP (I use iMac9,1 for model identifier).

IGP is the Internal Graphics Processor and is controlled by iGPUThrottle.  This setting can be found under ControlArray (Item 21 for iMac9,1) and is set to True.  Making it a little too dangerous for my taste.  At least for now without really knowing what it does.  We need additional info/data.

Beerkex'd, on Oct 2 2009, 03:39 AM, said:

Do you know what the "control-id" corresponds to? GPU class/family?

You can find the following items under ControlArray in ACPI_SMC_PlatformPlugin:

10 = CPU_PLIMIT
11 = GPU_PLIMIT
12 = MEM_PLIMIT
13 = CPU_STATE
14 = GPU_STATE
15 = IDLE_LIMIT
16 = GPU_RANGE_CONTROL_INTERNAL
17 = GPU_RANGE_CONTROL_EXTERNAL
18 = GPU_RANGE_CONTROL_PCI

Take a look at ValidConfigs under GPU_RANGE_CONTROL_PCI which is set to 18/0x12 (MacPro4,1).  That is also why is doesn't really work for you with iMac9,1 set as model identifier.

And the following items under ControlLoopArray:

0 = SMC_CPU_Control_Loop
1 = SMC_GPU_sensor_Control_Loop
2 = SMC_Memory_Control_Loop
3 = SMC_GPU_Range_Control_Loop

Which is rather important.  Let's have a look at CIA4 for the iMac9,1 which is set to: 3, 1 and 1.    Now compare this with CIA7 for the MacPro4,1   There you'll find: 3, 18 and 0.  Which happen to correspond with the following items:

SMC_GPU_Range_Control_Loop
GPU_RANGE_CONTROL_PCI
SMC_CPU_Control_Loop

Coincidence?  I don't think so.

Beerkex'd, on Oct 2 2009, 03:39 AM, said:

And the thresholds, are they degrees centigrade or a percentage of something?

Load percentage (0x64 is 100).

[FKA]

Master Chief, on Oct 1 2009, 10:21 PM, said:

I continued my testing today, and this time I used MacPro4,1 data to find the following error in kernel.log:

ACPI_SMC_GPU_CtrlLoop::controlRegistered - unexpected control ID 16

The reason I got this error was because my model identifier is set to P5K PRO and thus there's nothing in AppleGraphicsPowerMangement.kext to match with.   Enter a quick and dirty LegacyAGPM.kext (see attachments).  Now my NVIDIA 9600GT (10de:0622) is recognized, and thus no more error.  Oh and here's a handy link to lookup PCI vendor and device ID's.

Next things is to work on a LegacyACPI_SMC_PlatformPlugin.kext �" no more /S*/L*/Extensions hacks for me �" to enable NVIDIA throttling since that now only works with MacPro4,1   And I am not going to use this identifier but the one of a MacPro3,1 instead.

Can somebody please post ACPI dump from a MacPro4,1?

D.

[Master Chief]

THe KiNG, on Sep 22 2009, 11:04 AM, said:

<snip />

How to override SMC_Platform_Plugin.kext I described HERE

I thought to have killed another CPU:

But apparently it was just this code:

<dict>
	<key>IOCPUNumber</key>
	<integer>0</integer>
</dict>

Change it into 1 and then CPU2 is gone.  All OK again after removing the kext.

p.s. Same problem with my still in progress LegacyACPI_SMC_PlatformPlugin.kext

[THe KiNG]

Dunno what you doing there...works perfect for me(and others)

FormerlyKnownAs, on Oct 2 2009, 02:04 PM, said:

Can somebody please post ACPI dump from a MacPro4,1?

D.

http://rapidshare.de...mField.zip.html

[Master Chief]

THe KiNG, on Oct 2 2009, 05:10 PM, said:

Dunno what you doing there...works perfect for me(and others)

http://rapidshare.de...mField.zip.html

What I did is this:
1) Copy kext into: /Extra/Extensions.
2) Reboot.
3) Start CPU-i.

And I am pretty sure that others here can reproduce this behaviour.

[FKA]

THe KiNG, on Oct 2 2009, 04:10 PM, said:

Dunno what you doing there...works perfect for me(and others)


http://rapidshare.de...mField.zip.html

many thanks.
D

[FKA]

THe KiNG, on Oct 2 2009, 04:10 PM, said:

Dunno what you doing there...works perfect for me(and others)


http://rapidshare.de...mField.zip.html

Should I need to remove/disable AppleTYMCEDriver.kext when setting MacPro4,1 as I don't have i7 CPU?

[harshw]

FormerlyKnownAs, on Oct 3 2009, 05:17 PM, said:

Should I need to remove/disable AppleTYMCEDriver.kext when setting MacPro4,1 as I don't have i7 CPU?

Yup - it works only with Nehalem

[spanakorizo]

what's the benefits of using mac pro 4.1 as a model instead of 3.1 ?

[FKA]

spanakorizo, on Oct 3 2009, 06:28 PM, said:

what's the benefits of using mac pro 4.1 as a model instead of 3.1 ?

I want to try The KiNgs legacy ACPI_SMC kext and GPU throttling works with MacPro4,1 identifyer.

D.

[FKA]

IRQ Question  --

in my case would i remove what's highlighteed in red bellow ??

				Device (PIC)
				{
					Name (_HID, EisaId ("PNP0000"))
					Name (_CRS, ResourceTemplate ()
					{
						IO (Decode16,
							0x0020,			 // Range Minimum
							0x0020,			 // Range Maximum
							0x01,			   // Alignment
							0x02,			   // Length
							)
						IO (Decode16,
							0x00A0,			 // Range Minimum
							0x00A0,			 // Range Maximum
							0x01,			   // Alignment
							0x02,			   // Length
							)
						[b][color="#ff0000"]IRQNoFlags ()
							{2}[/color][/b]
					})
				}

D

[oldnapalm]

I tested Master Chief's LegacyAGPM.kext using MacPro4,1 as identifier, AGPM loads but with this identifier CPU-i shows no voltage reduction when CPU is idle (temperature is OK tough)
 Captura_de_tela_2009_10_03___s_18.31.31.png   88.91K   150 downloads

Using MacPro3,1 or MacPro4,1 with The King's MP41SpeedStepFix.kext voltage goes down, but no AGPM
 Captura_de_tela_2009_10_03___s_18.44.38.png   25.65K   98 downloads

How do I know if AGPM is actually working?

Thanks.

[Master Chief]

Done!

Like I said in post #362

"Next thing is to work on a LegacyACPI_SMC_PlatformPlugin.kext – no more /S*/L*/Extensions hacks for me – to enable NVIDIA throttling since that now only works with MacPro4,1 And I am not going to use this identifier but the one of a MacPro3,1 instead."

The new kext accompanying LegacyAGPM.kext is Legacy_ACPI_SMC_PP.kext and can be used with the following model identifiers:

MacPro3,1
MacPro4,1
P5K PRO

Feel free to replace the latter one with say iMac9,1    Oh and don't forget to modify LegacyAGPM.kext which only works with P5K PRO as model identifier, and you migh need to add your video card (see also post #362).

NVDA

AGPM Picture 1


AGPM Picture 2


AGPM Picture 3



CPU0

AGPM Picture 4



Attachments

Attached Files

•  Legacy_ACPI_SMC_PP.kext.zip   4.58K   172 downloads

[oldnapalm]

Yes Sir, it works. Thanks for sharing.
 Captura_de_tela_2009_10_04___s_02.35.05.png   87.91K   192 downloads

[FKA]

Master Chief, on Oct 4 2009, 06:04 AM, said:

AGPM Picture 1


AGPM Picture 2

very good - thanks!

I don't seem to have the 'gpu-control' branch under GFX, just AGPM.
Any ideas? not supported for my GPU or am i missing something from GPU DSDT injection part?

 Screen_shot_2009_10_04_at_13.48.24.png   35.63K   76 downloads

D.