Jump to content
62 posts in this topic

Recommended Posts

After update to 26.3,

I simply applied some patches to AppleEthernetRL, which allowed me to register my network card interface, but unfortunately, I couldn't access the internet.

 

Apple seems to have made some customization to the network card firmware, such as some PHY addresses being changed.

 

Perhaps someone will conduct more detailed decompilation research on it in the future, but that would be a waste of time.

 

Image_1771035810897_358.thumb.png.07445e300d6b241fa3b5c69f21df4ae2.png

Edited by laobamac_yyds
  • Like 5
44 minutes ago, Slice said:

Someone has a problem with IOSkywalkFamily in Tahoe 26.3?

I mean a method to block system kext and inject old one. Someone with OC does this?

 Hi @Slice

 

No problem here under Tahoe 26.3.. everything works as expected with the IOSkywalkFamily replacement.. Please have a look to my EFI-Folder distribution for Broadcom or Intel if it helps somehow.. 👍  

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

 Hi @Slice

 

No problem here under Tahoe 26.3.. everything works as expected with the IOSkywalkFamily replacement.. Please have a look to my EFI-Folder distribution for Broadcom or Intel if it helps somehow.. 👍  

Thanks, I will take your version of IOSkywalkFamily.kext but... the download is not finishing. May be because of VPN which I am forced to use.

 

  • Like 2
2 minutes ago, Slice said:

Thanks, I will take your version of IOSkywalkFamily.kext but... the download is not finishing. May be because of VPN which I am forced to use.

 

 

Download works here without issues, just checked on that: 87.79 MB downloaded successfully. 👍

  • Like 2

Haven't posted here in a while. I was postponing the upgrade from Sequoia but today I decided to prep and do it on an old laptop collecting dust around. Everything is working as expected. @laobamac_yyds's patch has been applied for full Wifi and audio capabilities. My system kernel panicked at first but I was able to find and fix the issue quickly, it was misconfiguration with the AMFI kext/boot args.

 

HP EliteBook 840 G6 | i5-8250U | 32GB DDR4 | WD Black SN770 1TB NVME | BCM94360NG

 

 

image.png.45043ded41abee2d06dcd4804a18a82f.png

  • Like 5
On 2/23/2026 at 4:20 AM, Slice said:

But not for me

Снимок экрана 2026-02-23 в 06.18.53.png

And stop forever.

 

Can you download the zip files attached below with your VPN connection? If the latter is not the case, never mind, I guess other users already provided you with the necessary and requested information.

 

For all other users: Do not blindly apply the EFIs attached below without reading the following context information:

1.)  EFI-Folder distribution 

2.) Experimental Fork of OCLP 3.0.0 Nightly

3.) OCLP-Mod

4.) X299 Guidelines

EFI-KGP-public-v.1.1.3-OCLP-Broadcom.zip EFI-KGP-public-v.1.1.3-OCLP-Intel.zip

Edited by KGP-iMacPro
  • Like 3
  • Thanks 1
  • 2 weeks later...

Painless OTA update to macOS Tahoe 26.3.1 (25D2128) with Whatevergreen 1.7.1d7.

 

 image.png.308ab9436ce21f96dfbdf9f9c38c925f.png

 

image.png.0aeb1612b0409965ab6895ce2234a821.png

 

Audio and Wi-Fi with Airdrop, Airplay and Screen Mirroring successfully tested with OCLP 3.0.0 Nightly available on my Github repository in line with my BCM943602CDP. 

 

image.png.176a49d5039d8c35921808b5866464e1.png

 

image.png.089b558062ea5581518c01735293fcf2.png

 

image.png.5b7b7509522e070e00b62ec1a9abf5e4.png

 

image.png.518e01a680afcf735f9481acdab2696b.png

 

image.thumb.png.3ed5239a9e3e5f4e93ff3e4fefa892c5.png

 

 

 

image.thumb.jpeg.0f34cba4efe447bc8388cc6649bd64f8.jpeg

 

image.thumb.jpeg.9a4d1c781622849abcd947b92cc57395.jpeg

 

image.thumb.jpeg.25c24da16dac351090d9fc3bdd0b71c8.jpeg

 

image.thumb.jpeg.62b8bbc8280d403add587db806a14fc6.jpeg

 

    

 

System booted with the Broadcom-EFI of my EFI-Folder Distribution with AMFIPass.kext 1.4.1 enabled and using boot-arg "amfi=0x80". Everything by exactly following my OCLP guidelines

 

Good luck,

 

KGP 👍 

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

System booted with the Broadcom-EFI of my EFI-Folder Distribution with AMFIPass.kext 1.4.1 enabled and using boot-arg "amfi=0x80". Everything by exactly following my OCLP guidelines

 

I'm a little confused. The OCLP 3.0.0 Nightly github says not to use AMFIPass.kext, but you're using both AMFIPass.kext and the "amfi=0x80" option at the same time. What does "using both at the same time" mean? If I use both, will I still be able to use Broadcom WiFi and audio? No kernel panics?

  • Like 3
6 hours ago, cloudy said:

I'm a little confused. The OCLP 3.0.0 Nightly github says not to use AMFIPass.kext, but you're using both AMFIPass.kext and the "amfi=0x80" option at the same time. What does "using both at the same time" mean? If I use both, will I still be able to use Broadcom WiFi and audio? No kernel panics?

 

I was definitely using AMFIPass.kext 1.4.1 (enabled) with boot-arg "amfi=0x80" over the recent months on my system (totally forgot about this tiny detail) and therefore corrected all respective guidelines yesterday. The description on Github just remains without unchanged yet. When just using boot-arg "amfi=0x80" without AMFIPass.kext enabled, AWDL refuses to work on my system. Apart from this difference, the system also boots with AMFIPass.kext disabled, but only Wi-Fi and AppleHDA are working (no AWDL). Try at first place,  if AWDL is working on your system with  boot-arg "amfi=0x80" and  AMFIPass.kext disabled. I can just talk about my system und EFI-Folder configuration. You might likely want to do the tests on a test drive and not on a productive system. In any case, always have a second EFI on a separate bootable disk with "amfi=0x80" and AMFIPass.kext disabled.       

Edited by KGP-iMacPro
  • Like 4
21 minutes ago, cloudy said:

Thanks for the quick reply. I'm having trouble with VMWare when I use the "amfi=0x80" option (not sure if it's related), so I was wondering if using it with the kext file would work with VMWare as well. Right now I'm just using the "amfi=0x80" option.

 

I know and you said that boot-arg ipc_control_port_options=0 does not help either.. BTW.. Have you tried @MakAsrock's approach with   https://github.com/YBronst/tccplus instead of ipc_control_port_options=0???

15 minutes ago, cloudy said:

Oh, after reading your reply, a new question arose. From what you said, it seems like using just AMFIPass.kext .14.1 only would be fine. Is that okay?

 

My system with the OCLP 3.0.0 Nightly root patches only works with AMFIPasskext enabled, when using boot-arg "amfi=0x80"!!!! Otherwise the system won't boot! Don't use OCLP 3.0.0 Nightly only with AMFIPass.kext! boot-arg "amfi=0x80" must be set in any case and is deemed necessary! If you have problems with "amfi=0x80", better use OCLP-Mod 3.1.5, which works with AMFIPass.kext enabled together with boot-arg "-amfipassbeta". 

Edited by KGP-iMacPro
  • Like 3
×
×
  • Create New...