Experimental Fork of OCLP 3.0.0 Nightly – modern Wi-Fi, AWDL and AppleHDA Fully Working under Tahoe

[Max.1974]

Excellent work, everyone!! 😄 

[kgp]

Post 1 and both Github repository READMEs have been completely reworked and synchronised.

 

The documentation now clearly defines:

 

- Hackintosh-only scope

- preserved OCLP 3.0.0 Nightly baseline

- no additional unsupported-Mac graphics patch frameworks

- minimal code modifications only

- distinction between the Preserved Reference Edition and the amfipassbeta Edition

- Credits and repository roles were also clarified accordingly. 👍

 

For details see:

 

1.) 

 

2.) https://github.com/kgp-macPro/OCLP-lzhoang2801-amfipassbeta

 

3.) https://github.com/kgp-macPro/OCLP-lzhoang2801

Edited May 6 by kgp

[kgp]

Update of Post 1: document IntelMausi.kext v1.0.8 compatibility issue with IOSkywalkFamily replacement - use IntelMausiEthernet.kext v3.0.0 instead!

Edited May 9 by kgp

[kgp]

Success with OCLP Nightly and AirportItlwm.kext on Lenovo P17 gen 1 with Intel AX201 CNVW under Tahoe 26.5! 

 

Original ACPI path, Intel IOName and Device Path in Hackintool:

 

 

Modified ACPI path (SSDT) and new Intel IOName (Broadcom spoofing via DeviceProperties in config.plist):

 

 

Modified ACPI properties in IOREG:

 

 

System Information:

 

 

Wi-Fi:

 

 

Bluetooth:

 

 

Link to the final EFI-Folder with removed SMBIOS-credentials.

 

Many thanks to @jkaul59 for the fruitful collaboration via PM 

 

 

 

Edited May 24 by kgp
Linking final EFI-Folder

[mengshi]

On 5/24/2026 at 2:01 AM, kgp said:

Success with OCLP Nightly and AirportItlwm.kext on Lenovo P17 gen 1 with Intel AX201 CNVW under Tahoe 26.5! 

 

Original ACPI path, Intel IOName and Device Path in Hackintool:

 

 

Modified ACPI path (SSDT) and new Intel IOName (Broadcom spoofing via DeviceProperties in config.plist):

 

 

Modified ACPI properties in IOREG:

 

 

System Information:

 

 

Wi-Fi:

 

 

Bluetooth:

 

 

Link to the final EFI-Folder with removed SMBIOS-credentials.

 

Many thanks to @jkaul59 for the fruitful collaboration via PM 

 

 

 

 

Airdrop is shown as supported. Does it work or is it just a spoof?

 

[deeveedee]

@mengshi I stand corrected - see kgp's response below and please accept my  apology if this inconvenienced you in any way.

 

================

 

Intel Wi-Fi has its limitations.  See here.  Handoff and Universal Clipboard are the only supported Continuity features.  I use Intel Wi-Fi with itlwm/Heliport because I need high-compatibility with Windows 11 and Linux Ubuntu (triple-boot macOS, Windows 11, Linux) I don't want to inject root-patches and I want SIP to be as restrictive as possible (my own personal reasons).

Edited May 25 by deeveedee

[kgp]

1 hour ago, deeveedee said:

@mengshi Intel Wi-Fi has its limitations.  See here.  Handoff and Universal Clipboard are the only supported Continuity features.  I use Intel Wi-Fi with itlwm/Heliport because I need high-compatibility with Windows 11 and Linux Ubuntu (triple-boot macOS, Windows 11, Linux) I don't want to inject root-patches and I want SIP to be as restrictive as possible (my own personal reasons).

 

@deeveedee, your statement is totally wrong.

 

First of all, we are talking about AirDrop — and likely also AirPlay and Screen Mirroring — which are AWDL features, not Continuity features like Handoff or Universal Clipboard.

 

