All Activity

Big thanks, @MaLd0n for you sources 4.1. I take from them a minimal part of AMD HDMI hot-plug and it works!!! My version is 3.6.2. I have a purpose to write only minimal right codes without quirks and workarounds so that it will be the good basis for a new investigations. Hope my sources are academic. VoodooHDA.kext-362.zip

@Alpha22 Thanks for the feedback

Update completed, no problems

@MakAsrock There is no privileged_helper_tool the author delete it two days a go, dont know why? because it must be there and make debug

Hi guys, New version is available for update with the app's built-in update feature. Let me know if you found a bug or ran into any issues.

Hi guys, New version is available for download via app's built-in update Improved the progress steps on USB disk creation to exactly parse terminal's output as it runs the createinstallmedia command. Minor bug fixes and updated Donation link and QR Code in the app. let me know if you ind any bugs or ran into any issues.

@MakAsrock I'm sure that the author appreciated your testing results and feedback.

You can also try my old soft power table. Also: If you use WhateverGreen, you need the Boot argument `agdpmod=pikera` Devices.plist.zip

Thanks @MakAsrock I added the framebuffer to the existing pci path, I did not use the one you provided. I will do some tests again when I have a chance.

You need to check the PCI path to your video card. I've provided mine as an example only: PciRoot(0x0)/Pci(0x1.0x0)/Pci(0x0.0x0)/Pci(0x0.0x0)/Pci(0x0.0x0) Your path may be different, and you may have added framebuffer entries to Bluetooth by mistake. Creating your own softpowerplaytable is recommended, but not required. I created one to prevent the card from overheating and the fans from spinning at maximum speed (slight undervolting and a custom Zero-RPM). I have a Fenvi FV-HB1200 ac Hackintosh WiFi and Bluetooth, it works fine.

