New GA-Z790-D and i7-1200KF build advice

Henties · October 5

Hi @all I just about completed the assembly of the following components for a new hackintosh:

GA-Z790-D mobo

i7-1200KF cpu

2 x 32 GiG Corsair Vengeance LPX memory

Red Devil RX 6800 XT Gpu

1 x Samsung EVO 970 500GB NVMe

3 x Samsung EVO 860 SSD;s

2 x WD Black 2TB NVMe's

1 x Noctual NH-D14 air cooler with an adaptor plate for an Intel 1700 socket

1 x EGVA 850 GT Supernova 80 Plus PSU

Apple Magic keyboard V.2

Logitech M705 Marathon mouse

Logitech C370 Webcam

The first initial startup - into Win 11 - is imminent, from where I will do the USB mapping for all the ports

I actually require and deem essential.

Note that, for obvious reasons, I deliberately steered away from the Raptor Lake CPU range.

In order to successfully complete this hack I would appreciate some help and advice about the

recommended bios, P-core, E-Core and hyper threading settings. If my memory serves me correctly

@Miezeis actually running a hack with fairly similar hardware, it would be great if she would share some

of her settings that work in her particular environment. Miau.

On the ACPI side I plan not to rely on a modded all inclusive DSDT file but rather on individually tailored .aml

files placed in the opencore ACPI folder. This measure should allow me more flexibility should it be required to

change something further down the line.

I am already running, quite successfully, 2 x GA-Z490-G mobos each with an Intel i9-10850K processor.

I figure that the transition from a Comet Lake to an Alder Lake environment should not be too challenging.

I am looking forward to any assistance or advice so that this new build can shortly be finalized and placed

into service.

Greetings Henties

Edited October 18 by Henties

MaLd0n · October 5

Bios/UEFI in full default. Just disable secure boot and enable XMP profile. Use last version from gigabyte.

Your EFI folder. Just generate new SMBIOS/Serial EFI Henties.zip

About ACPI i have one crazy topic with one perfect Hack https://olarila.com/topic/41085-insane-acpi-editing-on-hackintosh-like-apple/

DSDT Unpatched with 116984 lines and 553 KB on disk.

DSDT Patched with 5520 lines and 25 KB on disk.

DSDT.MaLd0n z790.zip

xh_rps14 Vanilla USB.aml.zip

Mieze · October 5

@Henties Here are my UEFI settings. I will post the EFI folder later this night after I will have returned home because I have to leave now.

Gigabyte_Z790_D_UEFI_Settings.zip

Mieze · October 5

@Henties ...and here comes the EFI folder as promised in the afternoon. Have fun!

😺

EFI_Gigabyte_Z790_D.zip

Henties · October 5

@MaLd0n and @Mieze thank you both very much especially @Mieze for her detailed BIOS UEFI settings of her GA-Z790 D mobo. This will certainly prove a valuable starting point in my endeavors with this new build of mine.

Still looking forward to have a glimpse at @MiezeEFI later on or tomorrow, before I embark on a round trip of 1000 Km. plus to drop a friend at the airport.

I am somewhat confused with the online documentation that is provided by Gigabyte for this mobo as it shows only 4 Sata ports whereas the mobo I received actually has 6 Sata ports fitted on the mobo. I am aware that this mobo is available with varying features, with the D version, for instance, not having an onboard WjFi/BT module fitted. I am guessing that Gigabyte added 2 additional Sata ports for the board with DDR4 memory slots because the total bandwidth required by the latter is less than what DDR5 type memory would need. Perhaps 6 slots were fitted because this mobo is only sporting 1 x PCIe 16 lane slot, making it possible to use the "free" unused bandwidth, for something else, in due cause will certainly get to t he bone of this particular one.

Thanks again to both of you for your inputs with a big Miau from my beloved "housecat" who would certainly one day love to have me for dinner if I am not carefull.

Greetings Henties

Henties · October 5

@MiezeThanks a lot for the EFI, indeed much appreciated. I thoroughly went through your EFI and immediately discovered that it is quite "lean and mean", indeed the way I prefer it myself.

