Jump to content
10 posts in this topic

Recommended Posts

Grab these and Install them:

Kernel_Debug_Kit_26.0_build_25A5279m.dmg

Kernel_Debug_Kit_26_build_25A353.dmg

 

Go to: /Library/Developer/KDKs/KDK_26.0_25A5279m.kdk/System/Library/Extensions

 

Copy AppleHDA.kext to the Desktop, Right Click Copy, Right Click Paste....

 

Using MyKextInstaller 4.2 it HAS to be 4.2..... Click Install Kext, and Select AppleHDA.kext,

 

when it finishes asking you for the password a hundred times, it'll ask to reboot,

 

when it reboots it'll say Update to macOS Tahoe Successful, asks you for your iCloud Password

 

and when you Log in you will have working AppleHDA.

 

Yes this is for the Build released on Sept 15th. As I can see Opencore, SimpleLoader, and the Newer MyKextInstaller why they don't all work I don't know... this is the only thing that does apparently..

Edited by fspkwonx86
  • Like 2
  • 2 weeks later...

Users who exclusively utilize the iGPU's HDMI audio, bypassing the motherboard's internal audio controller,

are not required to disable System Integrity Protection (SIP) and can successfully boot with a Secure Boot model enabled in OpenCore.

The necessary configuration simply involves injecting the hda-gfx property for both the HDA controller and the iGPU within the

DeviceProperties section of the OpenCore config.plist. Consequently, the native AppleGFXHDA kext will be loaded as expected.
 

<key>#WARNING - 1</key>
<string>This is just a sample. Do NOT try loading it.</string>
<key>PciRoot(0x0)/Pci(0x1F,0x3)</key> 
<dict>
	<key>hda-gfx</key>
	<string>onboard-1</string>
	<key>#your-layout-id-delete-me</key>
</dict>
<key>PciRoot(0x0)/Pci(0x2,0x0)</key>
<dict>
	<key>#your-configuration-delete-me</key>
	<key>hda-gfx</key>
	<string>onboard-1</string>
</dict>

 

  • Like 2

perfect that does apply to any user trying to use kabylake graphics chipsets only i think those use whatevergreen or tahoe

may require whatevergreen even on supported chipsets itll work but has no identification Acceleration with no Identification Strings

like your using Iris Plus 640 with X-Ram...

 

im posting now the only other required addition for full functionality (basically) on an iMac 18,1 2017 - non retina is now 100% tahoe

supported (basically) give or take FeatureEnabler...  is we just freaking got Wifi Back

  • Like 2
  • 4 weeks later...
On 9/28/2025 at 3:44 PM, fspkwonx86 said:

perfect that does apply to any user trying to use kabylake graphics chipsets only i think those use whatevergreen or tahoe

may require whatevergreen even on supported chipsets itll work but has no identification Acceleration with no Identification Strings

like your using Iris Plus 640 with X-Ram...

 

im posting now the only other required addition for full functionality (basically) on an iMac 18,1 2017 - non retina is now 100% tahoe

supported (basically) give or take FeatureEnabler...  is we just freaking got Wifi Back


Did you manage to get Wi-Fi working?
I’m modifying OCLP to use on Tahoe — I just finished compiling everything and will start testing now, just waiting for Time Machine to finish. If everything works as expected, I’ll make a post afterward.

image.thumb.png.983f71d5d26c93dca40ea6b1a8aeba0a.png

  • Like 2
7 hours ago, #McFly said:


Did you manage to get Wi-Fi working?
I’m modifying OCLP to use on Tahoe — I just finished compiling everything and will start testing now, just waiting for Time Machine to finish. If everything works as expected, I’ll make a post afterward.

image.thumb.png.983f71d5d26c93dca40ea6b1a8aeba0a.png

Yes, the Wi-Fi of bcm4360 doesn't work.This is really good news. Thank you for your hard work, brother. Good luck.

Edited by cfmwan
  • Like 3
On 10/23/2025 at 4:58 PM, #McFly said:


Did you manage to get Wi-Fi working?
I’m modifying OCLP to use on Tahoe — I just finished compiling everything and will start testing now, just waiting for Time Machine to finish. If everything works as expected, I’ll make a post afterward.

image.thumb.png.983f71d5d26c93dca40ea6b1a8aeba0a.png

