Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update power management page #111

Merged
merged 11 commits into from
Aug 8, 2022
Merged

Update power management page #111

Changes from 1 commit
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
0689e7d
Add notes on using CPUFriend + reusing old frequency vectors
dhinakg Jun 21, 2022
8fc2ed2
Incorporate suggested changes and grammatical changes
dhinakg Jul 24, 2022
1f2ffdc
Update wording
dhinakg Jul 24, 2022
a8f42d5
More small changes
dhinakg Jul 26, 2022
a563f7e
Update universal/pm.md
dhinakg Jul 29, 2022
861f64d
Update universal/pm.md
dhinakg Jul 29, 2022
5a236cb
Apply suggestions from code review
dhinakg Jul 29, 2022
101a77f
Incorporate changes
dhinakg Aug 3, 2022
99794ac
Add Min/MaxKernel note
dhinakg Aug 8, 2022
bd81b4c
Merge branch 'master' into cpufriend-updates
dhinakg Aug 8, 2022
e52d079
Merge branch 'master' into cpufriend-updates
dhinakg Aug 8, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update universal/pm.md 
Co-authored-by: Avery Black <[email protected]>
  • Loading branch information
@dhinakg @1Revenger1
dhinakg and 1Revenger1 committed Jul 29, 2022
commit a563f7e016f3d30b9cc188443af7373a8a3b7cac
2 changes: 1 addition & 1 deletion universal/pm.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -142,7 +142,7 @@ This final entry is to help macOS out what kind of overall performance you'd lik
Once you're finished, you'll be provided with a CPUFriendDataProvider.kext and ssdt_data.aml. Which you choose is your preference but I recommend the kext variant to avoid any headaches with data injection into Windows and Linux.

* **Note**: Load order does not matter with the CPUFriendDataProvider as it's just a plist-only kext
* **Note 2**: Wake issues resulting from CPUFriend is likely due to incorrect power management data, every system is unique so you'll need to play around until you get a stable config. Kernel panics will have `Sleep Wake failure in efi`. Reusing power management data from old macOS versions can also cause issues, so recreate your data provider if you update macOS.
* **Note 2**: Wake issues resulting from CPUFriend are likely due to incorrect power management data. Every system is unique so you'll need to play around until you get a stable config. Kernel panics will have `Sleep Wake failure in efi`. Reusing power management data from old macOS versions can also cause issues, so recreate your data provider if you update macOS.
* **Note 3**: If you do choose to use ssdt_data.aml, note that SSDT-PLUG is no longer needed. However the setup for this SSDT is broken on HEDT platforms like X99 and X299, so we highly recommend SSDT-PLUG with CPUFriendDataProvider.kext instead.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just an idea following Note 2 - maybe we could mention creating CPUFriendDataProvider_OSVersion.kext and then set Min/MaxKernel such that specific set of power management data is injected for different versions of macOS.


## Sandy and Ivy Bridge Power Management
Expand Down