Secondly, I have been proving for more than half a year now that Intel Wi-Fi chipsets can fully support AWDL features under Tahoe when using the full combination of OCLP, Broadcom spoofing, Ventura AirportItlwm.kext and the com.apple.iokit.IOSkywalkFamily replacement.

 

AirportItlwm.kext alone would not even allow Wi-Fi functionality under Tahoe. To make Intel Wi-Fi work properly under Tahoe, you additionally need OCLP with Broadcom spoofing and the related framework support.

 

I know that you personally prefer not to use this approach, which is perfectly fine. However, please avoid making inaccurate statements like the one above, as they simply do not reflect the current state of development and real-world testing.

 

You made me write this at 4 a.m. in the morning 😉

Edited May 25 by kgp

[deeveedee]

@kgp Airportitlwm supports airdrop?  if so, that's very cool and something I didn't know. I gladly stand corrected.

 

My response was not because I have an agenda as you implied and which I don't appreciate. It was because it was what I believed. I'm human. I make mistakes. Then I apologize.

Edited May 25 by deeveedee

[kgp]

11 minutes ago, deeveedee said:

@kgp' totally' is a bold statement. So you are saying that Airportitlwm supports airdrop?

 

I am saying that AirportItlwm.kext alone does not work at all under Tahoe — not even for basic Wi-Fi functionality.

 

The complete combination of OCLP, Broadcom spoofing, AirportItlwm.kext (Ventura) and the com.apple.iokit.IOSkywalkFamily replacement is required to make Intel Wi-Fi work properly under Tahoe.

 

And on top of that, AWDL features like AirDrop, AirPlay and Screen Mirroring are additionally supported with this approach.

 

If you do not believe it, simply make your own experience with the latter setup. You already have all ingredients to do so 😉

Edited May 25 by kgp

[deeveedee]

I said I believe you and said it is cool that it works. Not sure what else to say. It happens.

[kgp]

7 minutes ago, deeveedee said:

I said I believe you and said it is cool that it works. Not sure what else to say. It happens.

 

No worries 🙂

[kgp]

Post #1 fully reorganized with indexing and a structured table of contents.

[kalkmann]

Hello @kgp,
 

I had never really looked into these patches before, but I came across your post about Lenovo P17 gen 1 with Intel AX201 CNVW, got curious, and decided to give it a try.
 

I have an Intel AX210 on a Lenovo Legion 5-15ACH6A (Ryzen 5600H + Radeon RX 6600M) running Tahoe 26.5.
 

I believe I followed the instructions correctly and managed to achieve the same results shown in your screenshots, including having Wi-Fi working in what appears to be "native mode".
 

From the tests I performed:

• AirPlay from iPhone to Hack works.
• Universal Clipboard works from iPhone to Hack.
• Continuity works, and Safari tabs from my iPhone are shown on the Hack.

However, I could not get the following features to work:

• AirDrop (in either direction)
• Personal Hotspot
• iPhone Camera (Continuity Camera)
• iPhone Mirroring
• iPhone Notifications

Are these results expected and consistent with the current state of the patches, or is it possible that I missed something during the setup?

Thank you for all the effort you've put into this project and this ongoing battle. Take care!

Edited May 29 by kalkmann

[kgp]

50 minutes ago, kalkmann said:

Hello @kgp,
 

I had never really looked into these patches before, but I came across your post about Lenovo P17 gen 1 with Intel AX201 CNVW, got curious, and decided to give it a try.
 

I have an Intel AX210 on a Lenovo Legion 5-15ACH6A (Ryzen 5600H + Radeon RX 6600M) running Tahoe 26.5.
 

I believe I followed the instructions correctly and managed to achieve the same results shown in your screenshots, including having Wi-Fi working in what appears to be "native mode".
 

From the tests I performed:

• AirPlay from iPhone to Hack works.
• Universal Clipboard works from iPhone to Hack.
• Continuity works, and Safari tabs from my iPhone are shown on the Hack.

However, I could not get the following features to work:

• AirDrop (in either direction)
• Personal Hotspot
• iPhone Camera (Continuity Camera)
• iPhone Mirroring
• iPhone Notifications