Most EFI's that I have looked at, originating from the "internet" can be classified as "bloatware" with entries that often do not even remotely relate to the hardware the EFI was actually intended for.

This again will prove to be an excellent starting point for my own build endeavors and the hardware that I am using for my build. I notice that you are also not using a NVMeFix.kext, I also removed that particular kext quite some time ago, from my Comet Lake hacks, with my boot times not being affected noticeably at all. CPUFriend and CPUdataprovider kexts have also not been used, I guess it's because "power management" Is now performed in Bios by properly managing

hyper threading with P–Core and E-Core settings, will read this up shortly to get a better understanding what this is all about.

Greetings Henties.

Henties · October 18

To @all and especially @Mieze.

My new Alder Lake build is now running like a dream, which was indeed achieved in record time and minimal effort on my part, because @Mieze 's Bios settings as well her sample EFI, which she so generously provided, paved the way for me to accomplish the full functionality I am experiencing presently with my new Alder Lake build.

Further down the line I will comment in more detail on what I have done on my side to make this new "hackintosh" buiid working as well as it indeed presently does, especially considering my particular environment.

Thanks @Mieze

Greetings from a humbled and very gratefull Henties. Miau Miau Miau.

MaLd0n · October 18

Just one thing. If u using MacPro7,1 u need to fix power management with cpufriend for best perfomance, with iMacPro1,1 don't need just use CpuTopologyRebuild with -ctrsmt(in both cases)

Henties · October 19

@MaLd0nthank you for your advice. Your Geekbench score reflects performance obtained with a Raptor Lake CPU whereas I have been building my new rig with an Alder Lake CPU. It would be much more beneficial and helpful if one could compare Apples with Apples rather than Apples with Bananas.

I deliberately made a last minute decision, just before purchasing, to go for an Alder Lake CPU because of the well documented problems with Intel's Raptor Lake CPU range. I certainly do not regret my buying decision although I am conscious that I sacrificed the performance gains actually optainable had I opted for a Raptor Lake CPU instead.

I am quite happy with the new rig of mine, stability wise as well as power wise, without CpuFriend etcetera, as I am now typing my CPU die temp hovers around 23 degrees C with the present ambient temperature being merely 16 degrees C.

This new rig is intended to be used for flight simming and I confirm that it lives up to my expectation in that regard as well, with all graphics settings maxed out

I consistently obtain 30 fps and above when flying in the most demanding areas there are being Heathrow and greater London or JFK and New York.

My adage has always been don't fix something that ain't broken, therefore I will for the time being stay without CPUfriend and it;s "soulmate".

Wondering if @Miezewould go along with my comments as well.

Oh forgot to mention that the temps reflected by Intel Power Gadgets are a snapshot of the CPU testing phase with the highest CPU utilization imposed by Geekbench.

Greetings Henties and thank you for participating in this thread.

Edited October 19 by Henties

Mieze · October 19

@Henties @MaLd0n With Xcode being my main application, I haven't even measured single core performance because multicore performance is what matters for me. CPUFriend with frequency vector generated with the recommended settings didn't improve multicore performance at all but had a devastating impact on I/O performance most likely because of increased interrupt latency. Tx speed with IntelLucy dropped from 9.4 Gbit/s without to 7 Gbit/s with CPUFriend. That's why I removed it completely.

What really improved multicore performance was CpuTopologyRebuild without -ctrsmt. My Cinebench R23 score went up from ~18500 to ~22500. Adding -ctrsmt reversed that effect causing it to fall back to ~18500. Without CpuTopologyRebuild Cinebench MC scores were quite unstable. In most cases I got ~18500 with the P-cores maxing out at 3.8 GHz and CPU power consumption was limited to ~125W. In a small number of runs the P-cores reached their maximum turbo frequency with a CPU power consumption of ~180W.

After installing CpuTopologyRebuild I'm getting stable results of ~22500 with the CPU making full use of it's power budget of 190W.

Edited October 19 by Mieze

MaLd0n · October 19

@Mieze, @Henties Just work good with instructions from Vit Here. In some days i made 10 hacks or more in olarila.com and this way for me just work nice in all cases. It's a brutal performance on MacOS. :guitar:

