[HOW TO] Wi-Fi 6 Intel AX210 on macOS Sonoma

[Cosmix]

Innie.kext tells macOS to treat internal drives as internal, not as external, as is sometimes the case.

Thanks @Edhawk,

" ... internal drives" : Do you mean HDD, SSD , Nvme drives ?
" ...is sometimes the case" : Is this "case" a matter of cosmetics(visual), performance, speed, stability, compatibility, annoyance, confusion, etc ?

I have never used it, I hope it will never come into my sight !
Cheers

 

[Funnyland]

@Cosmix

Which function does the Hackintool under PCI have a magnifying glass in front of?

Can you use this to assign kexts?

 

[Cosmix]

So in the meantime I just updated Ventra from Sonoma.

... Ventura from Sonoma ? Not the other way around ?

Strangely enough, it works better with the EFI I have than doing a clean install. Much more liquid.

So you have multiple EFIs... you must keep track of them

But no matter: Innie.kext has been there the whole time.

Ok. Test your system with and without Innie.kext .... See which variant fits.

Of course I also installed the corresponding Airportltlwm Sonoma 2.3.0 but there is no improvement with the old one.

So... you upgraded to Sonoma and installed the "recommended" kext !!!

As a test, I deactivated BT and Lan once, but that didn't work

Bottom line : no matter the macOS version (Ventura, Sonoma) your Intel WiFi card is not working !

Are all your .aml files generated by SSDTTime under Windows OS ?

After editing the EFI's stuff, do not forget to reset nvram ...

 

[Funnyland]

... Ventura from Sonoma ? Not the other way around ?

So you have multiple EFIs... you must keep track of them

Ok. Test your system with and without Innie.kext .... See which variant fits.

So... you upgraded to Sonoma and installed the "recommended" kext !!!

Bottom line : no matter the macOS version (Ventura, Sonoma) your Intel WiFi card is not working !

Are all your .aml files generated by SSDTTime under Windows OS ?

After editing the EFI's stuff, do not forget to reset nvram ...

I deleted the other EFI so as not to mix things up.

I think I have the error: I didn't create .aml files and ssdttim under Windows.

Do you have any clear instructions for me? I think I have to catch up. ??

I've always done NVRAM

I just took the EFI and I think that was wrong.

Excuse me

 

[Cosmix]

@Cosmix

Which function does the Hackintool under PCI have a magnifying glass in front of?

Can you use this to assign kexts?

In Hackintool, PCIe tab, you can inspect important info related to existing devices. Nothing more.
In the first column there is an

icon, but it is greyed out. Not useful.

 

[Cosmix]

I deleted the other EFI so as not to mix things up.

I think I have the error: I didn't create .aml files and ssdttim under Windows.

Do you have any clear instructions for me? I think I have to catch up. ??

I've always done NVRAM

I just took the EFI and I think that was wrong.

Excuse me

In Windows, you must download SSDTTime archieve :

GitHub - corpnewt/SSDTTime: SSDT/DSDT hotpatch attempts.

SSDT/DSDT hotpatch attempts. Contribute to corpnewt/SSDTTime development by creating an account on GitHub.

github.com

Run it and generate all .aml files that can be generated !

 

[Funnyland]

I've done that and now I have a whole folder with a lot of data in it, but where does it have to go? or what do I have to do with it

 

[Cosmix]

I've done that and now I have a whole folder with a lot of data in it, but where does it have to go? or what do I have to do with it

Save your OLD .aml files from your EFI/OC/ACPI folder ( ACPI should be an empty folder )
Use a USB stick to transfer all new .aml files into the empty ACPI folder.

Using a tool ( ProperTree ) you should add to your config the data from patches_OC.plist (info related to your new .aml files)

 

[Funnyland]

Hmmm the translation into my language makes Google very incomprehensible.

Unfortunately I don't understand what you mean

 

[Cosmix]

Hmmm the translation into my language makes Google very incomprehensible.

Unfortunately I don't understand what you mean

Your EFI/OC/ACPI should look like this :

and your config.plist should start like this :