Jump to content

Chameleon RC5 mode with mem detection enabled and automatic P-States & C-States generation for native power managment

kozlek

By kozlek,
in Chameleon

 Share
1214 posts in this topic

Recommended Posts

banini_jeque
banini_jeque
Posted
Posted

I've patched my DSDT. It has HPET, RTC, TMR, etc. I've checked it like 20 times to make sure it's right, and the devices show up properly in ioreg. I read something about using tabs instead of spaces in the legacy kext causing c state errors, and I know if I use MacPro5,1 as a template, I do get the failed to do the c-state demotion data error, and I have tabs in there. Do I need to take out the tabs?

banini_jeque
banini_jeque
Posted
Posted

For the same reason other people are using legacy kexts, which I think is because it helps you set the CPUPLimit to 0, and get the CStates recognized in some cases where they aren't for whatever reason. I don't see either of those parameters in my ioreg, but I'm guessing that's because I can't yet boot without NullCPUPM.

 

I just named the machine PowerMac3,4 since that's the case I built it in, and because legacy kexts - from what I understand - need to be given machine names that don't exist in the ACPI_SMC_PlatformPlugin.

 

I booted without NullCPUPM and got the exact same panic as when I use -allowAppleCPUPM.

oldnapalm
oldnapalm
Posted
Posted

Try removing NullCPUPM, LegacyPowerMac3_4 and smbios.plist.

 

If ssdt.aml is the original from BIOS, remove these lines from boot.plist

	<key>DropSSDT</key>
<string>Yes</string>
<key>GenerateCStates</key>
<string>Yes</string>
<key>GeneratePStates</key>
<string>No</string>

If it's not (no _PSS and _CST in BIOS SSDT), use

	<key>GenerateCStates</key>
<string>Yes</string>
<key>GeneratePStates</key>
<string>Yes</string>

as4m4df
as4m4df
Posted
Posted

Hi guys, :D

 

Im trying to get this to work on my Vostro 3700 + Core i5 520m, but as soon as i remove NullCPU kext i get KP. (Screenie attached)

 