My setup gain 3k+ in some benchs.

Geekbench 18k go to 20.8k/21.5k and cinebench 2024 Version go to 2384.

Mieze · October 19

@MaLd0n Keep in mind that different CPU models have different number of E-Cores which influences the best choice for the CPU topology. With the 12700KF only having 4 E-Cores it isn't possible to create a fully balanced topology.

MaLd0n · October 19

Copied, dear! I haven't actually used 12th gen in a while.

Henties · October 19

@MaLd0n Great, would therefore suggest that you be a bit more "discerning" when commenting to ensure that what you are commenting on actually fits the

hardware being the actual topic under discussion.

It serves no purpose, and just contributes to uncertainty and generates a lot of confusion, when the actual topic of this thread centers around an Intel Alder Lake CPU whereas you find it prudent to throw in your "preferences" relating to a Raptor Lake CPU.

Just my 2 cents, I value your contributions, especially those relating to the hardware I am actually deploying.

Greetings Henties.

Edited October 19 by Henties

MaLd0n · October 19

@Henties Alder Lake and Raptor Lake uses same Hackintosh config. Don't change nothing in both cases and in this case your score is low. You can use your vanilla however you choose, but you're not using the full power of your hardware for now. That's just my 1 cent. :guitar:

Henties · October 19

@all I completed my new build and have attached the EFI currently driving my new hackintosh.

Kindly note that during the creation of the attached EFI I used @Mieze's sample EFI , which

she so generously provided, as a template for the creation of my own, which in turn I have

specifically configured to satisfy the demands of the hardware actually deployed by me.

Some pertinent differences between @Mieze's and my EFI are listed below:

My config.plist sports some minor configuration option changes. Compare and you will

notice where the differences are, one being that I use an icon based boot picker as opposed
to a text based picker.

My USB mapping differs from that which @Mieze decided would suit her best with her

build, using DDR5 memory, whereas I am using DDR4 memory with my build.

Note: The Gigabyte GA-Z790 D mobo is available in 4 different hardware configurations with

the DDR4 version, that I am deploying, being quite different to the DDR5 version of this mobo,

which @Miezeis actually using. Some of the differences manifest themselves in the available

number of USB as well as SATA ports. Go figure.

I mention this to alert anybody that an EFI that you receive from whatever source, must always

first be adapted to the specific needs of the hardware for which it is actually intended.

Just my 2 cents.

A final thanks to @Mieze for making it possible for me to actually progress as quickly as I did with

this new hackintosh now functioning extremely well in all respects that I believe to be important, with

sleep being one of them.

Greetings Henties Miau Miau Miau

EFI 2.zip

Henties · October 19

@MaLd0nI hear what you say but I am quite happy with the processing power currently available as it fully satisfies my intended use.

Why should I try and go for more when that which I am having at my disposal suffices for what I want to accomplish?

Further down the line I might indeed change my mind but at the moment I am content with what I have available in terms processing power,

and all that achieved with minimum "complexity" ie. a fairly lean EFI at the same time ensuring efficient power usage for the task at hand.

Greetings Henties

MaLd0n · October 19

2 minutes ago, Henties said:

@MaLd0nI hear what you say but I am quite happy with the processing power currently available as it fully satisfies my intended use.

That's what matters, bro!
Now just enjoy!!! :guitar:

Henties · October 19

2 hours ago, MaLd0n said:

@Henties Alder Lake and Raptor Lake uses same Hackintosh config.

@MaLd0nI am very skeptical about your statement, because an Alder Lake CPU architecture differs quite drastically from that of a Raptor Lake CPU.

@Miezehas indeed already pointed out the difference in P and E cores between the to CPU types, which in my, as well as @Mieze's considerations necessitates a different "hacking" approach to be employed with these very different CPU architectures.

Greetings Henties

MaLd0n · October 19

All hackintosh files, patches, etc is same for Alder and Raptor. You can use your EFI in both. Just test it. Just pay attention in processors with no E-Cores, you don't need CpuTopology.

Henties · October 19