Are these results expected and consistent with the current state of the patches, or is it possible that I missed something during the setup?

Thank you for all the effort you've put into this project and this ongoing battle. Take care!

 

 

Hi my friend!

First of all, thank you for your trust in OCLP and for taking the time to test this setup.

And congratulations on getting everything working almost exactly as expected!

 

AirDrop, AirPlay and Screen Mirroring (AWDL) should normally work in both directions when the setup is fully functional.

If AirDrop works from your Hack but not from other devices back to the Hack, I would suggest trying point 11.5 of the General Troubleshooting Notes in Post #1.

 

On my own Intel AX210 test system, Personal Hotspot from the iPhone was also working correctly.

 

Regarding Continuity features, Handoff and Universal Clipboard are currently the two features I have personally verified working on Intel Wi-Fi systems.

 

Could you clarify what exactly you mean by "iPhone Mirroring" and "Continuity Camera"?

 

- Phone Mirroring is unfortunately not available for testing in my country, so I have not been able to verify that functionality myself.

 

- By "Continuity Camera", do you mean using the iPhone as a webcam for FaceTime, Zoom, Teams, etc.?

Interestingly, I have just tested Continuity Camera successfully for the first time on my own Tahoe system using an iPhone 16 Pro and a BCM943602CDP Broadcom Wi-Fi card.

 

 

Therefore I would be interested to know whether this feature is working or failing on your Intel AX210 setup.

 

One feature that currently does not work on my systems is Sidecar. So far I have not been able to get Sidecar working with either Broadcom or Intel Wi-Fi and my iPad Pro M4 under Tahoe.

 

Cheers,
KGP 👍

Edited May 29 by kgp

[kalkmann]

7 hours ago, kgp said:

 

 

Hi my friend!

First of all, thank you for your trust in OCLP and for taking the time to test this setup.

And congratulations on getting everything working almost exactly as expected!

 

AirDrop, AirPlay and Screen Mirroring (AWDL) should normally work in both directions when the setup is fully functional.

If AirDrop works from your Hack but not from other devices back to the Hack, I would suggest trying point 11.5 of the General Troubleshooting Notes in Post #1.

 

On my own Intel AX210 test system, Personal Hotspot from the iPhone was also working correctly.

 

Regarding Continuity features, Handoff and Universal Clipboard are currently the two features I have personally verified working on Intel Wi-Fi systems.

 

Could you clarify what exactly you mean by "iPhone Mirroring" and "Continuity Camera"?

 

- Phone Mirroring is unfortunately not available for testing in my country, so I have not been able to verify that functionality myself.

 

- By "Continuity Camera", do you mean using the iPhone as a webcam for FaceTime, Zoom, Teams, etc.?

Interestingly, I have just tested Continuity Camera successfully for the first time on my own Tahoe system using an iPhone 16 Pro and a BCM943602CDP Broadcom Wi-Fi card.

 

 

Therefore I would be interested to know whether this feature is working or failing on your Intel AX210 setup.

 

One feature that currently does not work on my systems is Sidecar. So far I have not been able to get Sidecar working with either Broadcom or Intel Wi-Fi and my iPad Pro M4 under Tahoe.

 

Cheers,
KGP 👍

 

Thank you for the quick reply, and sorry for the delay!
 

I think that in my configuration the patch did not enable anything beyond getting Wi-Fi working through the native macOS interface, which is already pretty nice.
 

Regarding Continuity Camera, yes, I mean using the iPhone camera wirelessly as a webcam or for QuickTime recordings. As for iPhone Mirroring, I mean the native macOS feature that allows you to mirror and control the iPhone from the Mac. I find it very useful for certain tasks.
 

I had also already gone through all the General Troubleshooting Notes in Post #1 before posting here.
 

I reverted the patches, went back to the EFI I was using before applying them, and tested the same features again. The results were exactly the same.
 

Because of that, I suspect I was not successful in getting AWDL working. AirDrop never worked in either direction. I tested with both my iPhone and a Mac mini M4.
 