I dont know if my dsdt (added below) is modded correctly/or at all? Anyone check it or tell me whats to be done to it? i have limted/if any experience with dsdt patching :(

 

Thanks!

post-412067-1290983143_thumb.jpg

post-412067-1290983191_thumb.jpg

dsdt.aml.zip

Rino777
Rino777
Posted
Posted

banini_jeque

I have too - EVGA X58 SLI Classified and this KP problems...

Next Step for u: u have mistake in DSDT in proc. section.

In u DSDT:

Scope (_PR)
{
	Processor (CPU0, 0x00, 0x00000000, 0x00) {}
	Processor (CPU1, 0x01, 0x00000000, 0x00) {}
	Processor (CPU2, 0x02, 0x00000000, 0x00) {}
	Processor (CPU3, 0x03, 0x00000000, 0x00) {}
	Processor (CPU4, 0x04, 0x00000000, 0x00) {}
	Processor (CPU5, 0x05, 0x00000000, 0x00) {}
	Processor (CPU6, 0x06, 0x00000000, 0x00) {}
	Processor (CPU7, 0x07, 0x00000000, 0x00) {}
	Processor (CPU8, 0x08, 0x00000000, 0x00) {}
	Processor (CPU9, 0x09, 0x00000000, 0x00) {}
	Processor (CPUA, 0x0A, 0x00000000, 0x00) {}
	Processor (CPUB, 0x0B, 0x00000000, 0x00) {}
	Processor (CPUC, 0x0C, 0x00000000, 0x00) {}
	Processor (CPUD, 0x0D, 0x00000000, 0x00) {}
	Processor (CPUE, 0x0E, 0x00000000, 0x00) {}
	Processor (CPUF, 0x0F, 0x00000000, 0x00) {}

 

Fixed Code:

	Scope (_PR)
{
	Processor (CPU0, 0x00, 0x00000410, 0x06) {}
	Processor (CPU1, 0x01, 0x00000410, 0x06) {}
	Processor (CPU2, 0x02, 0x00000410, 0x06) {}
	Processor (CPU3, 0x03, 0x00000410, 0x06) {}
	Processor (CPU4, 0x04, 0x00000410, 0x06) {}
	Processor (CPU5, 0x05, 0x00000410, 0x06) {}
	Processor (CPU6, 0x06, 0x00000410, 0x06) {}
	Processor (CPU7, 0x07, 0x00000410, 0x06) {}
	Processor (CPU8, 0x08, 0x00000410, 0x06) {}
	Processor (CPU9, 0x09, 0x00000410, 0x06) {}
	Processor (CPUA, 0x0A, 0x00000410, 0x06) {}
	Processor (CPUB, 0x0B, 0x00000410, 0x06) {}
	Processor (CPUC, 0x0C, 0x00000410, 0x06) {}
	Processor (CPUD, 0x0D, 0x00000410, 0x06) {}
	Processor (CPUE, 0x0E, 0x00000410, 0x06) {}
	Processor (CPUF, 0x0F, 0x00000410, 0x06) {}

Let's test and report ?

U Bios Settings: Turbo - ?, CxE Function to - ?, SpeedStep - ?

banini_jeque
banini_jeque
Posted
Posted

Nah, I already asked them for one, but they said no. Some other guys narrowed it down to something introduced in bios 44 (possibly 32nm CPU support), but they didn't look any further after finding that the bios just before that works with the usual speedstep hacks.

dantoine
dantoine
Posted
Posted

Hi, i am trying to get work the native power management. But if i remove the NullCPUPowerManagement.kext from my extra-folder i get a kernel panic. Here are 1 pictures from the chameleon boot process an 1 picture from the kernel panic. I have also included my extra-folder with smbios.plist, com.apple.Boot.plist and dsdt.aml.

post-427792-1291108788_thumb.jpg post-427792-1291108801_thumb.jpg Extra.zip

 

Can someone help me to solve this problem?

olegischinski
olegischinski
Posted
Posted
Hi, i am trying to get work the native power management. But if i remove the NullCPUPowerManagement.kext from my extra-folder i get a kernel panic. Here are 1 pictures from the chameleon boot process an 1 picture from the kernel panic. I have also included my extra-folder with smbios.plist, com.apple.Boot.plist and dsdt.aml.

 

Can someone help me to solve this problem?

hi,

 

why do you use option DropSSDT=No in your boot.plist?

dantoine
dantoine
Posted
Posted

@olegischinski,

Hi,

I must confess, that I don't really know what the DropSSDT-parameter make. But I have also use this parameter with DropSSDT=Yes. The result is the same kernel-panic. Can someone check my dsdt-File, whether all settings are correct?

DarwinX
DarwinX
Posted
Posted
@olegischinski,

Hi,

I must confess, that I don't really know what the DropSSDT-parameter make. But I have also use this parameter with DropSSDT=Yes. The result is the same kernel-panic. Can someone check my dsdt-File, whether all settings are correct?

 

You must use the DropSSDT=y boot flag if you use a DSDT meant for a specific CPU, and you must NOT use it if you use a DSDT meant for any CPU.

toleda
toleda
Posted
Posted

I have the DFI P55-T36 mother board and I get the following message during boot:

 

AppleSMBusPCI::start failed to get acpi path for provider

 

As well, bdmesg:

 

ACPI table not found: SSDT.aml

 

Any suggestions?

aikidoka25
aikidoka25
Posted
Posted

Anyone using this RC5 with HP Mini 311?

 

I am using meklort branch rev 651 and in general it works fine except for one thing, wake kernel from hibernate (deep sleep) it is not possible.

 

The boot complained with this message: "Not enough space to restore image. Press any key to proceed with normal boot."

 

I viewed resume.c and the fix by Rek(ursor ?) is there.

 

My unit has 3 GB RAM and this was not an issue with PC EFi 10.6 before.

Slice
Slice
Posted
Posted
Anyone using this RC5 with HP Mini 311?

 

I am using meklort branch rev 651 and in general it works fine except for one thing, wake kernel from hibernate (deep sleep) it is not possible.

 

The boot complained with this message: "Not enough space to restore image. Press any key to proceed with normal boot."

 

I viewed resume.c and the fix by Rek(ursor ?) is there.

 

My unit has 3 GB RAM and this was not an issue with PC EFi 10.6 before.

Check, please

	// Rek : hibernate fix 
//	if (!((long long)mem_base+allocSize<1024*bootInfo->extmem+0x100000))
//Slice - ???
if ((long long)mem_base+allocSize<1024*bootInfo->extmem+0x100000)	
{
	printf ("Not enough space to restore image. Press any key to proceed with normal boot.\n");
	getc ();
	return;
}

aikidoka25
aikidoka25
Posted
Posted
Check, please

	// Rek : hibernate fix 
//	if (!((long long)mem_base+allocSize<1024*bootInfo->extmem+0x100000))
//Slice - ???
if ((long long)mem_base+allocSize<1024*bootInfo->extmem+0x100000)	
{
	printf ("Not enough space to restore image. Press any key to proceed with normal boot.\n");
	getc ();
	return;
}

 

Thank you Slice,

I managed to have it working using this modification, 

if (!(long long)mem_base+allocSize<1024*bootInfo->extmem+0x100000)

 

Since this branch is using dynamic library, file Symbols.dylib also changed automatically and need to be copied.

I didn't aware before and was struggling why my modification was not working.

Lesson learned.

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