Several success stories here for OpenCore 0.7.4/0.7.5 setup make a point of noting that with the new AMD patches, we must set our CPU core count correctly. We're instructed to look for the "algrey - Force cpuid_cores_per_package" nodes, and replace values like "BA000000 0090" and insert the hex number representing the number of cores in positions 3 and 4, i.e. "BAC00000 0090".
This is the same information I found online on Dortania.
The problem is that the config.plist files included in these success stories don't show these values anywhere. Sure, there are the three "algrey - Force cpuid_cores_per_package" section, but their "Find" and "Replace" section contain non-hex nonsense strings. Here's the complete Monterey section from one success story here:
<dict>
<key>Arch</key>
<string>x86_64</string>
<key>Base</key>
<string>_cpuid_set_info</string>
<key>Comment</key>
<string>algrey - Force cpuid_cores_per_package 12.0</string>
<key>Count</key>
<integer>1</integer>
<key>Enabled</key>
<true/>
<key>Find</key>
<data>wegaAAAA</data>
<key>Identifier</key>
<string>kernel</string>
<key>Limit</key>
<integer>0</integer>
<key>Mask</key>
<data>//3/AAAA</data>
<key>MaxKernel</key>
<string>21.99.99</string>
<key>MinKernel</key>
<string>21.0.0</string>
<key>Replace</key>
<data>ugwAAACQ</data>
<key>ReplaceMask</key>
<data>////////</data>
<key>Skip</key>
<integer>0</integer>
</dict>
As you can see, the "Find" section contains the non-hex string "wegaAAAA" and the "Replace" section contains the non-hex string "ugwAAACQ". Nowhere does anything like the strings described occur.
Since this issue comes up in several success stories using OpenCore 0.7.x, I'm obviously missing something. But what?
This is the same information I found online on Dortania.
The problem is that the config.plist files included in these success stories don't show these values anywhere. Sure, there are the three "algrey - Force cpuid_cores_per_package" section, but their "Find" and "Replace" section contain non-hex nonsense strings. Here's the complete Monterey section from one success story here:
<dict>
<key>Arch</key>
<string>x86_64</string>
<key>Base</key>
<string>_cpuid_set_info</string>
<key>Comment</key>
<string>algrey - Force cpuid_cores_per_package 12.0</string>
<key>Count</key>
<integer>1</integer>
<key>Enabled</key>
<true/>
<key>Find</key>
<data>wegaAAAA</data>
<key>Identifier</key>
<string>kernel</string>
<key>Limit</key>
<integer>0</integer>
<key>Mask</key>
<data>//3/AAAA</data>
<key>MaxKernel</key>
<string>21.99.99</string>
<key>MinKernel</key>
<string>21.0.0</string>
<key>Replace</key>
<data>ugwAAACQ</data>
<key>ReplaceMask</key>
<data>////////</data>
<key>Skip</key>
<integer>0</integer>
</dict>
As you can see, the "Find" section contains the non-hex string "wegaAAAA" and the "Replace" section contains the non-hex string "ugwAAACQ". Nowhere does anything like the strings described occur.
Since this issue comes up in several success stories using OpenCore 0.7.x, I'm obviously missing something. But what?