Jump to content
209 posts in this topic

Recommended Posts

Momentous news!!  I have managed to update my Test SSD to 25F5042g.   To do this I uninstalled OCLP MOD entirely rebooted cleared NVRAM and tried the update….and here we are.  Very pleased indeed.

 

Cheers, Howard

 

EDIT:  Well I was ok two of of three drives.  The one that failed installed ok and even started to load the desktop for about 15 seconds then the screen switched...Your software has installed successfully.  The next screen was the Analysis one and this I couldn't get past.  In the end I just cloned the drive so all three are up and running. 

Edited by Zevgoli
  • Like 6
On 4/5/2026 at 12:52 PM, mnfesq said:

The sluggishness that I reported after installing beta 4 persists every time I reboot and I have had some trouble with my laptop rebooting supposedly while it's sleeping.  When I wake it from sleep after it rebooted, it takes forever for the laptop to become responsive to my controls and usually requires another reboot.  None of this happened with beta 3 or earlier.  I continue to suspect that beta 4 introduced one or more significant changes "under the hood" that makes it much less compatible with my laptop's hardware.  To be honest, if Tahoe is the last version of macOS that works with Intel processors, I may consider reverting back to Sequoia, which works much better with my hardware than Tahoe.

Same behavior here... tried to reinstall the full installer on top of the existing installation and I got the same result... it takes ages to become responsive after booting... you click on an icon in the dock, it starts bouncing and it takes ages to open safari and others... very strange. We'll see how this works when the next beta comes out... 

 

Cheers,

D.

  • Like 1
  • Confused 2
  • Sad 1
1 hour ago, asdfghjklzxcvbnm said:

Thanks but Mac OS panics on boot while loading IOSkywalkFamily.kext using laboramac's oclp-mod 3.1.7 for patching

Upload your EFI-folder that somebody can have a look to it. I am not at home until later at night. I am convinced that there is something at odd in your EFI-configuration. Please provide also your system specs, in particular, which Ethernet controller and Ethernet.kext you are employing. That’s the proper way how to receive help in your issue.

Edited by kgp
  • Like 3
5 hours ago, kgp said:

Upload your EFI-folder that somebody can have a look to it. I am not at home until later at night. I am convinced that there is something at odd in your EFI-configuration. Please provide also your system specs, in particular, which Ethernet controller and Ethernet.kext you are employing. That’s the proper way how to receive help in your issue.

Thinkpad T60

 

config.plist

  • Like 1
1 hour ago, asdfghjklzxcvbnm said:

Very old hardware from 2006 (ThinkPad T60). No experience with such outdated Intel Wi-Fi. You may consider replacing it with a Broadcom BCM94360, but with about 50$ this might exceed the actual value of the entire laptop.

 

Ethernet is also very old. You can try IntelMausiEthernet.kext 3.0.0, but older versions might work better, although might not be compatible with the IOSkywalk replacement.

 

I can take a closer look at your EFI later tonight when I’m back home, if it will help at all. 👍

Edited by kgp
  • Like 1

@asdfghjklzxcvbnm,

 

I have already provided you with all necessary links to my EFI folder distribution (baseline) as well as OCLP guidelines. Please use these resources to rebuild your EFI from scratch.

 

Your EFI is heavily misconfigured. There are multiple conflicting approaches mixed together (Voodoo, AppleHDA patches, BrcmPatchRAM, itwlm.kext, etc.), no proper device property spoofing, no ACPI spoofing and no blocking of IOSkywalkFamily.

 

In this state, proper troubleshooting is not really possible.

 

I would strongly recommend rebuilding your EFI from a clean base and only adding what is actually required for your hardware instead of trying to fix your actual configuration.

 

However, given the extremely outdated hardware, any attempt to run any version of OpenCore Legacy Patcher (including 2.4.1 under Sequoia) on this system may be fundamentally ill-posed.

 

Good luck,

 

KGP 👍

Edited by kgp
  • Like 3
11 hours ago, asdfghjklzxcvbnm said:

Thanks but Mac OS panics on boot while loading IOSkywalkFamily.kext using laboramac's oclp-mod 3.1.7 for patching

 You must create a Kernel > Block Item for IOSkywalkFamily.kext in your OC config.plist, so that the System's IOSkywalkFamily.kext is not loaded.  This permits injection of the downgraded IOSkywalkFamily.kext.

  • Like 5
6 hours ago, kgp said:

@asdfghjklzxcvbnm,

 

I have already provided you with all necessary links to my EFI folder distribution (baseline) as well as OCLP guidelines. Please use these resources to rebuild your EFI from scratch.

 

Your EFI is heavily misconfigured. There are multiple conflicting approaches mixed together (Voodoo, AppleHDA patches, BrcmPatchRAM, itwlm.kext, etc.), no proper device property spoofing, no ACPI spoofing and no blocking of IOSkywalkFamily.

 

In this state, proper troubleshooting is not really possible.

 

I would strongly recommend rebuilding your EFI from a clean base and only adding what is actually required for your hardware instead of trying to fix your actual configuration.

 

However, given the extremely outdated hardware, any attempt to run any version of OpenCore Legacy Patcher (including 2.4.1 under Sequoia) on this system may be fundamentally ill-posed.

 

Good luck,

 

KGP 👍