Results RX 560M MACBOOKPro with latest Version (running with / without new TOSH_W64_PREFILL=1 - I didn't used that together with W64WAVE argument together) Best generation BENCH much faster compared to versions of last week (1.3 > 9.5 4B / 1.2 > 2.6 8B). Also Promt BENCH faster but "only2 15% FASTER.

IMHO, the human brain is a mystery—the most complex organ with the most intricate mechanisms in the universe. The reason AI still can't compete with our brain is simply due to our power of reasoning and our ability to find solutions to the problems we are presented with. This ability was perfected over millions of years, whereas AI has only been around for about 20 years or so. The speed at which AI can operate is amazing, and the way it improves is truly stunning. But there is a caveat: the reasoning and thinking process of AI is completely based on our knowledge and the data we give it. It's not perfect, it's not complete, and it's still evolving. As a developer, you have a wealth of experience doing what you do; no AI model can compete with what your brain can achieve just yet. It is you who controls the AI, not the other way around (yet!). AI still has a long way to go, but using tools to solve our problems and make things easier is one of our most amazing traits. AI is a great tool for a lot of tasks, but the human thought process is our most distinctive ability—the one that separates us from any other species on Earth (though I'm not sure about the entire universe!). Working with AI makes me feel like I have a great team of programmers and coders at my disposal, but we are still the ones who must point them in the right direction. Sometimes, AI simply lacks the vision and skills to find the correct solution. When I want AI to do something for me, it's never as easy as saying, "Create an app that does this or that." It requires giving it specific, detailed instructions, reviewing the output over and over, and debugging and testing until I get the results I want. Sometimes, the output still isn't what I looked for—so I completely agree with you there. But what amazes me is how rapidly AI is evolving. When I first started using it, it genuinely felt like my early days of learning how to work with computers. It was, and still is, incredibly exciting. Is it perfect? No. Is it fun? Yes! Do I need to learn a new language? Yes—I need to learn how to tell the AI exactly what I want and how to direct it to get the results I'm looking for. Many giant companies use AI to write their code, but our supervision and problem-solving abilities remain the most critical part of the equation.

Keep it coming @kgp 👌 If I recall, there was a fork of itlwm trying to merge all the patches into a single AirportItlwm. can't seem to find it anymore

no worries @MaLd0n we're here till the end of tahoe 😁

[ 36 ] 2026-07-13 20:59:22 .. 122-87489 .. 27.0.0.26A5378n macOS 27 Golden Gate Beta https://swdist.apple.com/content/downloads/14/57/122-87489-A_SX0HEXJAU8/owrlogyrsvvf0k1ezadignujdczc8gxbim/122-87489.English.dist https://swdist.apple.com/content/downloads/14/57/122-87489-A_SX0HEXJAU8/owrlogyrsvvf0k1ezadignujdczc8gxbim/InstallAssistant.pkg <key>BUILD</key> <string>26A5378n</string> <key>VERSION</key> <string>27.0</string>

Yeah! Thanks!!

Hi @LockDown , for my earlier itlwm/HeliPort tests, I used HeliPort 1.5.0 from the official OpenIntelWireless repository: https://github.com/OpenIntelWireless/HeliPort Just to avoid any confusion: my current experimental OCLP/AirportItlwm setup described here does not use HeliPort. HeliPort is only required when using itlwm.kext. I am currently working privately on my own AirportItlwm development branch, using @DexterSLamb’s itlwm/AirportItlwm fork merely as the initial code base: https://github.com/DexterSLamb/itlwm My own work specifically focuses on AWDL/AirDrop functionality. These modifications are not part of Dexter’s fork, and none of my own development work has been published yet.

@MakAsrock I added the framebuffer entries and immediately after rebooting, the bluetooth stopped working, so I removed the framebuffer entries, rebooted and the bluetooth was back. Could it be related to the softpowerplaytable that I also have defined which conflicts with the framebuffer? If yes, why would the bluetooth stop working? It's a behaviour that quite frankly I don't understand. At least the freezing stopped after tweaking the indexing settings and remove the garbage in the config file.

HI @kgp which Heliport repo are you using?

@MakAsrock thanks for the tip! I’ll verify this definitely. I also inadvertently left some residuals from the BCM card that I replaced with the Intel Ax210 last week and this could have been causing problems too. @deeveedee I did disable indexing for some folders and non-Mac drives and it seems to be better now. I also cleaned up the config file as I noticed I left some stuff related to the AppleBCMWLANCompanion kext that I no longer use after I put back the Intel AX210 card. I’m hoping that I don’t get any freezing going forward.

The author quickly fixed this issue, and the patcher worked, but I couldn't log in afterward because wifip2pd, which is required but incompatible with Tahoe, was installed. The only thing that helped me was this: 1. sudo mount -uw /Volumes/SN850 2. sudo bless --mount /Volumes/SN850 --bootefi --last-sealed-snapshot I won't be testing it again because it's broken. 😉

Your problem isn't related to Spotlight indexing pushing the CPU too hard. It's related to the RX-6600 card, or more specifically, the buggy default framebuffer. I solved this issue with a named framebuffer. Added properties: <key>DeviceProperties</key> <dict> <key>Add</key> <dict> <key>PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)</key> <dict> <key>@0,name</key> <string>ATY,Henbury</string> <key>@1,name</key> <string>ATY,Henbury</string> <key>@2,name</key> <string>ATY,Henbury</string> <key>@3,name</key> <string>ATY,Henbury</string> </dict> </dict> <key>Delete</key> <dict/> </dict> Now this card died and I installed AMD Radeon RX 5700XT It has the same problems, but the properties are different: <key>PciRoot(0x0)/Pci(0x1.0x0)/Pci(0x0.0x0)/Pci(0x0.0x0)/Pci(0x0.0x0)</key> <dict> <key>@0,name</key> <string>ATY,Adder</string> <key>@1,name</key> <string>ATY,Adder</string> <key>@2,name</key> <string>ATY,Adder</string> <key>@3,name</key> <string>ATY,Adder</string> </dict> </dict> <key>Delete</key> <dict/> </dict> I'm still using 26.5.2 and don't have any problems anymore. 😉

Smooth update. Is this really RC5?!?!