95 replies to this topic

[JBraddock]

Fire up terminal and type:  kextstat

You should see the below line if it is loaded.

78	0 0x555eb000 0x3000	 0x2000	 com.apple.driver.AppleLPC (1.4.12) <14 5 4 3>

In order to run the code above you may need to install this.

[gurde]

Well, yes. As I previously posted, I did that already.
kextstat | grep LPC
   62    0 0xffffff7f80926000 0x3000     0x3000     com.apple.driver.AppleLPC (1.4.12) <9 5 4 3>
So, do I have to patch anything?

Why do I still have this?
kernel[0]: ACPI_SMC_PlatformPlugin::start - waitForService(resourceMatching(AppleIntelCPUPowerManagement) timed out
kernel[0]: ACPI_SMC_PlatformPlugin::registerLPCDriver - WARNING - LPC device initialization failed: C-state power management not initialized

[JBraddock]

Do you still use NullCPUPowerManagement.kext?

[gurde]

Nope.

[JBraddock]

What do you use for speedstep?

VoodooPowerMini?
Chameleon RC's new feature?

[MaLd0n]

gurde, on Sep 24 2010, 01:51 PM, said:

Could you please be more specific?

more specific than this topic?

Quote

In the Info.plist I get <string>pci8086,2815</string>, does this mean is supported?

Yep

I want to know is if you applied the fixLpc?

I have seen cases of id compatible and when applied the patch (not necessary in this case)
this problem happened

*search by address, the names vary
0x001F0000

[gurde]

I don't use VoodooPowerMini or any VoodooPower.
And use the latest Chameleon.
I found that 0x001F0000, Device (ISAB).
Now what?

[JBraddock]

Do you use Generate P-States, C-States Feature. If not, give it a try.
If it doesn't change anything try to install VoodooPowerMini.

[gurde]

Yes I did included that into my com.apple.Boot.plist, but the same results.
Also with VoodooPowerMini, the same results, that's why I removed it.

[JBraddock]

As MaLd0n said above, may be even though your LPC device id matches you still need to patch your LPC device. Look at the example.
I assume that you change your mac model to what MaLd0n told you.

Here is the code from my DSDT.

Device (LPC) // Names vary.
			{
				Name (_ADR, 0x001F0000) // Search for this.
				Method (_DSM, 4, NotSerialized) // Start from here
				{
					Store (Package (0x02)
						{
							"device-id", 
							Buffer (0x04)
							{
								0x16, 0x29, 0x00, 0x00
							}
						}, Local0)
					DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
					Return (Local0)
				} // Stop here. Rest is removed.
							   ....

You only need to change 0x16, 0x29, 0x00, 0x00 to 0x15, 0x28, 0x00, 0x00.

[JBraddock]

If none of these suggestions solve your problem, assuming you set your mac model to MacbookPro5,1, please download the following kext and copy it to Extra folder. Repair permission and restart. Finally, after installing this kext, could you also use IORegistryExplorer and take a screenshot of the ACPI_SMC_PlatformPlugin section and upload it here.

http://www.mediafire...ke29otlp5vyhsnq

Try this kext, with the following combinations.

- With VoodooPowerMini and without GenerateC-States & P-States = True.
- Without VoodooPowerMini and with GenerateC-States & P-States = True
- Without VoodooPowerMini and without GenerateC-States & P-States = True (This should work fine)

Whenever you don't use GenerateC-States & P-States = True, make sure that you don't have DropSSDT=True key in your boot.plist.
Do backup first please.

[gurde]

So every time I use c&pstate=yes also I must use DropSSDT=Yes? Cause your explanations is ambiguous.

[JBraddock]

My friend, you are not reading carefully, if you look at the previous page, you can see that MaLd0n explained how to use these features.
Yes, you have to use that key because you basically override your SSDT tables, which are responsible for the speed step of the CPU, so you have to tell OSX not to use your original tables.

[gurde]

ok, I already had that there, just wanted to be sure.
Now maybe I'm blind, but I can't see Method (_DSM, 4, NotSerialized) under Name (_ADR, 0x001F0000). And even if I put that there, still doesn't work.
I attached my dsdt.dsl, could you please look inside it?
What am I doing wrong?

Attached Files

•  dsdt.dsl.zip   19.79K   2 downloads

[JBraddock]

gurde, on Sep 24 2010, 08:05 PM, said:

ok, I already had that there, just wanted to be sure.
Now maybe I'm blind, but I can't see Method (_DSM, 4, NotSerialized) under Name (_ADR, 0x001F0000). And even if I put that there, still doesn't work.
I attached my dsdt.dsl, could you please look inside it?
What am I doing wrong?

My friend, the code that I shared is from my DSDT. I just showed you the part that you should apply. So, this is your original code.

Device (ISAB)
			{
				Name (_ADR, 0x001F0000)
				Device (PS2M)
				{
					Name (_HID, EisaId ("PNP0F13"))
					Name (CRS, ResourceTemplate ()
					{
						IRQNoFlags ()
							{12}
					})
					Method (_CRS, 0, NotSerialized)
					{
						Return (CRS)
					}
				}

This is the one it should be.

Device (ISAB)
			{
				Name (_ADR, 0x001F0000)
				Method (_DSM, 4, NotSerialized) // Start from here
				{
					Store (Package (0x02)
						{
							"device-id", 
							Buffer (0x04)
							{
								0x15, 0x28, 0x00, 0x00 // Your device id.
							}
						}, Local0)
					DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0))
					Return (Local0)
				} // Stop here. Rest is removed.

				Device (PS2M)
				{
					Name (_HID, EisaId ("PNP0F13"))
					Name (CRS, ResourceTemplate ()
					{
						IRQNoFlags ()
							{12}
					})
					Method (_CRS, 0, NotSerialized)
					{
						Return (CRS)
					}
				}

Code between "Star from here" and "Stop Here" is what you have to apply.

[gurde]

I did that, I still get those errors in the kernel.log
Other suggestions?

[JBraddock]

Did you install my kext as I said?

[gurde]

Yes I did. I attached the screenshot also.
However 1st boot, kernel panicked, then went fine.
Same error in log.

Attached Files

•  Screen_shot_2010_09_24_at_10.36.21_PM.png   111.72K   26 downloads

[JBraddock]

It gets loaded but it doesn't active P-States or C-States. Assuming, you've tried all the combinations I said, I am sorry I don't know what else you could be having problem with. You should ask this on Intel Speedstep section of the forum. In the meantime, you could use NullPowermanagement and VoodooPowerMini to keep your laptop relatively cool.

[gurde]