@MaLd0nGreat news but that became apparent rather late in the game, I indeed use CpuTopology for this hack of mine which seems a requirement for my current hack and the hardware I actually deploy. Please correct me should I be wrong.

Henties · October 20

@all I have attached a revised config.plist file for the EFI folder which I provided earlier.

The only change I applied is in the information header which now reflects accurately what

hardware has actually been installed.

The software information under section #08 still requires to be updated.

Enjoy or destroy.

Greetings Henties

Added the final config.plist for my Alder Lake hack. The only change has been to position #8 of the information header now listing accurately all the third party sofware as well as version numbers, actually installed.

config.plist.zip

Final config.plist.zip

Edited October 20 by Henties
Added updated config.plist

Mieze · October 23

@MaLd0n I gave CPUFriend.kext another try, this time with a minimum frequency of 2000MHz, which is the default, and should be enough to avoid frequency related I/O performance issues. Tests were run against an Ubuntu server 22.04 LTS equipped with an Intel X520, like the client, and this is the result:

laura@Tigresa ~ % iperf3 -w 384K -c 192.168.10.32   
Connecting to host 192.168.10.32, port 5201
[  4] local 192.168.10.95 port 49384 connected to 192.168.10.32 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec  1.09 GBytes  9.39 Gbits/sec                  
[  4]   1.00-2.00   sec  1.09 GBytes  9.40 Gbits/sec                  
[  4]   2.00-3.00   sec  1.09 GBytes  9.39 Gbits/sec                  
[  4]   3.00-4.00   sec  1.09 GBytes  9.40 Gbits/sec                  
[  4]   4.00-5.00   sec  1.09 GBytes  9.39 Gbits/sec                  
[  4]   5.00-6.00   sec  1.09 GBytes  9.33 Gbits/sec                  
[  4]   6.00-7.00   sec  1.08 GBytes  9.27 Gbits/sec                  
[  4]   7.00-8.00   sec  1.09 GBytes  9.35 Gbits/sec                  
[  4]   8.00-9.00   sec  1.09 GBytes  9.40 Gbits/sec                  
[  4]   9.00-10.00  sec  1.09 GBytes  9.40 Gbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-10.00  sec  10.9 GBytes  9.37 Gbits/sec                  sender
[  4]   0.00-10.00  sec  10.9 GBytes  9.37 Gbits/sec                  receiver

iperf Done.
laura@Tigresa ~ % iperf3 -w 384K -c 192.168.10.32 -R
Connecting to host 192.168.10.32, port 5201
Reverse mode, remote host 192.168.10.32 is sending
[  4] local 192.168.10.95 port 49386 connected to 192.168.10.32 port 5201
[ ID] Interval           Transfer     Bandwidth
[  4]   0.00-1.00   sec   220 MBytes  1.85 Gbits/sec                  
[  4]   1.00-2.00   sec   222 MBytes  1.86 Gbits/sec                  
[  4]   2.00-3.00   sec   219 MBytes  1.84 Gbits/sec                  
[  4]   3.00-4.00   sec   204 MBytes  1.71 Gbits/sec                  
[  4]   4.00-5.00   sec   207 MBytes  1.74 Gbits/sec                  
[  4]   5.00-6.00   sec   217 MBytes  1.82 Gbits/sec                  
[  4]   6.00-7.00   sec   208 MBytes  1.74 Gbits/sec                  
[  4]   7.00-8.00   sec   266 MBytes  2.23 Gbits/sec                  
[  4]   8.00-9.00   sec   277 MBytes  2.33 Gbits/sec                  
[  4]   9.00-10.00  sec   228 MBytes  1.91 Gbits/sec                  
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-10.00  sec  2.21 GBytes  1.90 Gbits/sec    0             sender
[  4]   0.00-10.00  sec  2.21 GBytes  1.90 Gbits/sec                  receiver

Note the lousy receive performance which used to be > 9.8 Gbit/s without CPUFriend. Creating the data provider I used the following values:

Min. Frequency: 14 (2000 MHz)
Energy Performance Preference (EPP): 00 (Performance)
Perf Bias: 0x01 (Modern iMac)
Selected NO for the other energy related features:

Henties · October 24