Sorry T460 Some of the Kexts are disabled 

Edited by asdfghjklzxcvbnm
  • Like 2
4 hours ago, asdfghjklzxcvbnm said:

Sorry T460 Some of the Kexts are disabled 

 

T460 is a game changer. Your system (ThinkPad T460) should actually be well supported by OCLP, so with a proper setup this should work fine.

 

I have already provided you with all necessary links to my EFI-Folder distribution and the corresponding OCLP guidelines. Please use these as your reference and rebuild your EFI from scratch specifically for the T460. Do not keep mixing different approaches. Create a clean, minimal EFI designed for OCLP only.

Make sure to properly adjust the PCI/device path of your Wi-Fi card under DeviceProperties so that spoofing is applied correctly.

From all of my AMLs, you only need the EPG3 section of SSDT-X299-Slot1-Slot3-PC02-BR2A-SL05-RadeonVII-HDAU-ARPT.aml, adapted to the correct ACPI path of your T460.

Also use IntelMausiEthernet.kext v3.0.0 instead of IntelMausi.kext.

I am attaching IntelMausiEthernet.kext v3.0.0 and my Intel-OCLP-EFI-Folder distribution.

Once you have a clean and minimal EFI-Folder for your T460 and OCLP only, feel free to upload the complete EFI-Folder if problems still persist. I need the complete EFI-Folder to properly assess and work on your setup.

 

Most important! Let's move all future discussion to the experimental fork thread. This thread here is for issues with 26.5 beta only.  

 

Good luck,

 

KGP 👍

 

 

EFI-KGP-public-v.1.1.5-OCLP-Intel.zip IntelMausiEthernet.kext.zip

Edited by kgp
  • Like 3

Fast and painless sequential OTA update (3.72 GB) to macOS 26.5 Beta 2 (25F5053d)

 

image.png.14ba1ef10477bda06d03d22c4d61cb6b.png

 

image.png.7a51db9809e2d63ac5cbe56c54bef13a.png

 

No KDK for macOS 26.5 beta 2 has been released by Apple yet. Surprisingly, OCLP 3.0.0 Nightly (amfipassbeta variant) selects KDK build 25E246 from macOS 26.4 as the closest match.

 

image.png.416b7cd5c37f3adfe3519108c66b492f.png

 

Apparently, the KDK for macOS 26.4.1 is still missing in the Dortania KDKSupportPkg .

 

The KDK for build 25F5042g (macOS 26.5 beta 1) is still available on Dortania. However, it is labeled as macOS 26.5.1, which follows Apple’s original naming and is not an issue introduced by Dortania.

 

Due to this versioning, the patcher may not consider KDK 25F5042g a valid match for macOS 26.5 beta 2 (25F5053d), and instead falls back to macOS 26.4 (25E246) as the closest supported version.

 

Even though KDK 25F5042g (macOS 26.5 beta 1) was already installed from the previous system state, OCLP does not consider it a valid match for macOS 26.5 beta 2 and instead falls back to KDK 26.4 (25E246).

 

Nevertheless, modern audio and modern Wi-Fi, including AWDL, continue to work flawlessly.

 

image.png.6027753f4cb917366ecabb30e89b9543.png

 

image.png.10d21fadaf5febfea8fa81c1f04f5cb0.png

    

Edited by kgp
  • Like 5
35 minutes ago, LockDown said:

Aquí funciona. Nunca probé '-Plus'. 

https://github.com/5T33Z0/OCLP4Hackintosh/blob/main/Enable_Features/AirportItllwm_Sequoia.md

https://github.com/laobamac/OCLP-Mod/releases

https://github.com/YBronst/OCLP-Plus/releases

 

In Tahoe, neither of the two guides on a desktop PC activates Wi-Fi to be patched.

image.thumb.jpeg.471c2fff4dcde3bc1fcd635877fea5f2.jpeg

 

AirportItlwm_Sequoia.plist

Edited by kaoskinkae
  • Like 1
40 minutes ago, kaoskinkae said:

 

As I already pointed out, please follow my Intel Wi-Fi guidelines:

Also note that Broadcom spoofing is not universally applicable to all Intel Wi-Fi cards. This only works with newer Intel chipsets (e.g. AX200/AX210) that are compatible with the Modern Wi-Fi patch stack. Legacy Intel cards (such as 3165) are not supported and cannot be fixed via spoofing.

So this strongly depends on the actual hardware in use on your system.   

 

Good luck,

 

KGP

Edited by kgp
  • Like 3
3 minutes ago, kgp said:

 

As I already pointed out, please follow my Intel Wi-Fi guidelines:

Also note that Broadcom spoofing is not universally applicable to all Intel Wi-Fi cards. This only works with newer Intel chipsets (e.g. AX200/AX210) that are compatible with the Modern Wi-Fi patch stack. Legacy Intel cards (such as 3165/7265) are not supported and cannot be fixed via spoofing.

So this strongly depends on the actual hardware in use on your system.   

 

Good luck,

 

KGP

Thanks for the clarification. That's why my profile shows the three computers: New, Old1, and Old2 with the Wireless 3165. Therefore, I now know it's impossible and I'll continue using Heliport, which works perfectly. I'm closing this thread and have learned from your explanation.

  • Like 2
Guest
This topic is now closed to further replies.
×
×
  • Create New...