Jump to content

Probook 4540s Turbo boost not working


10 posts in this topic

Recommended Posts

Hi,

 

I have Probook 4540s without dGPU and CPU Power Management is driving me insane. When I inject AppleIntelCPUPowermanagement kexts, system boots properly and Turbo Boost is active for about 30 seconds. That's followed by instant reboot. I managed to stop the reboot process by adding debug statement to boot-args, but now the screen freezes instead of going into reboot. In System Logs (checked with Hackintool) I can't see nothing specific to that timing.

 

Does anyone have any idea? Or guide me how to check the logs properly? Or how to actually see the exception created on freeze?

 

Thanks!

Link to comment
Share on other sites

Ok. Now that I'm all set maybe it's good to remind people about the original ask:

 

I have Probook 4540s without dGPU and CPU Power Management is driving me insane. When I inject AppleIntelCPUPowermanagement kexts, system boots properly and Turbo Boost is active for about 30 seconds. That's followed by instant reboot. I managed to stop the reboot process by adding debug statement to boot-args, but now the screen freezes instead of going into reboot. In System Logs (checked with Hackintool) I can't see nothing specific to that timing.

 

Does anyone have any idea? Or guide me how to check the logs properly? Or how to actually see the exception created on freeze?

 

Thanks!

 

Link to comment
Share on other sites

You should check the system logs

Use the Console app (Applications > Utilities > Console) to check logs during boot and after the freeze. Look for entries around the time of the freeze or reboot.
Ensure you have the latest version and check the "Logs" section for any clues.

Link to comment
Share on other sites

On 10/30/2024 at 9:58 AM, harrystyles said:

You should check the system logs

Use the Console app (Applications > Utilities > Console) to check logs during boot and after the freeze. Look for entries around the time of the freeze or reboot.
Ensure you have the latest version and check the "Logs" section for any clues.

I did check the kernel logs (collected by Hackintool) but it seems that even the logging stops exactly on the freeze. I can attach then here if someone is willing to take a look.

 

However, from reading so far, it seems that I might need AppleIntelCPUPowerManagement.kext(s) from Monterey (version 12.6 at least or something like that) but the only kexts I have are Vanilla kexts from OCLP github. Can someone please attach the right ones?

 

Thanks!

 

Link to comment
Share on other sites

I fixed it somehow....not sure how. Out of million combinations and two EFIs one started working (wasn't working before). The only real change was that OCLP released version 2.1.0. Not sure if it was the new version or was it simply because i re-applied patches (that might be an important step).

 

However in case someone is stuck with the same problem.

 

1. Use @chris1111 HP-Probook-Elitebook-OC (just google chris1111 and you will find his repo)

2. In case something's not working like in my case (most likely because I'm just upgrading this machine for years) download SSDTTime

3. Drag @chris1111's .aml files from ACPI folder when asked (didn't work in Linux nor Windows for me)

4. Generate SSDT-HPET to resolve IRQ conflicts and hardware will start working

5. If you have that ugly PowerOff card icon and you want to get rid of it, generate SSDT-XOSI with the same tool.

6. If your camera doesn't get detected after all of that, generate SSDT-USB-Reset

7. For all generated SSDTs DO NOT FORGET to merge config.plist from SSDTTime's Results folder and your list 

8. And finally for turbo boost download AppleIntelCPUPowerManagement.kext and AppleIntelPowermanagementClient.kext (you will find them in OCLP github under Misc somewhere)

9. Also to fully configure turbo boost drop CPUPm and CPU0lst (or something like that) tables and reboot

10. Also turbo boost related, during next restart download ssdtPRgen and generate SSDT-PM for your processor

11. Don't forget to remove the tables drop (CPUPm and the other one).....reboot

12. Pray the lord, fingers crossed, go to the desert for 40 days etc.....and hopefully enjoy your fully functional machine with turbo boost 

 

P.S.

 

In case it's not wokring, rebooting, panicing......as a method of last resort, revert the OCLP patches you used somewhere during install, reboot, and re-apply them again.

 

Good luck - you'll need it (SMASH TV)!

 

Link to comment
Share on other sites

On 10/27/2024 at 5:31 PM, registracije registracije said:

Hi,

 

I have Probook 4540s without dGPU and CPU Power Management is driving me insane. When I inject AppleIntelCPUPowermanagement kexts, system boots properly and Turbo Boost is active for about 30 seconds. That's followed by instant reboot. I managed to stop the reboot process by adding debug statement to boot-args, but now the screen freezes instead of going into reboot. In System Logs (checked with Hackintool) I can't see nothing specific to that timing. uno online

 

Does anyone have any idea? Or guide me how to check the logs properly? Or how to actually see the exception created on freeze?

 

Thanks!

It sounds like there may be a kernel panic caused by the AppleIntelCPUPowerManagement kexts, which could be incompatible with your hardware configuration. You might want to try using a patched version of the kext or disable Turbo Boost in BIOS if available, as this could prevent the freezes and reboots.

Link to comment
Share on other sites

11 hours ago, Eddie Nelson said:

It sounds like there may be a kernel panic caused by the AppleIntelCPUPowerManagement kexts, which could be incompatible with your hardware configuration. You might want to try using a patched version of the kext or disable Turbo Boost in BIOS if available, as this could prevent the freezes and reboots.

Thanks Eddie, but I fixed it somehow. Not exactly sure how :)

 

Just spinning million combinations until something started working. The only real change is that while I was doing that, new OCLP came out and I re-applied the patches. In their changelog they mentioned that they disabled FeatureUnlock and something else.....to increase stability. Maybe that helped.....God only knows :)

 

I did patch the kext with AICPM (or whatever is called) patch....so that may have helped as well.

 

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...