@Mieze oh you jumped me to this. I did similar tests on my DDR 4 board and came to the same conclusion. Deploying CPUFriend and its dataprovider actually has noticeable detrimental performance effects on my system confirmed by the output of actual measured results, as well as the increased duration it takes to CCC-clone a macOS volume to a spare SSD when using CPUFriend, compared to the much shorter period to CCC-clone the the same macOS volume to the same SSD but this time without CPUfriend, say nop more.

As I mentioned in an earlier posting, the performance without CPUFriend is more than adequate, in my particular "use" environment, I am flying my planes in my X-Plane 12 simulator with all settings maxed out, with frames per second to spare, even when flying around the most resource demanding areas one can think of, being Heathrow and greater London as well as JFK and New York. What pleases me most is that the system as well as core temperatures remain within very reasonable limits never even approaching 80 degrees celsius. One must not forget that for every 10 degrees Celsius that electronic equipment runs cooler the MBTF (mean time between failure) doubles.

Also to be considered is that my GA-Z790 D DDR4 mobo cannot reach the same performance level as the same board variant with DDR5 memory, something I was actually aware of when I made my purchasing decisions opting to rather use some equipment that I already had available in my "treasure box", or was it junk box? than going for the latest and or greatest available. Another purchasing decision I consciously made was opting for a 12 th. gen. Intel Alder Lake ..KF cpu as opposed to one from the much more powerful Intel Raptor Lake range.

Overall I am as happy as a pig in a pool of muck with my latest addition to my hackintosh stable.

Greetings Henties

MaLd0n · October 24

@Henties If performance has dropped overall with CPUFriend, the kext was generated incorrectly.

Some examples of how this pair works much better, but if there is any side effect as Mieze mentioned, we have to weigh it up and see what is best in each case. My clients are basically Audio and Video editors and programmers. In these cases I use a very basic SSDT with the same patches used since 2009 or something like that and updated as Apple released new computers with new hardware with new ACPI things, which nowadays they insist on saying that these patches appeared in 2018, they just transformed it into SSDT and added a header.

My personal SSDT MiNi.600.700.aml.zip

My personal EFI folder EFI MaLd0n.zip

With CPUFriend + CpuTopologyRebuild + -ctrsmt (Credits to Vit9696 and b00t0x for this hard work)

With NO CPUFriend but with CpuTopologyRebuild + -ctrsmt

With iMacPro1,1 Smbios With CPUFriend + CpuTopologyRebuild + -ctrsmt.

With NO CPUFriend + CpuTopologyRebuild + -ctrsmt the result is same, but with CPUFriend for video Encoder/Decoder the performance improves a lot.

@Henties We see the word bloatware in this topic, but the proof is even in your EFI folder. You are using an SSDT with more than a thousand lines for a simple patch.

Quote

Scope (\_SB)
{
Processor (CP00, 0x00, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, Zero) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}

Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method
{
If (!Arg2)
{
Return (Buffer (One)
{
0x03 // .
})
}

Return (Package (0x02)
{
"plugin-type",
One
})
}
}

