Mavericks: Native CPU/IGPU Power Management

[RehabMan]

X86PlatformPlugin is loaded without SSDT.aml.

No X86PlatformPlugin in either of the ioreg you upload.

Here is the IOReg with the SSDT installed which is ACPI_SMC_Platformplugin.

ACPI_SMC_PlatformPlugin != X86PlatformPlugin.

No SSDT loaded by the bootloader. From your bootlog:

ACPI Table not found: DSDT.aml
ACPI Table not found: SSDT.aml

This is from from generate P/CStates=No

No. GenerateC/PStates is Yes. From your bootlog:

SSDT with CPU C-States generated successfully
P-States: min 0x8, max 0x25
SSDT with CPU P-States generated successfully

Maybe you are mixing your files up...

 

[wildwillow]

No X86PlatformPlugin in either of the ioreg you upload.



ACPI_SMC_PlatformPlugin != X86PlatformPlugin.

No SSDT loaded by the bootloader. From your bootlog:

ACPI Table not found: DSDT.aml
ACPI Table not found: SSDT.aml

No. GenerateC/PStates is Yes. From your bootlog:

SSDT with CPU C-States generated successfully
P-States: min 0x8, max 0x25
SSDT with CPU P-States generated successfully

Maybe you are mixing your files up...

I posted the same results earlier as a conundrum and resulted in the same.

 

[RehabMan]

I posted the same results earlier as a conundrum and resulted and in the same.

No conundrum. The ioreg files you upload do not support your assertions re your configuration.

 

[wildwillow]

No conundrum. The ioreg files you upload do not support your assertions re your configuration.

Firstly are seeing this power management installed via SSDT.

 

[RehabMan]

Firstly are seeing this power management installed via SSDT.

No SSDT installed. From your bootlog:

ACPI Table not found: DSDT.aml
ACPI Table not found: SSDT.aml

No X86PlatformPlugin loaded (as would be expected).

Two SSDTs in ioreg. Look like SSDTs generated from Chameleon. And confirmed by bootlog:

SSDT with CPU C-States generated successfully
P-States: min 0x8, max 0x25
SSDT with CPU P-States generated successfully

All your ioreg files appear to be from the same config. Which is:
- DropSSDT=Yes
- GenerateCStates=Yes
- GeneratePStates=Yes
- no generated SSDT at /Extra/SSDT.aml

 

[wildwillow]

No SSDT installed. From your bootlog:

ACPI Table not found: DSDT.aml
ACPI Table not found: SSDT.aml

No X86PlatformPlugin loaded (as would be expected).

Two SSDTs in ioreg. Look like SSDTs generated from Chameleon. And confirmed by bootlog:

SSDT with CPU C-States generated successfully
P-States: min 0x8, max 0x25
SSDT with CPU P-States generated successfully

All your ioreg files appear to be from the same config. Which is:
- DropSSDT=Yes
- GenerateCStates=Yes
- GeneratePStates=Yes
- no generated SSDT at /Extra/SSDT.aml

Sorry to be the bearer of bad news but IOReg is reading inaccurate results. C and P States are No.

 

[RehabMan]

Sorry to be the bearer of bad news but IOReg is reading inaccurate results. C and P States are No.

Ioreg never lies. Check bdmesg output yourself. Double check you're not mixing up your files.

 

[wildwillow]

Ioreg never lies. Check bdmesg output yourself.

You may be correct, maybe injection or user error, but output using tools is correct.

 

[RehabMan]

You may be correct, maybe injection or user error, but output using tools is correct.

I don't know what you mean by "output using tools is correct," but I'll wait for you to show an ioreg that shows something other than Yes/Yes for GeneratePStates/GenerateCStates and an ioreg that shows /Extra/ssdt.aml being loaded by the bootloader.

You can check all of that yourself by looking in ioreg before sending the file.

GeneratePStates/CStates=No: You should NOT see these lines in bdmesg output:

SSDT with CPU C-States generated successfully
P-States: min 0x8, max 0x25
SSDT with CPU P-States generated successfully

And you should see an SSDT.aml being loaded... eg. NOT:

ACPI Table not found: SSDT.aml

If the SSDT (assuming you get it placed where it will load) has plugin-type=1 injection, then you should see X86PlatformPlugin loaded in ioreg under CPU0.

In addition, in the event you manage to turn off bootloader generate C/P states, and install an SSDT to /Extra/ssdt.aml, you will see only one SSDT under AppleACPIPlatformExpert->ACPI Tables.

 

[wildwillow]

I don't know what you mean by "output using tools is correct," but I'll wait for you to show an ioreg that shows something other than Yes/Yes for GeneratePStates/GenerateCStates and an ioreg that shows /Extra/ssdt.aml being loaded by the bootloader.

You can check all of that yourself by looking in ioreg before sending the file.

GeneratePStates/CStates=No: You should NOT see these lines in bdmesg output:

SSDT with CPU C-States generated successfully
P-States: min 0x8, max 0x25
SSDT with CPU P-States generated successfully

And you should see an SSDT.aml being loaded... eg. NOT:

ACPI Table not found: SSDT.aml

If the SSDT (assuming you get it placed where it will load) has plugin-type=1 injection, then you should see X86PlatformPlugin loaded in ioreg under CPU0.

In addition, in the event you manage to turn off bootloader generate C/P states, and install an SSDT to /Extra/ssdt.aml, you will see only one SSDT under AppleACPIPlatformExpert->ACPI Tables.

Ok write to the author of power management, maybe IOReg doesn't see the change. as explained by many others ocB.c is correct. Yet IOReg doesn't see it.. Injection.