Jump to content

How to: Intel Pentium G3XXX and Celeron G1XXX (Haswell) works with speedstep Yosemite 10.10 and Mavericks 10.9


stinga11
 Share

237 posts in this topic

Recommended Posts

Hello syscl. Is there any news about power management on Pentium/Celeron CPU's in macOS Sierra?

Hello @vandroiy2012, I've tried to patch the mach_kernel for enabling XCPM, but sadly it does not work. So I have to dig out it from other ways.

 

Till now the best we can achieve is to remove both AppleIntelCPUPowerManagement.kext, AppleIntelCPUPowerManagementClient.kext and NullCPUPowerManagement.kext once we finish installed Sierra.

 

The support of XCPM on IvyBridge has since removed, so with the FakeCPUID=0x0306A0, system treats Haswell Pentium/Celeron as a IvyBridge model then calls for AppleIntelCPUPowerManagement::init(), which will cause kernel panic at booting stage. Things get worse on Sierra, because both AppleIntelCPUPowerManagement and XCPM cannot enable Pentium/Celeron P-State/C-State. 

 

So people may think by easily replacing 83f83a with 83f83c can solve such issue to enable XCPM, but this issue is much deeper than we might think. I assume maybe we can patch mach_kernel in some place to bypass the kernel panic directly instead of faking CPUID to IvyBridge which is not enough/suitable for Haswell Pentium/Celeron.

 

syscl 

  • Like 2
Link to comment
Share on other sites

Hello @vandroiy2012, I've tried to patch the mach_kernel for enabling XCPM, but sadly it does not work. So I have to dig out it from other ways.

 

Till now the best we can achieve is to remove both AppleIntelCPUPowerManagement.kext, AppleIntelCPUPowerManagementClient.kext and NullCPUPowerManagement.kext once we finish installed Sierra.

 

The support of XCPM on IvyBridge has since removed, so with the FakeCPUID=0x0306A0, system treats Haswell Pentium/Celeron as a IvyBridge model then calls for AppleIntelCPUPowerManagement::init(), which will cause kernel panic at booting stage. Things get worse on Sierra, because both AppleIntelCPUPowerManagement and XCPM cannot enable Pentium/Celeron P-State/C-State.

 

So people may think by easily replacing 83f83a with 83f83c can solve such issue to enable XCPM, but this issue is much deeper than we might think. I assume maybe we can patch mach_kernel in some place to bypass the kernel panic directly instead of faking CPUID to IvyBridge which is not enough/suitable for Haswell Pentium/Celeron.

 

syscl

If we dont use FakeCPUID, we can pass AICPUPM.kext panic, but get other panic.

 

I research to find solution. Yet not success now.

 

나의 LG-F410S 의 Tapatalk에서 보냄

  • Like 1
Link to comment
Share on other sites

  • 4 weeks later...

Good news!!! Thanks to @vit9696 Haswell Celeron/Pentium CPU's can use xcpm mode and work without NullCPUPowerManagement.kext and also prevent app crashing (Messages, iBooks etc.) 

 

1. Remove NullCPUPowerManagement.kext.

2. Use macmodel iMac13,1

3. Use FakeCPUID - 0x0306A0

4. -xcpm in bootargs

5. Two kernel patches into KernelAndKextPatches section in config.plist (first patch prevent app crashing, second patch enables xcpm mode)

        <key>KernelToPatch</key>
        <array>
            <dict>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>
                uaABAAAPMg==
                </data>
                <key>MatchOS</key>
                <string>10.12</string>
                <key>Replace</key>
                <data>
                uaABAAAxwA==
                </data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>xcpm on Sierra Haswell Celeron/Pentium</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>
                g8PEg/si
                </data>
                <key>MatchOS</key>
                <string>10.12</string>
                <key>Replace</key>
                <data>
                g8PGg/si
                </data>
            </dict>

post-1069282-0-04207500-1473375579_thumb.png

 

So we have working speedstep :thumbsup_anim:

post-1069282-0-13040600-1473375703.pngpost-1069282-0-72125700-1473375703.png

 

  • Like 2
Link to comment
Share on other sites

Good news!!! Thanks to @vit9696 Haswell Celeron/Pentium CPU's can use xcpm mode and work without NullCPUPowerManagement.kext and also prevent app crashing (Messages, iBooks etc.) 

 

1. Remove NullCPUPowerManagement.kext.

2. Use macmodel iMac13,1

3. Use FakeCPUID - 0x0306A0

4. -xcpm in bootargs

5. Two kernel patches into KernelAndKextPatches section in config.plist (first patch prevent app crashing, second patch enables xcpm mode)

        <key>KernelToPatch</key>
        <array>
            <dict>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>
                uaABAAAPMg==
                </data>
                <key>MatchOS</key>
                <string>10.12</string>
                <key>Replace</key>
                <data>
                uaABAAAxwA==
                </data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>xcpm on Sierra Haswell Celeron/Pentium</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>
                g8PEg/si
                </data>
                <key>MatchOS</key>
                <string>10.12</string>
                <key>Replace</key>
                <data>
                g8PGg/si
                </data>
            </dict>

attachicon.gifСнимок экрана 2016-09-09 в 01.41.43.png

 

So we have working speedstep :thumbsup_anim:

attachicon.gifСнимок экрана 2016-09-09 в 01.39.14.pngattachicon.gifСнимок экрана 2016-09-09 в 01.39.30.png

 

 

thanks good working now :)

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

Good news!!! Thanks to @vit9696 Haswell Celeron/Pentium CPU's can use xcpm mode and work without NullCPUPowerManagement.kext and also prevent app crashing (Messages, iBooks etc.) 

 

1. Remove NullCPUPowerManagement.kext.

2. Use macmodel iMac13,1

