Jump to content
64 posts in this topic

Recommended Posts

6 hours ago, deeveedee said:

Just upgraded my HackBookPro16,2 to Tahoe 26.4 Release.  Painless upgrade resulting in a perfect hack.

 

This hack uses

  • Open Core 1.0.7 Release
  • VoodooHDA.kext 3.1.2 (with VoodooHDAEnableVolumeChangeFix=True, thanks to MaLd0n and Lockdown) for Audio
  • itlwm 2.3.0 / Heliport 1.5.0 for Intel Wi-Fi
  • IntelBluetooth kexts and BluetoolFixup.kext 2.7.2 for Intel Bluetooth
  • SIP csr-active-config = <01000000>
  • No root patches

 

Incremental Upgrade

  Reveal hidden contents

Screenshot2026-03-25at4_32_47PM.png.628ccbe5ba670cdbdd835ca28eb0daae.png

 

GeekBench 6 CPU

  Reveal hidden contents

Screenshot2026-03-26at9_33_21PM.thumb.png.7420b5b0c8008c9c895606128d2e1603.png

 

Screenshot2026-03-26at9_01_30PM.png.97c76e5463ceac0cd307011a3ff75ad6.png

 

EDIT: These System Settings are significantly improving graphics performance on my underpowered Intel iGPU

  • Accessibility > Display > Reduce Transparency: Enabled
  • Accessibility > Motion > Reduce Motion: Enabled

 

Hi Deeveedee, hows the battery performance on your elitebook so far?

Edited by litemint09
  • Like 2

I've been testing until I confirmed that the problem I was having with the slow and annoying mounting of the XFAT formatted mechanical hard drive is solved and it mounts without issue. Now let's think about why. Well, it could be because I removed the kexts that weren't working for the Broadcom Wi-Fi, or it could be the addition of the NVMeFix.kext. Although I think it's the Broadcom kexts plus AMFIPass.kext. It's confirmed that it was the Wi-Fi kexts, later patched by OCPL, that were causing the delay on the desktop of the mechanical data drive in Tahoe. If anyone else experiences this, please confirm. Disabling the NVMeFix.kext kext does not cause the delay error when mounting the XFAT mechanical hard drive

on the desktop.

in NEW

 

image.jpeg.c01f45d8ac6eabff33ce8df4c014ad68.jpeg

 

  • Like 2
  • Thanks 1

Not sure where to post this, since I couldn't find the original question.  Hopefully this finds the person who asked the question.  My apologies for what may be an off-topic post.

 

Someone had indicated that their hack has a serial port that macOS was detecting and associating with a network device.  This serial port / network device was interfering with a Wi-Fi USB dongle.  I don't know if this helps you, but attached is an SSDT that I created on one of my hacks to "hide" a serial port from macOS.  This attached SSDT assigns class-code = <FF FF FF FF> so that macOS ignores the UART.  You will need to modify the ACPI path and _ADR for your device.

 

I hope this helps.

 

 

EDIT: Note that I needed to use the class-code technique, because I attempted to create an _STA method that conditionally returned Zero for Darwin, but the _STA method did not work.  Modifying class-code was the only way that I could achieve the desired result on my hack for this device.

SSDT-UART.aml.zip

Edited by deeveedee
  • Like 2
2 hours ago, kaoskinkae said:

It's confirmed that it was the Wi-Fi kexts, later patched by OCPL, that were causing the delay on the desktop of the mechanical data drive in Tahoe. If anyone else experiences this, please confirm. Disabling the NVMeFix.kext kext does not cause the delay error when mounting the XFAT mechanical hard drive on the desktop.

Just to confirm, you are saying that ExFAT volume access slows down AFTER you apply OCLP modern Wi-Fi patches and that ExFAT volume access is faster BEFORE you apply OCLP modern Wi-Fi patches.  Is that correct?

 

EDIT: Or are you saying that simply downgrading / injecting the Wi-Fi kexts with Open Core (without applying OCLP root patches) causes the ExFAT performance issue?

Edited by deeveedee
  • Like 1
10 minutes ago, deeveedee said:

Just to confirm, you are saying that exFAT volume access slows down AFTER you apply OCLP modern Wi-Fi patches and that exFAT volume access is faster BEFORE you apply OCLP modern Wi-Fi patches.  Is that correct?

I need to check, but for that I need a mechanical disk, which I don’t have.

31 minutes ago, deeveedee said:

Just to confirm, you are saying that ExFAT volume access slows down AFTER you apply OCLP modern Wi-Fi patches and that ExFAT volume access is faster BEFORE you apply OCLP modern Wi-Fi patches.  Is that correct?

 

EDIT: Or are you saying that simply downgrading / injecting the Wi-Fi kexts with Open Core (without applying OCLP root patches) causes the ExFAT performance issue?

Not without applying the OCPL patch with the kexts installed and the Wi-Fi icons grayed out. That is, before applying the OCPL patch, be prepared to do so, which you can do or not; in my case, I didn't because I use a wired network.

  • Like 1
21 minutes ago, kaoskinkae said:

Not without applying the OCPL patch with the kexts installed and the Wi-Fi icons grayed out. That is, before applying the OCPL patch, be prepared to do so, which you can do or not; in my case, I didn't because I use a wired network.

Sorry, but I still do not understand. As long as @MakAsrock understands, that's ok.

 

Does this have to be tested with a mechanical drive, or can the ExFAT be created on a USB or SSD?

 

Best to move this discussion to the OCLP-Mod/Experimental thread.

  • Like 1

I installed Tahoe  26.4 on a mechanical drive and have no OCLP. There is also Data partition as exFAT.

All is good. After Tahoe started I have to wait several minutes until Data will be mounted. 

FileVault is disabled at the bootloader level to be never ON after updates.

I stopped Documents and Desktop synchronisation with iCloud. It was very slow.

  • Like 2
1 hour ago, deeveedee said:

Just to confirm, you are saying that ExFAT volume access slows down AFTER you apply OCLP modern Wi-Fi patches and that ExFAT volume access is faster BEFORE you apply OCLP modern Wi-Fi patches.  Is that correct?

 

EDIT: Or are you saying that simply downgrading / injecting the Wi-Fi kexts with Open Core (without applying OCLP root patches) causes the ExFAT performance issue?

I created an ExFAT file system on a USB drive and didn't notice any difference. It runs very slowly with or without the patch, but I have a very slow drive.
I found a 3.5" Seagate Barracuda 8 TB ST8000DM004 SATA 6Gb/s (SATA-III) hard drive in the storage room, and it also didn't make any difference.

  • Like 1

Fix thread_invoke and thread_dispatch TSC non-monotonic panic on Darwin 25.4.0+(26.4+) for AMD Laptop.

 

PR: https://github.com/AMD-OSX/AMD_Vanilla/pull/215

 

Edited by laobamac_yyds
  • Like 1
  • 3 weeks later...
On 3/29/2026 at 12:16 PM, laobamac_yyds said:

Fix thread_invoke and thread_dispatch TSC non-monotonic panic on Darwin 25.4.0+(26.4+) for AMD Laptop.

 

PR: https://github.com/AMD-OSX/AMD_Vanilla/pull/215

 

Thank you very much, comfirmed working on Lenovo Legion laptop!

  • Like 2
×
×
  • Create New...