Processor (CP01, 0x01, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, One) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP02, 0x02, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x02) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP03, 0x03, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x03) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP04, 0x04, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x04) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP05, 0x05, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x05) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP06, 0x06, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x06) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP07, 0x07, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x07) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP08, 0x08, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x08) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP09, 0x09, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x09) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP0A, 0x0A, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x0A) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP0B, 0x0B, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x0B) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP0C, 0x0C, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x0C) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP0D, 0x0D, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x0D) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP0E, 0x0E, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x0E) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP0F, 0x0F, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x0F) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP10, 0x10, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x10) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP11, 0x11, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x11) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP12, 0x12, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x12) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP13, 0x13, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x13) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP14, 0x14, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x14) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP15, 0x15, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x15) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP16, 0x16, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x16) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP17, 0x17, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x17) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP18, 0x18, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x18) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP19, 0x19, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x19) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP1A, 0x1A, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x1A) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP1B, 0x1B, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x1B) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP1C, 0x1C, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x1C) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP1D, 0x1D, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x1D) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP1E, 0x1E, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x1E) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP1F, 0x1F, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x1F) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP20, 0x20, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x20) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP21, 0x21, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x21) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP22, 0x22, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x22) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP23, 0x23, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x23) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP24, 0x24, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x24) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP25, 0x25, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x25) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP26, 0x26, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x26) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP27, 0x27, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x27) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP28, 0x28, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x28) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP29, 0x29, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x29) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP2A, 0x2A, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x2A) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP2B, 0x2B, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x2B) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP2C, 0x2C, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x2C) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP2D, 0x2D, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x2D) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP2E, 0x2E, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x2E) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP2F, 0x2F, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x2F) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP30, 0x30, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x30) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP31, 0x31, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x31) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP32, 0x32, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x32) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP33, 0x33, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x33) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP34, 0x34, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x34) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP35, 0x35, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x35) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP36, 0x36, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x36) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP37, 0x37, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x37) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP38, 0x38, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x38) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP39, 0x39, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x39) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP3A, 0x3A, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x3A) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP3B, 0x3B, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x3B) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP3C, 0x3C, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x3C) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP3D, 0x3D, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x3D) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP3E, 0x3E, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x3E) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}

Processor (CP3F, 0x3F, 0x00000510, 0x06)
{
Name (_HID, "ACPI0007" /* Processor Device */) // _HID: Hardware ID
Name (_UID, 0x3F) // _UID: Unique ID
Method (_STA, 0, NotSerialized) // _STA: Status
{
If (_OSI ("Darwin"))
{
Return (0x0F)
}
Else
{
Return (Zero)
}
}
}
}

Here is a patch updated to improve this horrible and bloatware thing.

Quote

Scope (\_SB)
{
Processor (CP00, 0x00, 0x00000510, 0x06){}
Processor (CP01, 0x01, 0x00000510, 0x06){}
Processor (CP02, 0x02, 0x00000510, 0x06){}
Processor (CP03, 0x03, 0x00000510, 0x06){}
Processor (CP04, 0x04, 0x00000510, 0x06){}
Processor (CP05, 0x05, 0x00000510, 0x06){}
Processor (CP06, 0x06, 0x00000510, 0x06){}
Processor (CP07, 0x07, 0x00000510, 0x06){}
Processor (CP08, 0x08, 0x00000510, 0x06){}
Processor (CP09, 0x09, 0x00000510, 0x06){}
Processor (CP10, 0x0A, 0x00000510, 0x06){}
Processor (CP11, 0x0B, 0x00000510, 0x06){}
Processor (CP12, 0x0C, 0x00000510, 0x06){}
Processor (CP13, 0x0D, 0x00000510, 0x06){}
Processor (CP14, 0x0E, 0x00000510, 0x06){}
Processor (CP15, 0x0F, 0x00000510, 0x06){}
Processor (CP16, 0x10, 0x00000510, 0x06){}
Processor (CP17, 0x11, 0x00000510, 0x06){}
Processor (CP18, 0x12, 0x00000510, 0x06){}
Processor (CP19, 0x13, 0x00000510, 0x06){}
Processor (CP20, 0x14, 0x00000510, 0x06){}
Processor (CP21, 0x15, 0x00000510, 0x06){}
Processor (CP22, 0x16, 0x00000510, 0x06){}
Processor (CP23, 0x17, 0x00000510, 0x06){}
Processor (CP24, 0x18, 0x00000510, 0x06){}
Processor (CP25, 0x19, 0x00000510, 0x06){}
Processor (CP26, 0x1A, 0x00000510, 0x06){}
Processor (CP27, 0x1B, 0x00000510, 0x06){}
Processor (CP28, 0x1C, 0x00000510, 0x06){}
Processor (CP29, 0x1D, 0x00000510, 0x06){}
Processor (CP30, 0x1E, 0x00000510, 0x06){}
Processor (CP31, 0x1F, 0x00000510, 0x06){}
}

Be careful with these people who came after the opencore manual, they read the manual and now they think they are the best hackintoshers on the planet.

Remember that there is no "Paradise" and no "Little" things. :lol:

New GA-Z790-D and i7-1200KF build advice

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites