All Activity

Does anybody know why Yosemite has always volume muted after rebooting? I happens on both Mac and Hackintosh.

@LockDown That makes sense. The VoodooHDA.kext 3.6.4 Info.plist includes attribute LSMinimumSystemVersion = 10.13 (macOS High Sierra). If that is accurate and VoodooHDA targets 10.13 and later, then custom builds may be required for macOS versions earlier than High Sierra.

@Majonéz The 15.7.8 pre-release versions have problems with some VPNs and firewalls (e.g., Norton's Transparent Proxy is broken). Are you using any 3rd-party VPNs or Firewalls? For Norton's Firewall, toggling Transparent Proxy off and then on again fixes the problem until the next log-on.

Gmail and Exchange accounts have been broken since the first 15.7.8 build and are still broken in 24G824. They can't be added in Internet Accounts, and Mail won't connect to existing accounts either.

I do custom building to support my unlisted Yosemite

I think no one needs custom building. You have nothing to change except info.plist 364 and 365 have a big difference in 192kHz rate.

work === MAPPING DERIVED FROM MEASUREMENT === efficiency: Te05, Te0S * performance: Tp1j, Tp1n, Tp1t, Tp1w, Tp25, Tp28, Tp2B, Tp2E, Tp2J, Tp2M * a single key shared by 2 E-cores, and that is correct, 2 keys for 4 E-cores Thanks for your tests; you finally have the correct temperatures for all the cores.

sensor-verification-Mac16,9-1785003996.txt

@Max.1974 No offense, but that doesn't make any sense to me. Do you have a reference about this that I can learn from. I personally don't think anyone needs to be custom-building VoodooHDA, but I'm open to having my mind changed. If anyone else believes that they need to custom-build VoodooHDA, I'd like to learn why you think so. Thanks for your patience with my learning.

@Max.1974 @Slice @MaLd0n Should we all be building a custom VoodooHDA for our hacks? I have always used the kexts provided by Slice and MaLd0n (modifying only Info.plist as needed), but I'm open to your advice if you think that re-building the kext makes any difference.

Hi all — Kernel Inspector just got a big update (1.1.0). It still opens a .kext bundle or any Mach-O binary and lets you dig through it (think a lightweight Hopper), but the Hackintosh side has grown a lot: it now generates SSDTs, derives OpenCore patches from your own machine, and maps USB ports — on top of the install/maintenance chores it already did. Download: https://github.com/luminadevapps/KernelInspector/releases Source: https://github.com/luminadevapps/KernelInspector NEW IN 1.1.0 - SSDT Generator — pick your hardware, generate the maintenance SSDTs (AWAC, PMC, USBX, EC, PNLF, GPRW, RHUB, ALS0…), compile DSL → AML with iasl, then install the .aml straight into a mounted OpenCore EFI and register it under config.plist → ACPI → Add. It even adds the required renames (EC→EC0, _GPRW→XGPW) for you. - USB Ports — live view of your USB controllers from IOKit. Toggle which ports to keep, set each connector type, and auto-trim to the 15-port cap. - XCPM / CPU — the verified CPU power-management + topology patch set (AppleXcpmExtraMsrs, AppleCpuPmCfgLock, core-count fixes). Copy any entry as a config.plist patch, or verify it against your live Kernel Collection after a macOS update. - Port-Limit Patch — derives the XHCI port-limit patch from real bytes (a loaded binary or your live Kernel Collection) instead of a hard-coded pattern that only matches one build, with an optional universal (masked) variant. - Install Kexts now also targets a mounted OpenCore EFI and can restore AppleHDA on Tahoe via a KDK root patch; Maintenance gained per-volume config.plist access. WHAT IT DOES Analyze - Info.plist — kext identifier, version, UUID, linked libs, full searchable Info.plist - Hex Editor — byte view with hex find & replace and patch-to-file - Symbols — full nlist_64 table with global/local/undefined/debug filters - Disassembly — ARM64 / x86-64 of __text, colour-coded by branch/call/return - Control Flow — per-function basic-block graph - Pseudocode — heuristic pseudo-C (readability aid, not a decompiler) - Port-Limit Patch — derive an XHCI port-limit OpenCore patch from real bytes System (Hackintosh) - Install Kexts — readiness dashboard (SIP / macOS build / target / cache tool), install a .kext to /Library/Extensions or into your OpenCore EFI (auto-adds Kernel→Add + plugins to config.plist, backs it up first), rebuild caches, restore AppleHDA (Tahoe/KDK), uninstall - Maintenance — ESP-mounter style EFI partition mount/unmount, Kernel Debug Kit manager, per-volume config.plist viewer, APFS snapshot cleanup - USB Ports — live IOKit port map with keep/trim and the 15-port cap check - XCPM / CPU — verified CPU/XCPM patch set, checked against your live kernel - SSDT Generator — generate, compile and install OpenCore SSDTs from your hardware All privileged steps use the standard macOS admin prompt — the app never sees your password. INSTALL 1. Download KernelInspector-1.1.0.dmg from the Releases page 2. Drag Kernel Inspector into Applications 3. First launch only: right-click → Open → Open (it's ad-hoc signed, not notarized) Needs macOS 13+ and the Xcode Command Line Tools (xcode-select --install) — the disassembler shells out to otool/llvm-objdump. The SSDT Generator's compile step needs iasl (e.g. brew install acpica). NOTES Pseudocode/CFG are heuristic. Parser targets 64-bit Mach-O. The XCPM/CPU patches are verified on a specific machine (i9-13900K, macOS 26.x) — always re-verify against your own kernel after an update. The port-limit patch is a temporary aid for USB mapping; drop it once you've built a proper USBMap. It's a study/RE + Hackintosh aid for hardware you own. Feedback and bug reports welcome — cheers!

For Gigabyte Aorus Z790 Elite AX F16 (Bios) VoodooHDA-3.6.5.kext.zip

new info hardware

Hello Im Nick! I am trying to learn kernel development through macOS and through the last 10 years i've successfully made alot of hackintoshes. I used to daily drive a Tiger 10.4.8 and a Leopard 10.5.2 on the same Dell Latitude D505 for almost two years back in 2014-2015! It was a jam and since then I've came back to the hackintosh scene with renewed will for tinkering and learning!

Hello people and thank you for your work! I was aspiring of learning kext development for macos since i like the system and hackintoshing, so I took upon myself the challenge of making a kext for a wifi dongle I have. I am completely new at this so it was a bit of a challenge for me getting the device to match, initialising it, communicating with it (e.g. getting it to reply its firmware version) and (currently) trying to manage the sleep-awake path. For all this to happen, I started reading the book OS X and iOS Kernel Development. Development started on a very old Macbook4,1 (since the book I have targets old OS X 10.6-10.7 and I wanted to avoid the hassle of newer protection measures that make development difficult). I also own a newer macbook pro 14,1 so development there was much smoother (running Catalina). I'd like to ask now, any experienced people for advice, pointers and as many sources as possible so that I could read and learn. I am using Claude as a helping tool when I am completely stuck but I am not happy with the fact that it singlehandedly fixes all my problems without me learning alot! And finally, I'd like to ask the most important question: Is there any way for me to do development on newer macOS Tahoe? I can't stand the fact that i have to reboot after every change i make to the driver, and I'd like to know how to make my life easier if possible! Once, I have some of the parts I want ready, I will opensource the driver, aswell! - Nick

test this versions https://github.com/Lorys89/App-test/raw/refs/heads/main/M4 MAX-SiliconMonitorCenter 1.0 b9.zip Start the sensor check, and once it's finished, send me the generated file.

My compiled version 3.6.5 is good! Using my VoodooHDA Builder For Gigabyte Aorus Z790 Elite AX F16 (Bios)

Screen mirroring to Apple TV working perfectly with Intel AX201, itlwm/heliport, macOS Tahoe 26.6 (25G70). Audio and video are perfect. System specs HP EliteBook 850 G7 Laptop (i7-10610u / 10th Gen Intel UHD Graphics - see framebuffer patching here) macOS Tahoe 26.6 (25G70) Open Core 1.0.7 SIP csr-active-config = <01000000> Wi-Fi: Intel AX201, itlwm.kext / heliport Audio: VoodooHDA.kext 3.6.4 No root patching

Here a nice Background I have created to use with Flavours-AppleSet theme or any other themes Attaching Background resize for all screen size Choose your background then rename it Background.icns NOTE: The Background-3840x2160.icns file is intended for a 1920x1080 screen, so its size is always double. Background-7680x2880.icns.zipBackground-3360x2100.icns.zipBackground-3840x2160.icns.zip Background-3840x2400.icns.zipBackground-5120x2880.icns.zipBackground-3200x2400.icns.zip Background-3200x1800.icns.zipBackground-2880x2160.icns.zipBackground-2880x1800.icns.zip Background-2048x1536.icns.zipBackground-2560x1600.icns.zipBackground-2732x1536.icns.zip This is what it look like

You did well, macos27 as the main os I don't recommend it, it still has bugs. Macos26 works very well. Thank you for the files and your tests.

I downgraded back to macOS 26.5. sensor-dump-Mac16,9-20260725-082734.txtsensor-verification-Mac16,9-1784925209.txt

I suppose we are talking about a laptop with the integrated graphics card disabled and an external NVIDIA GeForce GT 555M graphics card.

Thank you, @Slice. I am currently testing VoodooHDA.kext 3.6.4 with analog InhibitCache=false on my HP EliteBook 850 G7 laptop. Is that the only difference between 364 and 365? Analog HDA Audio quality is outstanding.

Guys, build b9 is ready; it would be great if you have an M5 (including Pro and Max variants) to test it on. I’m looking forward to sensor verification tests, sensor dumps, and diagnostic reports (from M1 to M5). Thanks for your testing and the time you dedicate to helping me. https://github.com/Lorys89/App-test/raw/refs/heads/main/SiliconMonitorCenter 1.0 b9.zip

I installed all kexts to System/Library/Extensions on my SATA MacBook and recreated the kextcache. Then I created from the installer disk utility a dmg of this volume. I wrote it on a partition on my NVME MacBook and it's working. My desktop system has a Core i7 3770S and a Sapphire GPRO 4200 GPU, which is based on the Radeon R7 250x. It also uses AMD7000Controller.kext like the R9 370X in the MacBookPro11,5. The MacBook version doesn't need the OSx86 drives and most of the OSx86 tools. My Kingston 4 TB SSD has 2.1 GB read and 2.6 GB write. Counting from the Apple logo, Yosemite needs just 9 seconds to reach the desktop.