Jump to content
511 posts in this topic

Recommended Posts

@Matgen84

Hi, my friend. Don't worry, I just re-pushed some changes that should have appeared in the tahoe-test branch.

 

These changes are about the OMAPI address (this is related to whether users in mainland China can download KDK and other resources online normally, and will not affect other regions.) See here for details:

 

 

When synchronizing this change to the main branch (version 2.6.7), I forgot to use git branch to switch the target, causing the tahoe-test branch to be mistakenly overwritten by the same change. But I have repaired it so far.

 

laobamac.

 

  • Like 3

I am not using OCLP-Mod, so please forgive the naive question... Does OCLP-Mod install AppleHDA.kext in /Library/Extensions or /System/Library/Extensions?  Thank you.

2 minutes ago, deeveedee said:

I am not using OCLP-Mod, so please forgive the naive question... Does OCLP-Mod install AppleHDA.kext in /Library/Extensions or /System/Library/Extensions?  Thank you.

 

/System/Library/Extensions

 

  • Thanks 1

@KGP-iMacPro That's what I thought.  I tested the current OCLP 3.0.0 nightly and it installed AppleHDA.kext in /Library/Extensions.   The patch didn't work.  OCLP 3.0.0 is still a work in progress.

  • Like 1
16 minutes ago, deeveedee said:

@KGP-iMacPro That's what I thought.  I tested the current OCLP 3.0.0 nightly and it installed AppleHDA.kext in /Library/Extensions.   The patch didn't work.  OCLP 3.0.0 is still a work in progress.

 

There are rumours, that OCLP 3.0.0 for Tahoe should be released Dec 5–10 based on current progress. All links of the latest beta appear to be down again: 

 

https://www.itech4mac.net/2025/11/oclp-3-released-today-latest-nightly-build-what-actually-works/

 

I think any related information has to be treated very carefully for now... 

 

 

 

 

Edited by KGP-iMacPro
  • Like 1

I would recommend getting the OCLP 3.0.0 status from the actual OCLP Devs who are reporting status starting here.  Current Dev projections are a release in early 2026.  Any "non-official" links are probably just click-bait.

  • Like 1

https://github.com/OpenIntelWireless/itlwm/issues/1009#issuecomment-3602342522

 

in my system it doesnt work and i need to reseal my os

image.png.db29859fceeefd97c083c0da52d91737.png

 

also it detects a patch for audio that my system does not need

 

Only doubt is i have 26.2 beta and KDK is different

 

thanks @Anto65 to let me know about this

 

EDIT

It doesnt work also in 26.1 with a correct KDK

Edited by fabiosun
  • Like 1
1 hour ago, fabiosun said:

https://github.com/OpenIntelWireless/itlwm/issues/1009#issuecomment-3602342522

 

in my system it doesnt work and i need to reseal my os

image.png.db29859fceeefd97c083c0da52d91737.png

 

also it detects a patch for audio that my system does not need

 

Only doubt is i have 26.2 beta and KDK is different

 

thanks @Anto65 to let me know about this

 

EDIT

It doesnt work also in 26.1 with a correct KDK

indeed it is working here, but needs amfi=0x80 instead of AmfiPass 

 

just airdropped a mp4 from Tahoe to my iPhone 😉

Edited by schrup21
  • Like 4
1 hour ago, schrup21 said:

there's no Tahoe version - but as same as for Sequoia, the Ventura version + OCLP Modern Wifi Patch should work

no it doesn't work, I'm trying but it doesn't activate, at least for me,

Sorry again for a remedial question ... OCLP Devs say their current modern wi-fi patch for Tahoe needs VT-d disabled (for hacks, that would be VT-d disabled in BIOS or Kernel > Quirks > DisableIoMapper = True).

 

Does this OCLP-Mod implementation of modern Wi-Fi patches for Tahoe require disabled VT-d?

 

EDIT: @carlo_67 I need VT-d disabled for working OpenWireless itlwm/Heliport on my HackBookPro running Tahoe 26.2.  Does that help you with airportitlwm?

Edited by deeveedee

All the above appears still somewhat cryptic to me. May I ask, what needs to be done is the following?:

 

a.) Download OCLP 3.0.0 with this link?: https://nightly.link/lzhoang2801/OpenCore-Legacy-Patcher/workflows/build-app-wxpython/tahoe-patchset/OpenCore-Patcher.pkg.zip

b.) Disable AMFIPass.kext and use boot arg "amfi=0x80" instead?

c.) csr-active-config to 03080000?

d.) AppleVTD disabled, i.e. DisableIOMapper=true?

e.) Same com.apple.iokit.IOSkywalkFamily replacement like under Sequoia?

 

By this, OCLP 3.0.0 Modern Wifi Patch (Broadcom) and Modern Audio Patch are fully working? The Wifi Patch works with my BCM943602CDP, BCM943602CS, BCM94360CD and even with my Intel X210 by adding airportitlwm.kext for Ventura? 

 

