Jump to content
16 posts in this topic

Recommended Posts

Hi there.

I have a 9940X (skylake X). Is it interesting, necessary to use in Kernel/Emulate the cpuid data and cpuid mask.

If I'm not mistaken, it corresponds to this for my processor:

CPUID           Skylake-X 0x050654

Cpuid1Data   <->  57060500 00000000 00000000 00000000

Cpuid1Mask  <->   FFFFFFFF 00000000 00000000 00000000

Thank you for your answers and advice.

Link to comment
https://www.insanelymac.com/forum/topic/352378-cpuid-in-opencore-useful-or-not/
Share on other sites

@Olroy

Since your processor doesn't have native support in macOS you have to use a FakeCPUID (or use the mask) from a supported processor but once macOS is installed or loaded you can use the full potential of your processor.

You can use any value for Cpuid1Data and CpiidMask1 as long as they are supported by macOS.

 

For instance I use these values for my AlderLake processor which has no native support:

Cpuid1Data: 55060A00 00000000 00000000 00000000

CpiidMask1: FFFFFFFF 00000000 00000000 00000000

  • Like 1
1 minute ago, etorix said:

Skylake-X is natively supported (iMacPro).

iMacPro's come in four configurations and all of the have Xeon Processors:

1. 3.2 GHz 8-Core Xeon W-2140B

2. 3.0 GHz 10-Core Xeon W-2150B

3. 2.5 GHz 14-Core Xeon W-2170B

4. 2.3 GHz 18-Core Xeon W-2191B

 

They are built on Skylake server microarchitecture but they have different CPUID than Skylake-X.

  • Like 1

Actually Skylake-X, Skylake-W (iMacPro1,1), Cascade Lake-X, and Cascade Lake-W (MacPro7,1) and 1st/2nd gen. Xeon Scalable all share a CPUID.

Compared with mainstream desktop processors, these CPUs typically require some TSCSync kext and boot argument npci=0x2000, but no spoofing.

 

It's even in the Dortania documentation:

https://dortania.github.io/OpenCore-Install-Guide/config-HEDT/skylake-x.html#kernel

Quote

Emulate

Needed for spoofing unsupported CPUs, thankfully both Skylake-X and Cascade Lake-X have the same CPU ID as Xeon W chips which ship in the iMac Pro. So here we'll leave it blank.

 

Edited by etorix
  • Like 1

@etorix @Olroy

So in that case using Cpuid1Data and CpiidMask1 isn't necessary.

You remove the and boot into macOS, if it starts to lead the you don't need them otherwise you might have to use them after all.

With a X299 / C621 system the Dortania guide is not sufficient to get you running but it is a good start. Then you have to tackle additional issues one at a time. (Or find someone with the same motherboard in X299 threads…)

If you do it by yourself, I suggest to begin by dumping ACPI tables and making your own SSDTs. Consider everything which may apply (for instance, you may find that the DSDT has a PMC device which may actually allow for native NVRAM).

Hello. I use SSDTTime, but I don't know which SSDTs are useful for X299 motherboards and mine in particular. Especially to be able to use the built-in Thunderbolt 3 card. So, yes, I looked at the forums for information. I made a first version of an EFI that I will test. On the other hand, I find that the Dortania site is not very well done: I had to ask for information on insalenymac to realize that I was not in the right place: skylakeX/W CascadeX/W (mac os 10.13 minimum). I was on the sylake (mac os 10.11 minimum).

Well, the page "Skylake-X/W and Cascade Lake-X/W" seems to be an easy match for your Skylake-X CPU… I would not question the quality of Dortania's documentation on that one. :whistle:

 

The best way to make SSDTs is to dump the ACPI tables (Clover F4; OpenCore DEBUG Misc>Debug>SysReport:true) and to study them with the help of the very well written documentation by Dortania and of the ACPISample source code to find what is applicable.

https://dortania.github.io/Getting-Started-With-ACPI/

 

The lazy way is to search the Web for any guide for your very specific board.

 

Make it boot first, and keep Thunderbolt for a later stage. The best documentation for this is to be found in another forum Which-Shall-Not-Be-Named-Here.

8 minutes ago, Olroy said:

EFI/OC/Drivers/ResetNvramEntry.efi is only used for monterey installation? Can we remove it after installation and then copy the EFI to the NVME ?

don't remove it. u can use it to reset nvram on boot picker

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...