I searched for ways to verify whether the protocol was actually active. Here are the results:
 

---

Mac mini M4

ifconfig awdl0

awdl0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
	ether 7e:1d:70:33:aa:cf
	inet6 fe80::7c1d:70ff:fe33:aacf%awdl0 prefixlen 64 scopeid 0x12
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active

ifconfig -l

lo0 gif0 stf0 anpi1 anpi0 anpi3 en0 en5 en6 en7 en2 en3 en4 pktap0 ap1 en1 bridge0 awdl0 llw0 utun0 utun1 utun2 utun3

---

Hackintosh

ifconfig awdl0

ifconfig: interface awdl0 does not exist

ifconfig -l

lo0 gif0 stf0 XHC96 XHC128 en2 en0 utun0 utun1 utun2 utun3

---

Based on what I found, the features that did work with the patch appear to be independent of AWDL: AirPlay (in both directions), Universal Clipboard from iPhone/Mac mini to the Hack (but not the other way around), and Continuity features such as Safari tabs or TextEdit documents from the iPhone/Mac mini to the Hack.
 

These same features were also available when using itlwm.kext together with HeliPort. I believe they would even work over Ethernet.
 

I am not sure whether the fact that my setup is AMD could have any impact here, since you have a working AX210 setup.
 

Thank you for your effort and continued support of the community!
 

P.S. One other thing that I am not sure is expected behavior or specific to my setup: after performing the initial patching procedure, if I open OpenCore Legacy Patcher again (second or third launch after several reboots) and click Post-Install Root Patch, the next screen always shows the Start Root Patching button as available, as if the system had never been patched.

[kgp]

7 hours ago, kalkmann said:

 

Thank you for the quick reply, and sorry for the delay!
 

I think that in my configuration the patch did not enable anything beyond getting Wi-Fi working through the native macOS interface, which is already pretty nice.
 

Regarding Continuity Camera, yes, I mean using the iPhone camera wirelessly as a webcam or for QuickTime recordings. As for iPhone Mirroring, I mean the native macOS feature that allows you to mirror and control the iPhone from the Mac. I find it very useful for certain tasks.
 

I had also already gone through all the General Troubleshooting Notes in Post #1 before posting here.
 

I reverted the patches, went back to the EFI I was using before applying them, and tested the same features again. The results were exactly the same.
 

Because of that, I suspect I was not successful in getting AWDL working. AirDrop never worked in either direction. I tested with both my iPhone and a Mac mini M4.
 

I searched for ways to verify whether the protocol was actually active. Here are the results:
 

---

Mac mini M4

ifconfig awdl0

awdl0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=6460<TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
	ether 7e:1d:70:33:aa:cf
	inet6 fe80::7c1d:70ff:fe33:aacf%awdl0 prefixlen 64 scopeid 0x12
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect
	status: active

ifconfig -l

lo0 gif0 stf0 anpi1 anpi0 anpi3 en0 en5 en6 en7 en2 en3 en4 pktap0 ap1 en1 bridge0 awdl0 llw0 utun0 utun1 utun2 utun3

---

Hackintosh

ifconfig awdl0

ifconfig: interface awdl0 does not exist

ifconfig -l

lo0 gif0 stf0 XHC96 XHC128 en2 en0 utun0 utun1 utun2 utun3

---

Based on what I found, the features that did work with the patch appear to be independent of AWDL: AirPlay (in both directions), Universal Clipboard from iPhone/Mac mini to the Hack (but not the other way around), and Continuity features such as Safari tabs or TextEdit documents from the iPhone/Mac mini to the Hack.
 

These same features were also available when using itlwm.kext together with HeliPort. I believe they would even work over Ethernet.
 

I am not sure whether the fact that my setup is AMD could have any impact here, since you have a working AX210 setup.
 

Thank you for your effort and continued support of the community!
 