Thanks in advance for any clarification or confirmation! 

 

Cheers, KGP

 

  

  

Edited by KGP-iMacPro
  • Like 2
2 hours ago, KGP-iMacPro said:

All the above appears still somewhat cryptic to me. May I ask, what needs to be done is the following?:

 

a.) Download OCLP 3.0.0 with this link?: https://nightly.link/lzhoang2801/OpenCore-Legacy-Patcher/workflows/build-app-wxpython/tahoe-patchset/OpenCore-Patcher.pkg.zip

b.) Disable AMFIPass.kext and use boot arg "amfi=0x80" instead?

c.) csr-active-config to 03080000?

d.) AppleVTD disabled, i.e. DisableIOMapper=true?

e.) Same com.apple.iokit.IOSkywalkFamily replacement like under Sequoia?

 

By this, OCLP 3.0.0 Modern Wifi Patch (Broadcom) and Modern Audio Patch are fully working? The Wifi Patch works with my BCM943602CDP, BCM943602CS, BCM94360CD and even with my Intel X210 by adding airportitlwm.kext for Ventura? 

 

Thanks in advance for any clarification or confirmation! 

 

Cheers, KGP

 

  

  

 

in my case no need to Disable AMFIPass.kext but yes must use boot-arg : amfi=0x80

  • Like 4
3 hours ago, pico joe said:

 

in my case no need to Disable AMFIPass.kext but yes must use boot-arg : amfi=0x80

Same for me. Working fine with vt-d disabled in bios and following sequoia instructions except use amfi=0x80 instead of amfipass. I guess they will release a newer amfipass kext soon that will work with tahoe. Airdrop works great. Good thing is it also patches for audio - by installing kdk and kext in the background. 

  • Like 2

Has anyone needed to use amfi=0x80 (equivalent to amfi_get_out_of_my_way=1) for the "official" OCLP?  AMFI (Apple Mobile File Integrity) is a security measure that protects against malicious code running in macOS.  AMFIPass.kext specifically allows official OCLP code to run while leaving the rest of AMFI security measures unchanged.

 

What is this new fork of "OCLP 3.0.0" running that is not allowed by AMFIPass.kext?

 

EDIT: Is it possible that AMFIPass.kext has not yet been updated for Tahoe and if so, shouldn't the developers of their own forks be providing an updated AMFIPass.kext so that AMFI doesn't need to be completely disabled?

 

EDIT2: For those who need amfi=0x80, instead try using boot-arg -amfipassbeta with AMFIPass.kext (without amfi=0x80) to see if that resolves the AMFI issues with unofficial OCLP forks.

 

EDIT3: @miliuco has confirmed that -amfipassbeta does not work.  See @laobamac_yyds comments here and here about this new "Experimental OCLP 3.0.0 Nightly" and about the importance of AMFI.

Edited by deeveedee
  • Like 4
20 hours ago, deeveedee said:

Does this OCLP-Mod implementation of modern Wi-Fi patches for Tahoe require disabled VT-d?

To be honest, I had DisableIoMapper enabled, but only because of IntelMausiEthernet (which doesn't currently work with AppleVTD). OCLP couldn't load the KDK without internet, so I unknowingly fulfilled the requirement.

Since setting dart=0 apparently disables VT-d (which is also specified as a requirement but I haven't set), I would assume that disabling VT-d in the BIOS would have the same effect.

20 hours ago, KGP-iMacPro said:

a.) Download OCLP 3.0.0 with this link?: https://nightly.link/lzhoang2801/OpenCore-Legacy-Patcher/workflows/build-app-wxpython/tahoe-patchset/OpenCore-Patcher.pkg.zip

b.) Disable AMFIPass.kext and use boot arg "amfi=0x80" instead?

c.) csr-active-config to 03080000?

d.) AppleVTD disabled, i.e. DisableIOMapper=true?

e.) Same com.apple.iokit.IOSkywalkFamily replacement like under Sequoia?

Yes to all.

 

  • 3 weeks later...
47 minutes ago, mnfesq said:

Thank you @laobamac_yyds for the wonderful Christmas gift.

I would call it a "Christmas present" if Tahoe finally fully supports Nvidia graphics cards (Kepler).

This, with Wi-Fi and so on, is all secondary! There are alternatives for that, but there's no

way around full graphics support on Tahoe!! Especially not on unsupported Macs,

like my late 2013 27-inch iMac.

  • Like 1
2 hours ago, AlfredoM said:

I would call it a "Christmas present" if Tahoe finally fully supports Nvidia graphics cards (Kepler).

This, with Wi-Fi and so on, is all secondary! There are alternatives for that, but there's no

way around full graphics support on Tahoe!! Especially not on unsupported Macs,

like my late 2013 27-inch iMac.

 

Grinch

  • Haha 2
×
×
  • Create New...