Jump to content
11 posts in this topic

Recommended Posts

27 minutes ago, aben said:

You could try tuning X86PP’s power management data (by adjusting the frequency vectors/Perf Bias for your CPU) with help of CPUFriend.

 

*Recommend to go kext route for data injection.

But my cpu is comet lake and ssdtPRGen.sh doesn't support it.

I used CpuFriendFriend and it seems to work but now the CPU name is unknown.

Is it possible to solve this problem?

If I lock the screen the screen won't turn on anymore, is there a way to fix it?

image.png.4f57b4a3c715a92f4ac61e9eef340ea2.png

 

config.plist

Edited by Xflash2006

AFAIK: With CPUFriend, you should either use the kext approach (CPUFriendDataProvider.kext) OR SSDT for data injection, NOT both; try removing/disabling ssdt_data.aml from your plist and see if that fixes the CPU branding issue.

Try the config.plist below

config.plist

Edited by aben
3 hours ago, aben said:

AFAIK: With CPUFriend, you should either use the kext approach (CPUFriendDataProvider.kext) OR SSDT for data injection, NOT both; try removing/disabling ssdt_data.aml from your plist and see if that fixes the CPU branding issue.

Try the config.plist below

config.plist 42.18 kB · 2 downloads

Now the CPU name is right.
Is it normal for the clock to drop to 2.55 GHz in the stress test?

Screenshot 2023-02-10 alle 09.05.49.png

 

On Windows the clock during the stress test is 2.8 GHz

 

Screenshot_20230210_082300.png

 

For the black screen problem what can I do?

Edited by Xflash2006

Those marginal discrepancies between monitoring tools shouldn't matter - what matters is that your CPU should be able to scale to its max turbo frequency dynamically when requested (depending on workloads that demand higher clock speed/peak performance) even on macOS, which I believe is working based off the screenshot you posted. How are you performing the stress test tho? Through the options available via Intel Power Gadget's dropdown-menu? Are you seeing similar results with IPG's  "All Thread Frequency" test?

As for the black screen issue - not quite sure I can be of much help here as I don't have enough info to identify the actual root cause - too many symptoms to list from. You might want to look into testing other CFL/CML framebuffer profiles as well as fixing sleep/wake issues if any (best recommended to consult Dortania's Post-Install guide). 

Feel free to test below attached config.plist (for the display issue only)

config.plist

Edited by aben
  • Thanks 1
6 hours ago, aben said:

Those marginal discrepancies between monitoring tools shouldn't matter - what matters is that your CPU should be able to scale to its max turbo frequency dynamically when requested (depending on workloads that demand higher clock speed/peak performance) even on macOS, which I believe is working based off the screenshot you posted. How are you performing the stress test tho? Through the options available via Intel Power Gadget's dropdown-menu? Are you seeing similar results with IPG's  "All Thread Frequency" test?

As for the black screen issue - not quite sure I can be of much help here as I don't have enough info to identify the actual root cause - too many symptoms to list from. You might want to look into testing other CFL/CML framebuffer profiles as well as fixing sleep/wake issues if any (best recommended to consult Dortania's Post-Install guide). 

Feel free to test below attached config.plist (for the display issue only)

config.plist 42.78 kB · 1 download

Thank you very much! Now the black screen issue is solved.

Is the VRAM normal to be only 1536MB instead of 3.9GB?

I attach the screenshot of the All Thread Frequency test.

 

 

Screenshot 2023-02-11 alle 13.46.39.png

Edited by Xflash2006

Yes, it is working as intended. As per the screenshots, macOS is clearly well-aware of the CPU's max. clock capability and will dynamically request/scale to higher freq. as and when the workload/task calls for the CPU to meet its demands (while actively keeping in-check that all other CPU factors are operating within its designed TDP limit (during request by OS) which is why you will not see the CPU peaking to its max freq for any and all stress tests, especially on low-powered CPUs designed for mobile/laptop devices)

As for VRAM patching - it is best advised to leave it as-is and allow the driver to allocate natively (which is 1536). In fact, WEG documentation strongly recommends against this patch.

Also, good to hear the black screen issue has been solved! :)

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.

×
×
  • Create New...