P.S. One other thing that I am not sure is expected behavior or specific to my setup: after performing the initial patching procedure, if I open OpenCore Legacy Patcher again (second or third launch after several reboots) and click Post-Install Root Patch, the next screen always shows the Start Root Patching button as available, as if the system had never been patched.

 

Hi my friend!

 

Thank you very much for your report.

 

Based on your findings, I decided to re-install my Intel AX210S today and repeat the testing under macOS Tahoe 26.5.

 

Interestingly, I can now reproduce very similar behaviour on my own system.

 

Wi-Fi itself works correctly, AirportItlwm loads, ARPT injection is present and the AX210S is detected properly in System Information.

 

However, I also noticed that Intel Bluetooth currently does not appear to function correctly under macOS 26.5.

The Bluetooth stack itself is present and active. However, Bluetooth devices are only detected after manually power-cycling them. Even then, actual device connections fail. For example, my Magic Keyboard and Magic Mouse are detected after switching them off and on again, but they cannot successfully connect.

 

At the same time, AirDrop is currently not working correctly either:

- My Hack can see my MacBook Pro M1

- Sending fails

- The MacBook Pro M1 does not see the Hack at all

 

I also checked:

ifconfig awdl0

and

ifconfig -l

and can confirm that awdl0 is currently not being created on my AX210S setup under Tahoe 26.5.

 

Because AWDL-dependent services rely heavily on proper Bluetooth functionality, I currently suspect that the Bluetooth issues under macOS 26.5 may also affect AWDL functionality.

 

Interestingly, all of these features had been working correctly during my earlier AX210S testing several months ago, so I am currently re-investigating what may have changed in newer Tahoe releases.

 

Does anybody know a solution to get Intel Bluetooth fully working again under macOS 26.5?

 

See also:

IntelBluetoothFirmware Issue #505

 

Cheers,
KGP 👍

 

Regarding your P.S.:

Yes, I can confirm the same behaviour on my systems.

Even after the root patches have been successfully applied and continue working correctly, OCLP may still present the "Start Root Patching" button again when re-opening the application later.

As far as I can tell, this is purely cosmetic and does not indicate that the patches are missing or that root patching needs to be performed again.

I have observed the same behaviour with both Broadcom and Intel Wi-Fi setups.

Edited May 30 by kgp

[kalkmann]

3 hours ago, kgp said:

 

Hi my friend!

 

Thank you very much for your report.

 

Based on your findings, I decided to re-install my Intel AX210S today and repeat the testing under macOS Tahoe 26.5.

 

Interestingly, I can now reproduce very similar behaviour on my own system.

 

Wi-Fi itself works correctly, AirportItlwm loads, ARPT injection is present and the AX210S is detected properly in System Information.

 

However, I also noticed that Intel Bluetooth currently does not appear to function correctly under macOS 26.5.

The Bluetooth stack itself is present and active. However, Bluetooth devices are only detected after manually power-cycling them. Even then, actual device connections fail. For example, my Magic Keyboard and Magic Mouse are detected after switching them off and on again, but they cannot successfully connect.

 

At the same time, AirDrop is currently not working correctly either:

- My Hack can see my MacBook Pro M1

- Sending fails

- The MacBook Pro M1 does not see the Hack at all

 

I also checked:

ifconfig awdl0

and

ifconfig -l

and can confirm that awdl0 is currently not being created on my AX210S setup under Tahoe 26.5.

 

Because AWDL-dependent services rely heavily on proper Bluetooth functionality, I currently suspect that the Bluetooth issues under macOS 26.5 may also affect AWDL functionality.

 

Interestingly, all of these features had been working correctly during my earlier AX210S testing several months ago, so I am currently re-investigating what may have changed in newer Tahoe releases.

 

Does anybody know a solution to get Intel Bluetooth fully working again under macOS 26.5?

 

See also:

IntelBluetoothFirmware Issue #505

 

Cheers,
KGP 👍

 

Regarding your P.S.:

Yes, I can confirm the same behaviour on my systems.

Even after the root patches have been successfully applied and continue working correctly, OCLP may still present the "Start Root Patching" button again when re-opening the application later.

