Contribute
Register

Z690 Chipset Motherboards and Alder Lake CPU

@StefanAM, @Romanychev Thanks! I've seen the ghosts!

Throughout the P-cores and their hyperthreads, all is fine. First E-core (from 12900K):View attachment 536455
'processor-id' and 'processor-number are in sync. Then the next E-core:
View attachment 536456
'processor-id' keeps with the sequence (as defined in SSDT) but 'processor-number', which should be an OS X-generated alternate index, has jumped by two units! 'Processor-number' 0x11 is nowhere to be found.
This goes on with the remaining cores, and eventually the last processors are not initialised.

There are no such jumps or loss of synchronicity in a previous IOReg with P+E cores (no HT).

Mad Scientist proposal: What happens if the "effective" numbers are raised in the kernel patch?
Replace: B8 28 00 14 00 31 D2 for i9-12900K
Replace: B8 1C 00 0E 00 31 D2 for i7-12700K
Replace: B8 18 00 0C 00 31 D2 for i5-12600K
(Most likely the hack no longer boots because the patch does not match the actual CPU, or the limiting counter is not there—or is only one of the two patched instances.)
12700k, no boot
 
@StefanAM, @Romanychev Thanks! I've seen the ghosts!

Throughout the P-cores and their hyperthreads, all is fine. First E-core (from 12900K):View attachment 536455
'processor-id' and 'processor-number are in sync. Then the next E-core:
View attachment 536456
'processor-id' keeps with the sequence (as defined in SSDT) but 'processor-number', which should be an OS X-generated alternate index, has jumped by two units! 'Processor-number' 0x11 is nowhere to be found.
This goes on with the remaining cores, and eventually the last processors are not initialised.

There are no such jumps or loss of synchronicity in a previous IOReg with P+E cores (no HT).

Mad Scientist proposal: What happens if the "effective" numbers are raised in the kernel patch?
Replace: B8 28 00 14 00 31 D2 for i9-12900K
Replace: B8 1C 00 0E 00 31 D2 for i7-12700K
Replace: B8 18 00 0C 00 31 D2 for i5-12600K
(Most likely the hack no longer boots because the patch does not match the actual CPU, or the limiting counter is not there—or is only one of the two patched instances.)

Hey @etorix, I tested it with your Kernel Patch suggestion (B8 28 00 14 00 31 D2), but without success, on 12900k 4 cores remain without activating.

cores-active.png


Kernel Patch:

kernel-patch.png


we continue in the saga of activating all cores LOL!
 
@StefanAM, @Romanychev Thanks! I've seen the ghosts!

Throughout the P-cores and their hyperthreads, all is fine. First E-core (from 12900K):View attachment 536455
'processor-id' and 'processor-number are in sync. Then the next E-core:
View attachment 536456
'processor-id' keeps with the sequence (as defined in SSDT) but 'processor-number', which should be an OS X-generated alternate index, has jumped by two units! 'Processor-number' 0x11 is nowhere to be found.
This goes on with the remaining cores, and eventually the last processors are not initialised.

There are no such jumps or loss of synchronicity in a previous IOReg with P+E cores (no HT).

Mad Scientist proposal: What happens if the "effective" numbers are raised in the kernel patch?
Replace: B8 28 00 14 00 31 D2 for i9-12900K
Replace: B8 1C 00 0E 00 31 D2 for i7-12700K
Replace: B8 18 00 0C 00 31 D2 for i5-12600K
(Most likely the hack no longer boots because the patch does not match the actual CPU, or the limiting counter is not there—or is only one of the two patched instances.)
I did this today morning with the following values: 18-30, 14-28. No boot!

Maybe DSM method support to insert 'processor-id' and 'processor-number'.
 
Almost finished my build! Mini ITX 12700K Incoming!
Guys I need help

Today the new WIFI/BT Module arrived:
arrived and I replaced the one that came with my Z690I with the new one