it worked perfectly now since i just round tripped gentoo and back and freebsd and back im looking for oclp and just as id find all the builds are expired 

  • Like 2
  • 3 weeks later...
On 10/29/2025 at 7:55 PM, fspkwonx86 said:

it worked perfectly now since i just round tripped gentoo and back and freebsd and back im looking for oclp and just as id find all the builds are expired 

 

My build is private for security reasons so that no one can download it and get a Kernel Panic.
I made a lot of modifications and had to stop for the last few days, my focus was on Wifi BCM and Intel, as no one has managed to make it work yet.
Try using the laobamac mod. (Chinese version, if you have difficulties, use a translator using your cell phone camera)
laobamac-OCLP-Mod

  • Like 2
6 hours ago, #McFly said:

 

My build is private for security reasons so that no one can download it and get a Kernel Panic.
I made a lot of modifications and had to stop for the last few days, my focus was on Wifi BCM and Intel, as no one has managed to make it work yet.
Try using the laobamac mod. (Chinese version, if you have difficulties, use a translator using your cell phone camera)
laobamac-OCLP-Mod

right now im actually on device-specific dsdt fixes (work cited multiple sources of allllllllll the little fixes that come before you even think about devices new and old cpus and what semantics it all appears as), and since i dont know if this laptop im using right now has the Intel HDA Jumper Pin for BIOS Unlock (Dell) I have to figure out if 1. All EFIs have a BIOS Block, they shift from 4/8/16MB Blocks and the Number of Regions that get flashed pretty basic, broken down into Keys i get that, Changing the Bitmap and running it against UEFIPatch to Unlock MSRs... I have to figure out how to Flash it though... I have an Intel Wifi that ITWLM works but the Bluetooth is the big question.... as for the iMac i have iMac 18,1 Non-Retina 2017 Kabylake running Tahoe and it runs Beutifully with your Broadcom Driver even the KDK Disk Update darwin-development....  I just shut debugging off and i can still do IOKit Level Kext stuff like its able to send a series of VERB commands and report which ones work using AppleHDA Hooking and this is all on Tahoe that its working

  • Like 2
On 11/19/2025 at 11:11 PM, fspkwonx86 said:

right now im actually on device-specific dsdt fixes (work cited multiple sources of allllllllll the little fixes that come before you even think about devices new and old cpus and what semantics it all appears as), and since i dont know if this laptop im using right now has the Intel HDA Jumper Pin for BIOS Unlock (Dell) I have to figure out if 1. All EFIs have a BIOS Block, they shift from 4/8/16MB Blocks and the Number of Regions that get flashed pretty basic, broken down into Keys i get that, Changing the Bitmap and running it against UEFIPatch to Unlock MSRs... I have to figure out how to Flash it though... I have an Intel Wifi that ITWLM works but the Bluetooth is the big question.... as for the iMac i have iMac 18,1 Non-Retina 2017 Kabylake running Tahoe and it runs Beutifully with your Broadcom Driver even the KDK Disk Update darwin-development....  I just shut debugging off and i can still do IOKit Level Kext stuff like its able to send a series of VERB commands and report which ones work using AppleHDA Hooking and this is all on Tahoe that its working

For MSR, this might help.
Alternative method
Intel BL (My build)
With my build I was able to connect the MX Keys keyboard.
image.png.20405c22d0c580c3e3a0f58e102aea77.png


1. IntelBTPatcher.kext
2. IntelBluetoothFirmware.kext
3. BlueToolFixup.kext (2.7.1)

  • Like 2
3 hours ago, #McFly said:

For MSR, this might help.
Alternative method
Intel BL (My build)
With my build I was able to connect the MX Keys keyboard.
image.png.20405c22d0c580c3e3a0f58e102aea77.png


1. IntelBTPatcher.kext
2. IntelBluetoothFirmware.kext
3. BlueToolFixup.kext (2.7.1)

I have to do something similar but hit a roadblock in the Touchpad/Trackpad of the Dell System, Alot of OEMs have their own BIOS 1. and Trackpads 2. well NOW atleast they do.

so instead of voodooi2c voodoops2 im going to try VoodooRMI...  and experiement if that works with getting the Intel Bluetooth working...  and finishing my ACPI Works Cited , i figured out the trackpad it requires changing some method names its just unclogging the Device, Renaming some sections and then letting that do its thing with a proper plugin load order

Edited by fspkwonx86
  • Like 1
×
×
  • Create New...