As far as I can tell, this is purely cosmetic and does not indicate that the patches are missing or that root patching needs to be performed again.

I have observed the same behaviour with both Broadcom and Intel Wi-Fi setups.

 

Thank you very much for the confirmations!
 

That is exactly what I have noticed during my testing over the past few days as well. Through Bluetooth, I am unable to connect to any Apple devices (which also explains why Personal Hotspot remains stuck trying to connect).
 

I also tried connecting my Logitech MX Master 3 (BLE) via Bluetooth, and it would not connect either.
 

Let's hope this is something that can be resolved with a future update to IntelBluetoothFirmware.
 

Thanks again for your time and all the work you have put into this project.
 

Best regards,

Juliano

[kgp]

1 hour ago, kalkmann said:

 

Thank you very much for the confirmations!
 

That is exactly what I have noticed during my testing over the past few days as well. Through Bluetooth, I am unable to connect to any Apple devices (which also explains why Personal Hotspot remains stuck trying to connect).
 

I also tried connecting my Logitech MX Master 3 (BLE) via Bluetooth, and it would not connect either.
 

Let's hope this is something that can be resolved with a future update to IntelBluetoothFirmware.
 

Thanks again for your time and all the work you have put into this project.
 

Best regards,

Juliano

 

Many thanks, Juliano, for bringing this to my attention.

To be honest, I initially assumed that the issue might be specific to your setup. However, after re-installing my own AX210S, I was immediately able to reproduce the same Intel Bluetooth/AWDL issue under macOS Tahoe 26.5.

The issue has now been documented under "10.) Verified Functional Results → b.) Intel Wi-Fi" and has also been reported in IntelBluetoothFirmware Issue #505 for further investigation.

Many thanks again for your detailed testing and feedback. Without your report, I probably would not have re-tested the AX210S under Tahoe 26.5 anytime soon, as I have been happily running my BCM943602CDP setup under macOS 26.5 and 26.6 beta 1.

Cheers,
KGP 👍

[kgp]

Intel AX210 troubleshooting under macOS 26.5.1/26.6 beta 1

 

After recent fixes by Z3cOld to IntelBTPatcher.kext, a new IntelBluetoothFirmware package can be downloaded from:

 

https://github.com/Vinhts/IntelBluetoothFirmware/actions/runs/26730492997

 

Good news first:

Bluetooth now works flawlessly with my Intel AX210 under macOS 26.5.1/26.6 beta 1.

A brand-new AX210 was installed and tested with the latest IntelBluetoothFirmware package from Vinhts.

Results so far:

• Bluetooth controller detected correctly
• Stable Bluetooth address assigned
• Magic Keyboard working
• Magic Mouse working
• Nearby Apple devices detected correctly
• Bluetooth stack remains stable after multiple reboots and sleep/wake cycles
• No Bluetooth-related issues observed so far
• Native Wi-Fi working
• AirPlay working
• Screen Mirroring working

Screenshots:

• Bluetooth Controller
• Magic Keyboard and Magic Mouse connected
• Nearby Apple devices detected
• Hackintool showing AX210 Wi-Fi and Bluetooth controller correctly detected and initialized
• IOREG

 

 

 

 

 

 

 

Unfortunately, there is still no progress regarding:

• AWDL
• AirDrop
• Personal Hotspot

Testing was performed with both:

• OCLP 3.0.0 Nightly
• OCLP-Mod 3.1.9

Both show identical behaviour.

The AWDL interface is not created at all:

ifconfig awdl0

ifconfig: interface awdl0 does not exist

The following components are loaded correctly:

• IOSkywalkFamily
• IO80211FamilyLegacy
• AirportItlwm 2.3.0

However, the system log reports:

Failed to create interface AWDL with error

Failed to accept XPCSession[airportd]

because there is no AWDL interface

As a consequence:

• awdl0 does not exist
• AirDrop does not work
• Personal Hotspot does not work
• Continuity Camera does not work