Could not make WiFi Work on windows (I'm trying to set everything up on Windows before trying macOS)
Bluetooth Works, but Wifi doesn't. Windows update could not find the matching driver, when I tried installing the driver from the following page:

I got the following
1638812736276.png


Does anyone has experience with this specific module?
Ordered it from here

Note that it has 3 Antennas connections, I connected my 2 available to J1, J2.
Could this be the issue?

The Module that came with the board is AX201NGW
Thanks for the help!
 
Almost finished my build! Mini ITX 12700K Incoming!
Guys I need help

Today the new WIFI/BT Module arrived:
arrived and I replaced the one that came with my Z690I with the new one

Could not make WiFi Work on windows (I'm trying to set everything up on Windows before trying macOS)
Bluetooth Works, but Wifi doesn't. Windows update could not find the matching driver, when I tried installing the driver from the following page:

I got the following
View attachment 536473

Does anyone has experience with this specific module?
Ordered it from here

Note that it has 3 Antennas connections, I connected my 2 available to J1, J2.
Could this be the issue?

The Module that came with the board is AX201NGW
Thanks for the help!
Try this:
 

Attachments

  • Arhivă.zip
    15.2 MB · Views: 53
Almost finished my build! Mini ITX 12700K Incoming!
Guys I need help

Today the new WIFI/BT Module arrived:
arrived and I replaced the one that came with my Z690I with the new one

Could not make WiFi Work on windows (I'm trying to set everything up on Windows before trying macOS)
Bluetooth Works, but Wifi doesn't. Windows update could not find the matching driver, when I tried installing the driver from the following page:

I got the following
View attachment 536473

Does anyone has experience with this specific module?
Ordered it from here

Note that it has 3 Antennas connections, I connected my 2 available to J1, J2.
Could this be the issue?

The Module that came with the board is AX201NGW
Thanks for the help!

Hi there.

Not 100% sure but if your motherboard is Gigabyte then the wireless card slot may be locked to CNVI-only. If ASUS then it should be okay in an adapter.

If you have an m.2 socket, front or back, you may be able to use that instead and disable the Intel.

Happy to be proved wrong.
 
@StefanAM, @Romanychev Thanks! I've seen the ghosts!

Throughout the P-cores and their hyperthreads, all is fine. First E-core (from 12900K):
'processor-id' and 'processor-number are in sync. Then the next E-core:

'processor-id' keeps with the sequence (as defined in SSDT) but 'processor-number', which should be an OS X-generated alternate index, has jumped by two units! 'Processor-number' 0x11 is nowhere to be found.
This goes on with the remaining cores, and eventually the last processors are not initialised.

There are no such jumps or loss of synchronicity in a previous IOReg with P+E cores (no HT).

Mad Scientist proposal: What happens if the "effective" numbers are raised in the kernel patch?
Replace: B8 28 00 14 00 31 D2 for i9-12900K
Replace: B8 1C 00 0E 00 31 D2 for i7-12700K
Replace: B8 18 00 0C 00 31 D2 for i5-12600K
(Most likely the hack no longer boots because the patch does not match the actual CPU, or the limiting counter is not there—or is only one of the two patched instances.)
@etorix,

macOS will in fact boot on i5-12600K if we use this instead:

Replace: B8 1C 00 0E 00 31 D2 for i5-12600K

This is based on the following:
  • 6 P-cores + Hyper Threads = 12 threads
  • 4 E-cores
  • 4 more E-cores (because half the E-cores are uninitialized, assume there are twice as many)
Now we have 6 + 4 + 4 = 14 (0x0E) cores. Multiply by 2 for total threads = 28 (0x1C).

This at least allows macOS to boot, but the result is unchanged from before. We still get 16 threads total with 2 being uninitialized.
 
Hi there.

Not 100% sure but if your motherboard is Gigabyte then the wireless card slot may be locked to CNVI-only. If ASUS then it should be okay in an adapter.

If you have an m.2 socket, front or back, you may be able to use that instead and disable the Intel.

Happy to be proved wrong.
Unfortunately, I'm using both M.2 sockets for an NVMe drive.
I do have a Gigabyte, Z690i Aorus.
If this is the case, how come Bluetooth works?

Here are the adapter properties.
Still fails with Code 10, I believe I have the wrong driver
1638814915334.png
 
Back
Top