3. Use FakeCPUID - 0x0306A0

4. -xcpm in bootargs

5. Two kernel patches into KernelAndKextPatches section in config.plist (first patch prevent app crashing, second patch enables xcpm mode)

        <key>KernelToPatch</key>
        <array>
            <dict>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>
                uaABAAAPMg==
                </data>
                <key>MatchOS</key>
                <string>10.12</string>
                <key>Replace</key>
                <data>
                uaABAAAxwA==
                </data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>xcpm on Sierra Haswell Celeron/Pentium</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>
                g8PEg/si
                </data>
                <key>MatchOS</key>
                <string>10.12</string>
                <key>Replace</key>
                <data>
                g8PGg/si
                </data>
            </dict>

attachicon.gifСнимок экрана 2016-09-09 в 01.41.43.png

 

So we have working speedstep :thumbsup_anim:

attachicon.gifСнимок экрана 2016-09-09 в 01.39.14.pngattachicon.gifСнимок экрана 2016-09-09 в 01.39.30.png

 

Hi,

 

I have done all this and when the installer reboots the system and i choose the install disk in clover nothing happens. Turned on -V and noticed a kernel panic.

Can anyone help me out with this?

Link to comment
Share on other sites

This is KERNEL patches but not kext patches. Look at my post #103 carefully. Especially on pictures :)

 

Thanks, but i cant find the issue here. Have i set those lines of code in the wrong place in the config file or what? What is that program the picture is showing? Cant find that in clover configurator

Link to comment
Share on other sites

Thanks, but i cant find the issue here. Have i set those lines of code in the wrong place in the config file or what? What is that program the picture is showing? Cant find that in clover configurator

 

You insert KERNEL patches in KEXT patches section. Look carefully :drool:

 

We need KernelToPatch but not KextToPatch section!!! 

Link to comment
Share on other sites

You insert KERNEL patches in KEXT patches section. Look carefully :drool:

 

We need KernelToPatch but not KextToPatch section!!! 

 

what program are you using in the picture in that post? I mean in CC theres not all the fields.

Sorry for being a noob here :( 

Link to comment
Share on other sites

PlistEdit Pro. Forget about CloverConfigurator...

I have now edited it with plistedit pro with the given values. Run the installer and choose install disk in clover. It starts moving and then stops and nothing happens. Is that normal?

 

Heres the new config.plist

 

https://www.dropbox.com/s/tujpftfbytgtvdx/config.plist?dl=0

 

Thanks for helping me!

Link to comment
Share on other sites

I have now edited it with plistedit pro with the given values. Run the installer and choose install disk in clover. It starts moving and then stops and nothing happens. Is that normal?

 

Heres the new config.plist

 

https://www.dropbox.com/s/tujpftfbytgtvdx/config.plist?dl=0

 

Thanks for helping me!

 

Config.plist is OK. I don't know why nothing happens. You should boot in verbose mode and provide photo of the stop screen.

Link to comment
Share on other sites

Config.plist is OK. I don't know why nothing happens. You should boot in verbose mode and provide photo of the stop screen.

I have submitted a picture where it stops right now. The strange thing here is that i have managed to get passed this and ending up with a grey screen with the mouse pointer active just spinning that colored wheel. When i click the mouse it disappear. I´ve left the computer on that grey screen for about 7 hours and nothing is happening.

 

https://www.dropbox.com/sh/39qp9zky4q5b4bn/AACVlsNnM2nIkSxb5H4IugZIa?dl=0

Link to comment
Share on other sites

Good news!!! Thanks to @vit9696 Haswell Celeron/Pentium CPU's can use xcpm mode and work without NullCPUPowerManagement.kext and also prevent app crashing (Messages, iBooks etc.) 

 

1. Remove NullCPUPowerManagement.kext.

2. Use macmodel iMac13,1

3. Use FakeCPUID - 0x0306A0

4. -xcpm in bootargs

5. Two kernel patches into KernelAndKextPatches section in config.plist (first patch prevent app crashing, second patch enables xcpm mode)

        <key>KernelToPatch</key>
        <array>
            <dict>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>
                uaABAAAPMg==
                </data>
                <key>MatchOS</key>
                <string>10.12</string>
                <key>Replace</key>
                <data>
                uaABAAAxwA==
                </data>
            </dict>
            <dict>
                <key>Comment</key>
                <string>xcpm on Sierra Haswell Celeron/Pentium</string>
                <key>Disabled</key>
                <false/>
                <key>Find</key>
                <data>
                g8PEg/si
                </data>
                <key>MatchOS</key>
                <string>10.12</string>
                <key>Replace</key>
                <data>
                g8PGg/si
                </data>
            </dict>

attachicon.gifСнимок экрана 2016-09-09 в 01.41.43.png

 

So we have working speedstep :thumbsup_anim:

attachicon.gifСнимок экрана 2016-09-09 в 01.39.14.pngattachicon.gifСнимок экрана 2016-09-09 в 01.39.30.png

Would that still require me to use that SSDT generator script stuff on the first post? or can I just use the above mentioned patches sans issues?

Link to comment
Share on other sites

By the way. The system works even better if i use iMac14,2. With this macmodel i don't have failed to send stepper error in log.

Using the same procedure? In my case I get an AppleIntelCPUPowerManagement kernel panic after deleting the NullCPUPM kext. Tried disabling and/or enabling Generate C/P states and a few others to no avail.

Link to comment
Share on other sites

Using the same procedure? In my case I get an AppleIntelCPUPowerManagement kernel panic after deleting the NullCPUPM kext. Tried disabling and/or enabling Generate C/P states and a few others to no avail.

Yes. Same procedure except macmodel. Check patches. They should be in KernelToPatch section, not KextToPatch.
  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...