One additional observation:

OCLP-Mod 3.1.9 correctly detects the Intel AX210 without requiring Broadcom IOName spoofing.

 

 

Nevertheless, the AWDL behaviour remains identical to standard OCLP.

 

At this point Bluetooth can be considered solved on my system, while AWDL remains the last major obstacle.

 

Further testing will follow.

 

Cheers,
KGP 👍

Edited June 5 by kgp

[kgp]

BE200 troubleshooting under macOS 26.5.1/26.6 beta 1

 

After completing my AX210 testing, I installed a brand-new Intel BE200 (Wi-Fi 7 / Bluetooth 5.4) for additional evaluation under macOS Tahoe 26.5.1/26.6 beta1.

The card was tested using AirportItlwm 2.3.0 (Ventura) from issue #955:

https://github.com/OpenIntelWireless/itlwm/issues/955

together with the latest IntelBluetoothFirmware package provided by Vinhts:

https://github.com/Vinhts/IntelBluetoothFirmware/actions/runs/26730492997

Good news first:

Bluetooth works very well with the BE200.

Results so far:

• Bluetooth controller detected correctly
• Stable Bluetooth address assigned
• Magic Keyboard connects successfully
• Magic Mouse connects successfully
• Nearby Apple devices detected correctly
• No Bluetooth-related issues observed so far

Screenshots:

• Bluetooth Controller
• Magic Keyboard and Magic Mouse connected
• Nearby Apple devices detected
• Hackintool showing Intel BE200 Wi-Fi 7 + Bluetooth 5.4 correctly detected and initialized
• IOREG

 

 

 

 

 

 

 

Wi-Fi behaviour is much more interesting.

The BE200 is detected correctly by macOS:

• Intel BE200 Wi-Fi 7 + Bluetooth 5.4
• Device ID: 0x272B
• AirportItlwm loaded correctly
• Firmware loaded correctly
• Country Code: DE

Initial testing suggested that Wi-Fi scanning was completely broken:

• No networks detected
• Manual network creation returned "Network not found"
• Scan Cache Count = 0

However, after additional testing, the situation turned out to be more complicated.

The BE200 eventually detected and joined my WPA2/WPA3 network ("bbc") and macOS reported the network as connected.

 

 

However:

• DHCP does not appear to work
• No IPv4 or IPv6 address is assigned to en2
• No DNS servers are assigned
• Internet access is unavailable
• Even the local router (192.168.178.1) cannot be reached through the BE200 connection

Manual configuration of TCP/IP settings and DNS servers does not change the result.

 

Although the BE200 is able to associate with the Wi-Fi network and the interface reports status: active, the network configuration is not applied successfully and no functional internet connectivity is established.

 

Additional observations:

AWDL is  missing:

ifconfig awdl0

ifconfig: interface awdl0 does not exist

wdutil reports:

• AWDL Enabled: n/a
• Interface Name: (null)
• Power: Off

Current status:

• Bluetooth: Working
• Wi-Fi Scanning: Working sporadically
• Wi-Fi Association: Working sporadically
• Router Connectivity: Not Working
• DHCP or manual TCP/IP and DNS configuration: Not Working
• Internet Access: Not Working
• AWDL: Missing

This is a significantly different result from the AX210.

 

The AX210 provides stable Wi-Fi connectivity but lacks AWDL.

 

The BE200 appears capable of occasionally associating with Wi-Fi networks; however, it consistently fails to obtain a functional network configuration.

 

Further testing will follow.

 

Cheers,

KGP

Edited June 5 by kgp

[dogansan]

2 hours ago, kgp said:

BE200 troubleshooting under macOS 26.5.1/26.6 beta 1

 

After completing my AX210 testing, I installed a brand-new Intel BE200 (Wi-Fi 7 / Bluetooth 5.4) for additional evaluation under macOS Tahoe 26.5.1/26.6 beta1.

The card was tested using AirportItlwm 2.3.0 (Ventura) from issue #955:

https://github.com/OpenIntelWireless/itlwm/issues/955

together with the latest IntelBluetoothFirmware package provided by Vinhts:

https://github.com/Vinhts/IntelBluetoothFirmware/actions/runs/26730492997

Good news first:

Bluetooth works very well with the BE200.

Results so far:

• Bluetooth controller detected correctly
• Stable Bluetooth address assigned
• Magic Keyboard connects successfully
• Magic Mouse connects successfully
• Nearby Apple devices detected correctly
• No Bluetooth-related issues observed so far

Screenshots:

• Bluetooth Controller
• Magic Keyboard and Magic Mouse connected
• Nearby Apple devices detected
• Hackintool showing Intel BE200 Wi-Fi 7 + Bluetooth 5.4 correctly detected and initialized
• IOREG

 

 

 

 

 

 

 

Wi-Fi behaviour is much more interesting.

The BE200 is detected correctly by macOS:

• Intel BE200 Wi-Fi 7 + Bluetooth 5.4
• Device ID: 0x272B
• AirportItlwm loaded correctly
• Firmware loaded correctly
• Country Code: DE

Initial testing suggested that Wi-Fi scanning was completely broken:

• No networks detected
• Manual network creation returned "Network not found"
• Scan Cache Count = 0

However, after additional testing, the situation turned out to be more complicated.

The BE200 eventually detected and joined my WPA2/WPA3 network ("bbc") and macOS reported the network as connected.

 

 

However:

• DHCP does not appear to work
• No IPv4 or IPv6 address is assigned to en2
• No DNS servers are assigned
• Internet access is unavailable
• Even the local router (192.168.178.1) cannot be reached through the BE200 connection

Manual configuration of TCP/IP settings and DNS servers does not change the result.

 

Although the BE200 is able to associate with the Wi-Fi network and the interface reports status: active, the network configuration is not applied successfully and no functional internet connectivity is established.

 

Additional observations:

AWDL is  missing:

ifconfig awdl0

ifconfig: interface awdl0 does not exist

wdutil reports:

• AWDL Enabled: n/a
• Interface Name: (null)
• Power: Off

Current status:

• Bluetooth: Working
• Wi-Fi Scanning: Working sporadically
• Wi-Fi Association: Working sporadically
• Router Connectivity: Not Working
• DHCP or manual TCP/IP and DNS configuration: Not Working
• Internet Access: Not Working
• AWDL: Missing

This is a significantly different result from the AX210.

 

The AX210 provides stable Wi-Fi connectivity but lacks AWDL.

 

The BE200 appears capable of occasionally associating with Wi-Fi networks; however, it consistently fails to obtain a functional network configuration.

 

Further testing will follow.

 

Cheers,

KGP

I need to make an addition to your findings, I am observing almost similar behaviours except my BE200 has internet once it strugles  and finally is connected to my router.

[kgp]

Update of post 1....

 

Hackintosh Real-world Network Performance (80 Mbps DSL)

 

 

 

LAN (IntelLucy/X550-AT2):

 

 

Wi-Fi (OCLP/BCM943602CDP):

 

 

The results show virtually identical real-world internet performance over Ethernet and 5 GHz mesh Wi-Fi on the same Hackintosh. 

 

AX210 Wi-Fi performance under Tahoe is virtually indistinguishable from my BCM943602CDP:

 

Edited June 11 by kgp

[kgp]

For all Intel Wi-Fi users following the ongoing Tahoe testing:

 

I have opened AirportItlwm issue #1062 to investigate the current AWDL situation under macOS Tahoe.

 

Wi-Fi, Bluetooth, AirPlay, Screen Mirroring and Handoff appear to be working with the current AirportItlwm/OCLP approach, but AirDrop, Personal Hotspot and Continuity Camera remain unavailable due to the apparent absence of awdl0.

 

Additional test results, logs and feedback from AX2xx, BE200 and older Intel chipsets are highly appreciated.

 

GitHub issue:
https://github.com/OpenIntelWireless/itlwm/issues/1062