RSS Feed

Nullmoth 1401 error creating usb

Sun, 11 Oct 2026 18:14:02 +0000

Hi, sorry to bother you, I'm having a problem with the creation of the USB: when I press "build" after a few seconds I get an error asking me to disable the VMD, but after looking online I saw that my computer has NO way to disable it, what can I do?

NVIDIA Graphics Acceleration on macOS - NullMoth NVIDIA Driver | GeForce GTX 16, RTX 20/30/40/50

Sat, 10 Oct 2026 21:32:42 +0000

Hello everyone! I'd like to share an interesting project with the Hackintosh community: NullMoth NVIDIA Driver for macOS, a source-available graphics driver developed by NullMoth Systems that aims to bring NVIDIA GPU acceleration back to modern macOS systems. For years, NVIDIA graphics support has been one of the biggest limitations for Hackintosh users, particularly since Apple discontinued support for NVIDIA Web Drivers in newer macOS releases. NullMoth takes a different approach by implementing a graphics driver stack that connects Apple's Metal framework to NVIDIA hardware through a combination of shader translation, Mesa's NVK Vulkan driver, and NVIDIA's open GPU kernel modules. The project is currently focused on macOS Sequoia running on Intel-based Macs and OpenCore systems, with support targeted at NVIDIA Turing and newer GPU architectures. Important: This is a new and experimental project. Broad GPU compatibility has not yet been physically validated, and functionality may vary considerably between systems. Supported NVIDIA GPUs The driver's device table covers several NVIDIA GPU generations: Architecture GPU Families Turing GeForce GTX 16, RTX 20, TITAN RTX Ampere GeForce RTX 30 Ada Lovelace GeForce RTX 40 Blackwell GeForce RTX 50 Workstation Selected Quadro, RTX A and RTX PRO GPUs Support for a GPU's PCI device ID does not necessarily mean that the card has been successfully tested on macOS. According to the project's documentation, physical testing has primarily focused on the GeForce RTX 5060, with additional working reports for RTX 5070 and RTX 5080 configurations. Other GPUs are included through NVIDIA's supported hardware tables but still require further testing. Older architectures such as Pascal, Maxwell and Kepler are outside the scope of the current implementation. Graphics Features The project implements a number of graphics technologies and interfaces, including: Metal graphics acceleration Metal 3 interfaces OpenGL through Apple's GL-on-Metal implementation OpenCL compute support Core Image integration Metal Performance Shaders (MPS) Core ML integration Vulkan-based graphics execution through Mesa NVK GPU-accelerated desktop composition NVIDIA framebuffer and display management Support for multiple display outputs Hardware H.264 decoding on supported GPUs Shader compilation through the NAK compiler Implementation paths for ray tracing, mesh shaders and MetalFX Feature availability depends on the GPU, macOS configuration and driver implementation. Not all features or applications have been independently validated across every supported GPU generation. How Does It Work? Unlike traditional NVIDIA Web Drivers, NullMoth uses a different graphics architecture. The driver connects Apple's Metal interface to NVIDIA hardware using several components. 1. Metal Driver Plugin The NVMTLDriver.bundle component implements Metal interfaces used by applications and the macOS graphics system. 2. Shader Translation A shader translation layer converts Apple's AIR intermediate representation into SPIR-V, allowing shaders to be processed through the Vulkan graphics pipeline. 3. Mesa NVK The project uses Mesa's open-source NVK Vulkan driver and NAK shader compiler to generate NVIDIA GPU instructions and execute graphics workloads. 4. NVIDIA Open GPU Kernel Modules The kernel-side implementation adapts NVIDIA's open GPU kernel modules to the macOS XNU environment. 5. Framebuffer and Acceleration Components Additional kernel extensions provide framebuffer functionality, graphics acceleration integration and display policy handling. The resulting architecture can be summarized as: Metal Application → Metal Driver Plugin → Shader Translation → Mesa NVK → NVIDIA Kernel Driver → GPU This approach is particularly interesting because it does not depend on the traditional proprietary NVIDIA Web Driver architecture previously used on older macOS releases. macOS Compatibility The current driver targets: macOS Sequoia (Intel / x86_64) OpenCore is required for the supported configurations. The project is not an official NVIDIA or Apple graphics driver. Compatibility with other macOS releases should not be assumed unless explicitly documented by the developers. Apple Silicon Macs are not part of the current supported platform. Installation and Requirements The project provides prebuilt driver packages and a companion installation application. For an existing Hackintosh installation, the basic requirements include: A compatible NVIDIA GPU macOS Sequoia A working OpenCore configuration Appropriate BIOS/UEFI graphics settings The required macOS security and kernel-extension configuration The NullMoth NVIDIA driver package The installation process involves configuring OpenCore, installing the driver components and rebuilding the required macOS kernel collection. The project also provides the 1401 Mac application, designed to simplify installation, configuration, logging and removal of the driver. For users installing macOS from Windows, the separate 1401 project provides tools for preparing the installation media and OpenCore environment. Please note: Installation requires changes to security-related settings, including SIP and Secure Boot configuration. These changes have security implications and should only be made after reviewing the official documentation. The developers recommend following the instructions provided in the repository rather than assuming that settings from older NVIDIA Hackintosh configurations will work. Current Limitations Despite the progress described by the project, there are still important limitations. The developers document ongoing issues involving: Screen flickering on certain high-refresh-rate configurations Flickering with some multi-monitor setups HDMI and DisplayPort audio output from the NVIDIA GPU Hardware compatibility differences between desktop and laptop systems Limited physical validation across the advertised GPU families Laptop configurations may also require a direct display connection to the NVIDIA GPU. The driver does not automatically provide support for NVIDIA Optimus switching or unsupported display routing. This remains experimental software and should not yet be considered a drop-in replacement for a fully mature graphics driver. Download and Source Code Official Project Repository https://github.com/nullmoth/nvidia-macos-driver Driver Downloads and Releases https://github.com/nullmoth/nvidia-macos-driver/releases 1401 – macOS Installation and Configuration Tools https://github.com/nullmoth/1401 Technical Documentation https://github.com/nullmoth/nvidia-macos-driver/blob/main/docs/HOW-IT-WORKS.md GPU Compatibility Information https://github.com/nullmoth/nvidia-macos-driver/blob/main/docs/CARD-SUPPORT.md Official Website https://nullmothsystems.com The repository includes driver components, installation tools, source code, build instructions and technical documentation. Credits & Acknowledgments This project builds upon multiple graphics technologies and open-source components developed by the broader software and GPU development community. Full credit belongs to their respective developers and maintainers. NullMoth Systems Development and maintenance of the NullMoth NVIDIA Driver for macOS. Metal driver implementation, integration, macOS compatibility layers and installation utilities. Anees Iqbal (steelbrain) Original developer of metal2vulkan, the project upon which NullMoth's shader translation component is based. https://github.com/steelbrain/metal2vulkan Mesa Developers and Contributors Development of the Mesa graphics stack, including the NVK Vulkan driver and NAK shader compiler. https://mesa3d.org NVIDIA Corporation NVIDIA Open GPU Kernel Modules and GPU System Processor firmware used by the project. https://github.com/NVIDIA/open-gpu-kernel-modules Acidanthera and OpenCore Contributors Development of OpenCore and related technologies used by the Hackintosh community. https://github.com/acidanthera/OpenCorePkg Special thanks to everyone involved in Mesa, NVIDIA open driver development, reverse engineering, testing and documenting graphics technologies. Licensing The project is available free of charge with source code, but it is not licensed for unrestricted commercial use. The main NullMoth components are distributed under the PolyForm Noncommercial License. Third-party components retain their respective licenses, including LGPL for the shader translator, MIT for Mesa-related changes and NVIDIA's applicable licenses for kernel modules and firmware. Please review the repository's LICENSE and NOTICE files before redistributing or modifying the software. Final Thoughts The NullMoth NVIDIA Driver is an ambitious effort to address one of the most significant limitations of modern Hackintosh systems: NVIDIA graphics acceleration. Its architecture, combining Metal compatibility layers, Mesa NVK, shader translation and NVIDIA's open kernel modules, represents an interesting alternative to the legacy NVIDIA Web Driver approach. Although the project is still experimental and requires considerably more hardware testing, it may open new possibilities for users with NVIDIA Turing, Ampere, Ada Lovelace and Blackwell GPUs. Community testing and feedback are welcome! If you're testing the driver, consider sharing: NVIDIA GPU model and PCI Device ID CPU and motherboard macOS build OpenCore configuration Display connections and refresh rates Working features and known problems Relevant logs or crash reports Sharing detailed results can help the developers identify compatibility problems and improve the project. As always, back up your OpenCore EFI and macOS installation before making driver or system modifications. Official GitHub: https://github.com/nullmoth/nvidia-macos-driver Thanks to NullMoth Systems and all the developers contributing to graphics driver development and the Hackintosh community!

WhateverXe - Intel Xe-LP Graphics Acceleration for macOS | Tiger Lake, Alder Lake-N & Twin Lake

Sat, 10 Oct 2026 21:28:06 +0000

I'd like to introduce WhateverXe by b00t0x, an open-source project designed to bring graphics acceleration to selected Intel Xe-LP integrated GPUs on macOS. Derived from WhateverGreen and built on top of Lilu, WhateverXe adapts Apple's graphics drivers to work with Intel integrated graphics architectures that are not officially supported by macOS. The goal is to extend Hackintosh compatibility to newer Intel platforms while providing functional hardware acceleration, external display support, and other GPU-related features. This is an experimental project under active development. Compatibility and functionality may vary depending on the hardware configuration. Supported Intel Graphics The project currently includes implemented support for the following GPU families: Intel Platform Device IDs Tiger Lake 9A40, 9A49, 9A78 Alder Lake-N 46D0–46D4 Twin Lake 46D0–46D4 Alder Lake-N and Twin Lake currently require PCI revision 0 for their implemented backends. GPU detection is handled automatically using the PCI device ID, without requiring manual CPU model selection. Features WhateverXe currently provides several graphics-related capabilities, including: Metal and OpenGL hardware acceleration Hardware-accelerated graphics rendering HDMI and DisplayPort output on supported configurations Dual external displays at 1920×1080 @ 60 Hz Hardware HEVC encoding and decoding Hardware H.264 encoding and decoding tested on Tiger Lake Display sleep and wake functionality Automatic GPU identification and backend selection Connector configuration using firmware VBT information when supported Integration with OpenCore and Lilu These capabilities have been tested on selected Tiger Lake and Alder Lake-N configurations. Some features, including three simultaneous displays, full system sleep, higher display resolutions, and additional connector configurations, still require further testing. How Does It Work? WhateverXe works as a Lilu plugin that applies runtime adaptations to Apple's Intel graphics drivers. Instead of relying solely on device ID spoofing, the project implements dedicated compatibility logic for supported Intel Xe-LP architectures. It also works alongside a modified OpenCore Legacy Patcher (OCLP) implementation, which provides the necessary Xe graphics root patches. The combination allows selected Intel Xe-LP GPUs to initialize and use Apple's graphics acceleration stack under supported macOS configurations. Requirements The following components are required: Lilu.kext – Provides the runtime patching infrastructure. WhateverXe.kext – Implements Intel Xe-LP graphics compatibility. Modified OpenCore Legacy Patcher – Installs the required graphics root patches. AMFIPass Mod – Required for the modified root-patched graphics environment. WhateverXe must be loaded after Lilu through OpenCore. Important: WhateverGreen and WhateverXe must not be enabled simultaneously, including on systems with multiple GPUs. Basic Configuration The following OpenCore boot arguments are required: -allow3d -disablegfxfirmware Tiger Lake systems without an internal display additionally require: -wex-nopanel The latter argument is not required for the current Alder Lake-N / Twin Lake backend. For graphics memory allocation, setting DVMT Pre-Allocated to 96 MB in BIOS/UEFI is recommended when available. Systems with a fixed 60 MB DVMT allocation require the alternative configuration documented in the project's README. Please refer to the official documentation for the complete installation procedure, device properties, and additional configuration options. Future Development The project roadmap includes: Compatibility with additional macOS releases, from Monterey through Tahoe Support for additional Intel Alder Lake and Raptor Lake variants USB-C display output Internal laptop displays Further graphics compatibility improvements These are planned features and should not be considered implemented or guaranteed at this stage. Xe-LPG, Xe2, and newer graphics architectures are not currently planned. Download & Source Code WhateverXe – Official GitHub Repository https://github.com/b00t0x/WhateverXe Latest Releases https://github.com/b00t0x/WhateverXe/releases Modified OpenCore Legacy Patcher https://github.com/b00t0x/OpenCore-Legacy-Patcher OCLP Releases https://github.com/b00t0x/OpenCore-Legacy-Patcher/releases GPU Device Selection Documentation https://github.com/b00t0x/WhateverXe/blob/main/docs/device-selection.md Both RELEASE and DEBUG builds are provided. The RELEASE build is intended for normal use, while DEBUG builds are intended for troubleshooting. The complete source code is publicly available on GitHub. Credits & Acknowledgments WhateverXe builds upon the work of several developers and open-source projects that have made macOS graphics patching and Hackintosh development possible. WhateverXe Development b00t0x – WhateverXe project development, implementation, maintenance, and the modified OpenCore Legacy Patcher integration. Original Projects & Developers vit9696 – Original WhateverGreen copyright holder and key developer of the underlying graphics patching ecosystem. Acidanthera Team & Contributors – WhateverGreen, Lilu, and the underlying technologies that make runtime macOS graphics patching possible. Dortania / OpenCore Legacy Patcher Contributors – Original OpenCore Legacy Patcher development and the foundation for the modified implementation used by this project. OpenCore and Hackintosh Community – Research, documentation, testing, and contributions to macOS compatibility development. Related Projects WhateverGreen: https://github.com/acidanthera/WhateverGreen Lilu: https://github.com/acidanthera/Lilu OpenCore Legacy Patcher: https://github.com/dortania/OpenCore-Legacy-Patcher WhateverXe retains the original WhateverGreen copyright notices and is distributed under the BSD-3-Clause license. Full licensing information is available in the official repository. Final Notes WhateverXe is an ongoing effort to expand macOS graphics compatibility beyond Apple's officially supported Intel GPU generations. Although hardware acceleration and multiple graphics features are already functional on selected configurations, the project remains experimental. Community testing and feedback are welcome! If you have a Tiger Lake, Alder Lake-N, or Twin Lake system, feel free to share your hardware specifications, PCI device IDs, display connections, macOS build, and testing results. Bug reports and technical feedback can help identify compatibility issues and improve the project for other users. Please make sure to read the documentation carefully and back up your system before applying graphics root patches. Project: https://github.com/b00t0x/WhateverXe Thanks to everyone who continues contributing to the Hackintosh community!

Can't install catalina on my device

Fri, 09 Oct 2026 09:21:13 +0000

the error I'm getting is: OCB: LoadImage failed - Unsupported CPU:I5-4210u iGPU:Intel HD 4400 Network adapter:Intel ac 7265

Pulse Monitor does not read RAM

Wed, 07 Oct 2026 08:51:58 +0000

Hallo, Though I play with hackintosh for quite some time now (I am 45 yo, I started with Clover and El Capitan on my HP Elitebook 8540p with 2nd Gen intel cpu), I am still a newbie. I only follow guides and read a lot to understand. I am member of this wonderful site since 2018. My current hackintosh testbench PC is already a Frankenstein with Asus Maximus IX Apex Z270 with modded BIOS, running now Core i9-9900KF, G.Skill TridentZ kit of 32GB DDR4 @3600 and Sapphire Radeon RX 580 NITRO+ 8GB GDDR5 11265-21-20G. And the cherry on top is the original 256GB Apple SSD in a SATA adapter. I got bunch of these SSDs back in time when I was working in an Apple refurbishment warehouse. It was scrapped as dead but most of them are 100% with only couple hundreds of starts and few GB read/written. They are just slow as they are basically 2011-2015 SATA SSDs with Apple proprietary connector. I am now running OpenCore as boot tool and Sequoia macOS and all works pretty well. Now I just came accross Pulse Monitor so I ran it and it shows the HW pretty well except for the RAM. It shows how much each process or program takes but the all over RAM gauge shows zero. The screenshot of the PM not showing RAM is zipped and attached. But in "About This Mac" the RAM amount and frequency is correct. I think its because of SMC is not reading the CPU RAM controller correctly. What do you think about it? Regards, George Archive.zip

UVCProbeFix for macOS Tahoe - Fix Broken USB Webcam Video and Black Screen on Hackintosh

Tue, 06 Oct 2026 12:16:03 +0000

UVCProbeFix is a macOS kernel extension designed to restore certain USB UVC webcams that are correctly detected by macOS but fail to produce a usable video stream, resulting in a black screen or a failed camera start. DONATIONS Link HERE or HERE Confirmed Working – Lenovo IdeaPad S145 Ice Lake The fix has been verified through UVC runtime traces, not only by visual testing. Before UVCProbeFix was active, the webcam returned a malformed PROBE response: Frame: 4 Frame Size: 184549376 Payload: 16842753 Result: Start Stream Failed With UVCProbeFix loaded, the same camera negotiated: Frame: 1 Frame Size: 614400 Payload: 3072 Interval: 333333 The captured PROBE response and COMMIT were byte-for-byte identical, after which macOS selected Stream Alternate Setting 6, opened the USB streaming pipe and reported start streaming for client. The successful trace contains zero Start Stream Failed events. Hardware: Lenovo IdeaPad S145 Ice Lake Resolution: 640×480 YUV422 @ 30 FPS Result: ✅ UVC negotiation recovered and video streaming successfully started. The problem Some UVC webcams enumerate normally and expose valid video formats, but their firmware returns malformed values during the UVC PROBE/COMMIT negotiation performed by macOS. In the hardware case that led to this project, macOS selected a valid video mode, but the webcam returned an invalid GET_CUR(VS_PROBE_CONTROL) response containing incorrect frame-size and payload values. macOS then committed those invalid parameters and attempted to start the stream, which resulted in a black image / stream startup failure. The camera itself was functional. The failure happened during UVC negotiation. What UVCProbeFix does UVCProbeFix intercepts the affected negotiation path and applies a known-good recovery before macOS commits the broken configuration. For the currently verified hardware case, the original negotiation behaves approximately like this: macOS selects: Frame 4 640x480 30 FPS Camera returns: Frame size: 184549376 Payload: 16842753 macOS COMMIT: same invalid values Result: stream fails / black screen UVCProbeFix detects this broken negotiation and performs a controlled re-negotiation using the working equivalent UVC frame. The recovered negotiation becomes: Frame: 1 Resolution: 640x480 Interval: 333333 Frame size: 614400 Payload: 3072 macOS then commits the corrected values and the camera starts producing real image data normally. Important distinction UVCProbeFix is not a generic webcam driver and it does not replace Apple's UVC stack. It works alongside the existing macOS camera stack and targets a specific class of problems where: the webcam is detected; the UVC interface enumerates correctly; supported video formats are visible; PROBE/COMMIT negotiation occurs; but the camera firmware returns malformed negotiation values or a broken equivalent-frame path. Problems involving USB power, physical connection, proprietary camera protocols, missing device enumeration, sensor failure or unsupported codecs are outside this recovery path. Current release strategy The production Release currently preserves the physically verified recovery implementation for the known working case. The experimental branch also contains a descriptor-driven generic recovery engine intended to eventually support other webcams exhibiting the same class of UVC negotiation failure. The generic design does not rely on a specific VID/PID or fixed camera model. Instead, it is being developed to: parse the webcam's own UVC descriptors; validate the returned PROBE data; identify impossible frame-size or payload values; discover equivalent frames dynamically; perform at most one safe re-negotiation; leave healthy webcams completely untouched; fail closed when a correction cannot be proven. This generic path remains isolated from the stable Release until it passes sufficient real-hardware validation. Compatibility Initial target: macOS Tahoe Darwin 25.6 Intel x86_64 Lilu-based kernel extension environment The current recovery has been physically validated on the hardware that originally exhibited the black-screen UVC negotiation issue. Other webcams may exhibit a similar symptom for completely different reasons, so additional hardware must be analyzed before compatibility can be claimed. Future webcam support For additional webcams, the goal is not to create an endless VID/PID compatibility list. The intended workflow is: Passive UVC trace ↓ Analyze PROBE / COMMIT negotiation ↓ Parse the webcam's descriptors ↓ Identify the failure class ↓ Prove a safe recovery ↓ Add regression fixtures ↓ Test in Generic Recovery mode ↓ Hardware validation This allows future fixes to be based on UVC behavior and descriptor evidence, rather than camera brand or model. Safety The project follows a conservative recovery policy: healthy negotiations are passed through unchanged; no arbitrary frame or payload values are guessed; unsupported or ambiguous cases remain untouched; internal recovery attempts are bounded; the stable legacy recovery remains isolated from experimental generic code. Status The original black-screen webcam case is working again under the stable recovery path. Development is now focused on safely generalizing the same concept so that other UVC webcams with equivalent negotiation failures can potentially be recovered without camera-specific hardcoding. Download Kext HERE Download DUMP HERE Credits Special thanks to the developers and projects that made this work possible: Lilu by vit9696 / Acidanthera — kernel patching framework used by UVCProbeFix. MacKernelSDK by Acidanthera — kernel development headers and build support. Apple UVC / IOUSBHost stack — platform interfaces analyzed during development and debugging. Linux uvcvideo developers — valuable reference for UVC negotiation, descriptor parsing and recovery behavior. Olarila.com community — testing, feedback and hardware reports that help expand compatibility. UVCProbeFix development and research: DNMTechLabs / MaLd0n Contact: dnmtechlabs@gmail.com

macOS 26 Tahoe with alpha 15 b5eek

Mon, 05 Oct 2026 14:04:25 +0000

Hi everyone, I am trying to run macOS 26 Tahoe on my MSI Alpha 15 B5EEK laptop. Here are my detailed hardware specs: CPU: AMD Ryzen 5 5600H (iGPU Radeon Vega 7) dGPU: AMD Radeon RX 6600M 8GB RAM: 16GB DDR4 Storage: NVMe SSD Bootloader: OpenCore Since it's an AMD Ryzen laptop requiring NootedRed.kext for the iGPU, I'm stuck with Kernel Panic / Black screen during boot on Tahoe. Is there anyone who has successfully booted Tahoe on a similar Ryzen 5000 series laptop, or could help me build/patch a working EFI for this specific setup? Any guidance or help would be greatly appreciated. Thanks in advance!

Tahoe on Intel NUC NUC10i7FNH

Mon, 05 Oct 2026 10:23:31 +0000

Hello, I want to install macOS Tahoe on an Intel NUC NUC10i7FNH. I use the EFI folder for this NUC from Olarila. I have change the SMBIOS to iMac20,2 because there is the "Forbiden" logo at boot. In the BIOS, I have disabled Secure Boot, TPM, Intel Virtualisation and Intel VT-d. I can boot from the usb key but it is stuck on this line Set Power State : Already change state to new power state, done Thank you if you can help me 🙂

How to extract audio codec dump using Clover Bootloader or Linux

Sun, 04 Oct 2026 13:08:15 +0000

This guide explains how to create an audio codec dump using Clover Bootloader or Linux. -Linux Use Ubuntu or other distro then run this tool HERE Download Ubuntu HERE -Clover You must already have the prepared EFI folder installed or copied to your EFI partition. Download EFI HERE Steps Boot your computer using the prepared EFI folder with Clover Bootloader. When you reach the Clover boot screen, do not boot macOS. Press the F8 key on your keyboard. You don't need boot to macOS! Clover will create a codec/audio dump automatically. Open your EFI partition. Go to the Clover folder: EFI/CLOVER/ Inside the Clover folder, look for a folder named: misc Compress the entire misc folder into a .zip file. Send me the zipped misc folder. Important Notes The F8 key must be pressed at the Clover boot screen, before booting macOS. Do not rename or modify the files created inside the misc folder. Send me the complete misc folder exactly as Clover/Linux created it. If the misc folder was not created, reboot and try pressing F8 again at the Clover boot screen.

Lenovo Thinkcentre M700 Hackintosh EFI

Sun, 04 Oct 2026 08:28:50 +0000

I did a lot of repeated tests and tries a lot of versions, and I was getting 4mb of my 128mb iGPU can anyone help me

Bugs after 26.7 and Safari 27 - Safari (Youtube) freezes and apfsd in an endless loop.

Sat, 03 Oct 2026 00:40:15 +0000

Em Português: Olá pessoal. Após atualizar o hack para o Tahoe 26.7 e persistindo no 26.7.1 e o Safari 27, meu sistema começou a ter 2 problemas sérios. São eles: 1º - Tenho vários HDs de muitos TB e após o upgrade o processo apfsd fica consumindo 400% de CPU o tempo inteiro por dias e sem parar. Cheguei a deixar 7 dias seguidos e não termina. Não adianta colocar os discos em Privacidade no Spotlight parar não indexar, pois não influência. A única forma de parar é desmontando os discos e remontando (finalizar o processo apfsd não adianta pois é chamado novamente). Parece que consome 100% de CPU para cada disco, deixei com os 2 menores discos conectados apenas e ficou consumindo 200% por dias também e não termina. Imagino que seja algo em relação a IA, que não vou usar mas não consigo com que o processo pare. Testei sem os plugins e sem nenhum software de terceiros rodando no sistema e o problema ainda continua. Video: https://drive.google.com/file/d/1YwZyEl-4MNksBkyd-m2qNiFuQDXrPPk9/view?usp=sharing 2º - O Youtube no Safari fica travando toda vez que passa uma aba e volta, rola qualquer página para baixo/cima, e muda de mesa. Há outras coisas também que fazem travar mas estas são as principais. Muito chato, atrapalha demais. Claro que posso usar um outro navegador mas o Safari é o meu principal e seria bom achar uma solução. Video: https://drive.google.com/file/d/1_vdEX8cFf1M3gaPSuIZ3OwLGCTyHU3v8/view?usp=sharing Se alguém souber resolver me dê uma luz por gentileza pois deve ter outras pessoas com os mesmos problemas. Core i5-11400 - MSI B560 Tomahawk Wifi - 32GB RAM 3600MHZ XPG - OpenCore 1.0.8 - macOS Tahoe 26.7.1 Em Inglês: Hello everyone, After updating my hack to Tahoe 26.7—which persists on 26.7.1—and Safari 27, my system started having two serious issues. They are: 1st - I have several multi-TB HDDs, and after the upgrade, the `apfsd` process keeps consuming 400% CPU continuously for days without stopping. I even left it running for 7 straight days and it didn't finish. Adding the drives to Spotlight's Privacy tab to prevent indexing doesn't help at all. The only way to stop it is by unmounting and remounting the drives (killing the `apfsd` process doesn't work since it immediately spawns again). It seems to consume 100% CPU per drive; I tested leaving only my 2 smallest drives connected, and it stayed at 200% CPU for days as well without finishing. I suspect it might be related to AI features, which I don't intend to use, but I can't find a way to stop the process. I tested this without any plugins or third-party software running in the background, and the issue persists. Video: https://drive.google.com/file/d/1YwZyEl-4MNksBkyd-m2qNiFuQDXrPPk9/view?usp=sharing 2nd - YouTube on Safari freezes/stutters every time I switch tabs and come back, scroll any page up or down, or switch spaces/desktops. There are other triggers as well, but these are the main ones. It's very annoying and disruptive. Of course I could use another browser, but Safari is my primary one and I'd really like to find a solution. Video: https://drive.google.com/file/d/1_vdEX8cFf1M3gaPSuIZ3OwLGCTyHU3v8/view?usp=sharing If anyone knows how to fix these issues, please point me in the right direction, as I'm sure others might be experiencing the same problems. Core i5-11400 - MSI B560 Tomahawk Wifi - 32GB RAM 3600MHZ XPG - OpenCore 1.0.8 - macOS Tahoe 26.7.1

gigabyte gaming A16 CVH i7 13620 (RAPTOR Lake 13th gen) efi + install help?

Fri, 02 Oct 2026 01:27:08 +0000

hey all, i'm attempting sonoma 14.8.9 on my raptor lake gigabyte gaming a16 cvh, it's a raptor lake i7 13620 10 cores 16 threads, intel iris xe graphics (igpu), nvidia rtx 5060 8gb dgpu, intel ax 211 wifi + bluetooth, 16gb ddr5 ram, 1tb skhynix 611 nvme ssd with windows 11 pro, WD Blue 1tb nvme for macOS sonoma, realtek rtl8111 ethernet, realtek alc245 audio. I tried the olarila notebook 12th, 13th and 14th gen efi + olarila 14.8.9 raw file. it halted on during boot with or without nootedgreen enabled, i tried making a usb map in windows still no good, can anyone help me troubleshot and fix this please? i dont currently have a log or etc. to send.. i was up ALL night last night trying if not longer to make this work, and my iphone 16 pro has a tough time taking pics of the screen to show output so that isn't an ideal thing to show verbose logs if honest. but i'm willing to share the EFI i used though.

Broadcom Bluetooth on real MacBookPro9,2

Fri, 02 Oct 2026 00:16:25 +0000

Hello, I have a problem with My 13" MacBookPro9,2 from Mid 2012. This is one of the last ones with DVD drive, it has a Core i7 2,9 GHz and Intel HD4000 graphics. And Broadcom Bluetooth. I'm using Mavericks 10.9.5. I know it's old, but it is fast and enough for me. Because it only has two USB ports which are close together I wanted to connect the mouse using Bluetooth. Bluetooth is shown active in the menu bar, but BT devices can be directly next to the MacBook and they aren't detected. The Bluetooth Preferences Pane also doesn't help. The MacBook shows this in System Profiler: USB name: Broadcom BRCM20702 Hub Device: 0x4500 (17664) Manufacturer: 0x0a5c (02652) Bluetooth USB Host controller: Device: 0x821d (33309) Vendor: 0x05ac (01452) There was an issue with this MacBook. There was no audio. So I tried VoodooHDA. I got several audio outputs, but it didn't had internal speakers. I read that several people had problems with no sound after updating to 10.9.3, so I tried different kexts back to 10.9.0. No success. Then I tried AppleHDA.kext from 10.8.5 and this worked. I've checked Contents/Resources, and in the 10.8 kext are 77 layout.zlib files, in Mavericks just 14. In Yosemite are 126. Why removed Apple so many of the zlib files in Mavericks that it made audio not working? After the 10.8.5 audio kext was working well I tried the Bluetooth kexts from 10.8.5. It didn't worked worse, but it also didn't work better. So I wanted to switch over to BrcmBluetoothInjectorLegacy.kext, which is working on my OSx86 system with a Dell-branded card, DW1550 27020A3. First I had to deactivate the Apple drivers. So I replaced in the bluetooth kexts the ID 33309 to 93309 so the card couldn't be found. This worked, there was no Bluetooth anymore. Then I added the neccessary device entry in BrcmPatchRAM.kext. This also worked fine, everything is loaded as it should. But which firmware should I use? There are 54 entries with BCM20702A1 and one BCM20702B0. I have my OSx86 drivers always in /S/L/E because I'm using different versions of macOS. I've checked the descriptions of BrcmPatchRAM. I have the Bluetooth drivers from the BootCamp package. But actually I have no Windows system to install them on. My Windows experiences are also so gone... Windows 7 was the last I used. I inspected the files I had, checked them in a hex editor, extracted other files from the exe files... One .exe contained another installer exe which contained this data. Shown in TextEdit it looks like this in the attachment. Reminds me at some ascii graphics. Greets, naquaada. WhatIsThis.zip

How to change a intel ax201ngw to DW1820a card in Sequoia ?

Thu, 01 Oct 2026 16:14:15 +0000

How to change a intel ax201ngw to DW1820a card in Sequoia 15.8 ? Can support all continuity, airdrop, etc?

Wi-Fi problem

Wed, 30 Sep 2026 04:58:43 +0000

my Wi-Fi driver is qualcomm fast connect 6900. Is there any way to make it work other than usb ?

Hackintosh Mouse Cursor Freezing After Installing RX 580

Mon, 28 Sep 2026 07:51:48 +0000

Hi, I have a problem with my mouse cursor on Hackintosh. The cursor randomly freezes/stutters, even when I disconnect other USB devices. The problem started after I installed a Sapphire RX 580 8GB. Before changing the GPU, the mouse worked normally. PC Specs: Intel Core i3 10th Gen Sapphire RX 580 8GB GDDR5 16GB DDR4 SK hynix PC711 NVMe FSP Vita 550W macOS Hackintosh / OpenCore USBMap I already tried different USB ports, disconnecting other devices, rebuilding USBMap, and agdpmod=vit9696, but the problem remains. Could the RX 580 be causing this issue? And should XhciUnsupported.kext be disabled when using USBMap?

ZeroRPMBuilder for macOS - AMD Zero RPM / Fan 35c PowerPlay Patch Generator

Sun, 27 Sep 2026 20:01:25 +0000

ZeroRPMBuilder is a native macOS utility created to generate AMD GPU fan-control patches for Clover/OpenCore through DeviceProperties. The application can extract or import an AMD PowerPlay table, validate its structure, apply a controlled Zero RPM modification, and generate a ready-to-use PP_PhmSoftPowerPlayTable without flashing or modifying the GPU VBIOS. It was designed for users who want a cleaner and safer way to disable Zero RPM or configure a predictable fan start/stop temperature on supported AMD GPUs. Extracting the VBIOS with Clover (if you don't use Windows) You can dump your GPU VBIOS directly from the boot menu: Boot with Clover HERE Press F6. Clover will save the GPU ROM/VBIOS to the EFI partition, usually inside the Clover misc folder. Copy the generated file and load it into ZeroRPMBuilder. This is useful when you want ZeroRPMBuilder to work with the exact VBIOS from your GPU. Main Features Native macOS application AMD GPU and PowerPlay table detection Automatic GFX0 detection Bundled gfxutil 1.84b Automatic OpenCore PCI Device Path detection VBIOS / PowerPlay table extraction SPPT import support Strict PowerPlay structure validation Automatic Clover/OpenCoreDeviceProperties generation Automatic device-id spoofing when required Automatic no-gfx-spoof for supported Lexa cases Offline patch generation for GPUs not installed in the current Mac Original SPPT backup Patched binary and hexadecimal exports OpenCore config.plist generation OpenCore DeviceProperties snippet generation Detailed export report No VBIOS flashing required Fan Presets ZeroRPM OFF — Fan Always On This mode disables the GPU's Zero RPM behavior. Only the Zero RPM enable field is changed. The original: fan start temperature fan stop temperature fan curve RPM limits thermal targets are preserved. This is intended for users who prefer the fans to remain available instead of entering the GPU's factory Zero RPM state. FAN 35°C — Stop 30°C This preset keeps Zero RPM enabled but changes the fan activation temperatures to: Fan Stop Temperature: 30°C Fan Start Temperature: 35°C Zero RPM: Enabled The GPU can stop its fans below the configured threshold and restart them at approximately 35°C. Only the required PowerPlay fan-control fields are modified. Supported AMD Architectures ZeroRPMBuilder currently supports validated PowerPlay layouts for: Polaris Polaris 10 Polaris 11 Polaris 12 / Lexa Polaris 20 Polaris 21 Polaris 23 Examples include: RX 460 RX 470 RX 480 RX 550 RX 560 RX 570 RX 580 RX 590 Radeon Pro WX series Vega 10 Including: RX Vega 56 RX Vega 64 Vega Frontier Edition Radeon Pro WX 8100 / 8200 / 9100 Vega 20 Including: Radeon VII Radeon Pro VII Navi 10 / Navi 14 Including: RX 5300 RX 5500 RX 5600 RX 5700 Radeon Pro W5500 Radeon Pro W5700 Navi 21 / Navi 22 / Navi 23 Including members of the: RX 6600 family RX 6700 family RX 6800 family RX 6900 family Radeon Pro W6600 / W6800 families The application currently recognizes 56 AMD PCI Device IDs across the supported PowerPlay families. Automatic DeviceProperties Detection ZeroRPMBuilder includes gfxutil 1.84b directly inside the application bundle. No Homebrew installation is required. The application first attempts: gfxutil -f GFX0 to obtain the real EFI PCI device path. Example: PciRoot(0x2)/Pci(0x0,0x0)/Pci(0x0,0x0) If gfxutil cannot resolve the device, ZeroRPMBuilder uses its internal IORegistry detector. If no usable GPU path can be determined, generation is still allowed through a generic fallback: PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0) The user can also manually enter the required DeviceProperties path. Offline / Cross-GPU Patch Generation ZeroRPMBuilder does not require the target GPU to be installed in the Mac used to generate the patch. For example: Mac currently running: RX 6600 XT / Navi 23 Loaded VBIOS: RX 580 / Polaris The application will still generate the Polaris patch. The local GPU is used only when appropriate for DeviceProperties path detection. The loaded VBIOS/SPPT remains authoritative for the actual patch. This makes ZeroRPMBuilder useful for: preparing an EFI for another computer; preparing a patch before installing the GPU; building patches remotely; working with VBIOS dumps from another machine. A different GPU installed in the current Mac will no longer block generation. Automatic Device-ID Spoofing For selected GPUs that require a compatible PCI Device ID, ZeroRPMBuilder can automatically generate: device-id inside OpenCore DeviceProperties. Current automatic mappings include selected: Navi 21 Navi 23 Polaris Lexa Examples: 73EF → 73FF 73AF → 73BF 73A5 → 73BF and supported Lexa mappings such as: 699F → 67FF 6987 → 67FF 6995 → 67E3 6985 → 67E3 6981 → 67E3 The property is stored in the correct little-endian OpenCore format. Lexa no-gfx-spoof For the supported Lexa Device IDs that require the additional WhateverGreen behavior, ZeroRPMBuilder also generates: no-gfx-spoof AQAAAA== which corresponds to: 01 00 00 00 This is currently applied to: 699F 6987 6995 6985 6981 It is not added globally to every spoofed GPU. Generated OpenCore Properties A generated entry can look like: DeviceProperties └── Add └── PciRoot(...)/Pci(...)/Pci(...) ├── PP_PhmSoftPowerPlayTable ├── device-id └── no-gfx-spoof device-id and no-gfx-spoof are only added when applicable. The actual PowerPlay patch is stored as raw binary data in: PP_PhmSoftPowerPlayTable Safe PowerPlay Validation ZeroRPMBuilder does not blindly patch arbitrary offsets. Before modifying a table, it validates the expected PowerPlay structure for the detected architecture. Depending on the GPU family, validation can include: PowerPlay format revision content revision table revision declared structure size fan table revision fan table offset SMU PowerPlay version thermal controller type OverDrive table layout required field bounds If the loaded table does not match a supported structure, the application refuses to patch it. Unknown layouts are not guessed. What Does ZeroRPMBuilder Modify? Depending on the architecture, only the equivalent fields for: FanZeroRpmEnable FanStopTemp FanStartTemp are modified. ZeroRPMBuilder does not intentionally change: GPU core clocks memory clocks GPU voltage memory voltage power limits TDC limits fan curves minimum RPM maximum RPM fan target temperature OverDrive capability tables FeaturesToRun Original Table Preservation Before exporting the modified PowerPlay table, ZeroRPMBuilder preserves the original source. Generated packages can contain: Original SPPT Patched SPPT HEX export OpenCore config.plist OpenCore DeviceProperties snippet Generation report This makes it easier to compare or restore the original configuration. VBIOS Safety ZeroRPMBuilder does not flash your GPU. It does not write anything to the physical VBIOS. The modified PowerPlay table is applied through OpenCore: DeviceProperties → PP_PhmSoftPowerPlayTable Removing the property restores normal behavior without reflashing the graphics card. Built-in gfxutil ZeroRPMBuilder includes the official Acidanthera gfxutil 1.84b RELEASE universal binary: x86_64 arm64 It is used exclusively for PCI / EFI Device Path discovery. The application therefore does not require the user to install gfxutil separately. Credit for gfxutil belongs to its respective upstream authors and contributors. Testing The current release has been validated through automated regression, structural, parser and stress testing. The current development test set includes: Core regression tests: 405/405 Structural validation: 143/143 Swift parser checks: 13/13 AddressSanitizer tests: 405/405 ThreadSanitizer tests: 405/405 Stress testing: PASS Stress testing includes repeated: PowerPlay modifications; VBIOS extraction; PCI path parsing; OpenCore plist generation; ZIP generation; import/export operations. The patch matrix also covers both fan modes across all currently recognized GPU IDs. Important Notes PowerPlay tables can vary between: GPU generations; board partners; VBIOS revisions; OEM cards; workstation variants. ZeroRPMBuilder therefore validates the structure before writing anything. If a VBIOS contains an unknown PowerPlay layout, please provide the original ROM/SPPT so support can be investigated safely. Always keep a working EFI backup before modifying your OpenCore configuration. Feedback and Hardware Samples Compatibility reports are welcome. If a GPU is detected but its PowerPlay table is rejected, please include: exact GPU model; PCI Device ID; VBIOS ROM if possible; original SPPT; macOS version; ZeroRPMBuilder log. Additional real-world VBIOS samples help improve validation without resorting to unsafe generic offsets. Credits ZeroRPMBuilder ©DNMTechLabs dnmtechlabs@gmail.com Additional credit to the Acidanthera project and the authors/contributors of gfxutil, Lilu, WhateverGreen and the broader Hackintosh development community. Download ZeroRPMBuilder HERE AMD PowerPlay / Zero RPM patch generator for macOS and OpenCore. No VBIOS flashing. No permanent GPU modification.

macOS Catalina VM with Windows Subsystem for Linux

Sun, 27 Sep 2026 11:21:03 +0000

Hello, I would like to know if it is possible to have macOS Catalina in Virtualbox or VMWare and Windows Subsystem for Linux (WSL) at the same time on the same Windows 11 pc with an Intel CPU. Thank you for your ansers 🙂

macOS is very slow on Asus PN60

Sat, 26 Sep 2026 16:04:34 +0000

Hello, I am installing macOS Tahoe on an Asus PN60 Here are the specifications : - Intel Core i3 8130U - Intel UHD Graphics 620 - DDR4 So-dimm 16 Go - SSD Sata Kingston A480 I have successfully installed macOS with the corresponding OpenCore folder. But at first boot, when it ask for personnal informations, the computer is very slow. Thank you per advance for your help 🙂

macOS with Intel N CPU

Fri, 25 Sep 2026 09:57:59 +0000

Hello, I would like to know if it is possible to install macOS on a pc with an Intel "N" cpu (Intel N100, N150, N305, N355...) Thank you for your answer 🙂

[WIP / Open Source] 12th-gen Intel Core i7-12650H iGPU driver on macOS Tahoe

Thu, 24 Sep 2026 03:16:40 +0000

Hi everyone, I have published the source for an experimental macOS Tahoe graphics driver and compatibility project targeting the Intel Core i7-12650H integrated UHD Graphics (Alder Lake-P, PCI 8086:46A3, revision 0c). Tested system: macOS Tahoe 26.6.2 (25G83), x86_64, with a 1920 × 1080 internal display running at 144 Hz. Demonstrated on this machine Internal display and backlight integration, plus a working Metal device used by WindowServer and tested applications. Metal support covers a basic validated subset. Desktop dragging measured approximately 119–127 actual new frames per second in one 144 Hz test scenario. This is not a guaranteed frame rate across workloads. A separate H.264 hardware decode test produced 30/30 frames with pixel-for-pixel agreement against a software reference. Decoding during video export does not establish H.264 hardware encoding. Current limits This is hardware-specific source, not a universal Intel iGPU driver or one-click installer. Standalone Stencil8, dynamic shader libraries, some newer Metal features, and long-term desktop GPU stability remain incomplete. HEVC encoding has a first-frame pixel-corruption issue. Support for other iGPU IDs, Tahoe builds, external displays, and sleep/wake has not been established. The repository contains original source code, build and same-hardware deployment instructions, capability evidence, and known limitations. It does not distribute Apple binaries, modified Apple drivers, or an EFI. The original code is GPL-3.0-only, with third-party Intel licenses preserved. Source and documentation: IntelIGPU-Tahoe on GitHub Verified capabilities and limitations: CAPABILITIES.md I am sharing the implementation for technical discussion.

VoodooI2C + VoodooI2CSynaptics - Sleep/Wake Fix for Synaptics

Thu, 24 Sep 2026 02:29:05 +0000

We are releasing a version of VoodooI2C with VoodooI2CSynaptics that includes a specific fix for Sleep/Wake issues affecting Synaptics trackpads. On some laptops, the Synaptics trackpad works normally after boot, but stops responding after macOS enters Sleep and wakes up again. The device may still remain present in the system, but the RMI communication/interrupt state is not properly restored after wake. This version introduces specific power-management handling inside VoodooI2CSynaptics. What does the fix do? During Sleep, the driver tracks the device power-state transition. After Wake, VoodooI2CSynaptics performs the required recovery procedure to restore proper trackpad operation, including: restoring RMI ATTN mode; restoring the F01 interrupt mask; dedicated handling through IOKit power states; preventing unnecessary reinitialization when the trackpad is already awake; dedicated Sleep/Wake diagnostic messages. When the recovery succeeds, the driver reports: Woke up from Sleep! RMI ATTN mode restored. There are also specific diagnostic messages if any part of the recovery procedure fails: Wake recovery failed to restore RMI ATTN mode Wake recovery failed to restore F01 interrupt mask If the device is already active, the driver reports: Trackpad already awake! Not reinitializing. Version The provided package contains: VoodooI2C 2.9.1 VoodooI2CSynaptics 1.0 Current architecture: x86_64 The current build is configured for the Synaptics device identified as: SYNA2B61 Please verify the ACPI device name of your trackpad before using this version. Purpose of this fix The main goal is to address the common behavior where: Boot → Trackpad works → Sleep → Wake → Trackpad stops working With this fix, the RMI state required for trackpad interrupts is restored during Wake, allowing the device to remain operational without requiring a macOS reboot. Check the trackpad device name in IORegistryExplorer (IOReg) for each laptop, then replace the existing device name in the VoodooI2CSynaptics.kext Info.plist with the correct one for your hardware. Download: VoodooI2CSynaptics.zip Credits to the original VoodooI2C project and its developers. This version keeps the original project base while adding the Synaptics Sleep/Wake handling described above.

Sound Blaster z audio card

Wed, 23 Sep 2026 13:21:35 +0000

Hi I have a sound blaster z internal audio card ,i'd like to try to get it working in sequoia and tahoe ,is this even possible? Thanks

DSDT.aml could not be disassembled!

Wed, 23 Sep 2026 01:20:18 +0000

Hey everyone, good evening. I'm trying to build an AMD Hackintosh (or a "Ryzentosh," as the insiders call it) and I'm running into trouble creating the EFI for macOS Ventura. When I run SSDTTime and select option "P. Dump the current system's ACPI tables," I get the following error: "DSDT.aml could not be disassembled!" I know my motherboard isn't exactly top-tier (Mancer Mcr a520m dx), and from what I can see, there seems to be a duplicate file. I tried booting without the ACPI files anyway, but OpenCore got stuck at a specific point (I'm not sure if the two issues are related). I'd be really grateful for any help you could provide. :D Specs: Processor: Ryzen 5 4500 Graphics card: RX 580 RAM: 16GB Motherboard: Mancer Mcr a520m dx DSDT and Opencore.zip

[Help] Intel UHD 630 stuck at 7MB VRAM on MSI PRO H410M (macOS Monterey) - OpenCore

Tue, 22 Sep 2026 15:09:58 +0000

Spesifikasi Sistem: - Motherboard: MSI PRO H410M - CPU / iGPU: Intel Comet Lake Intel UHD Graphics 630 - RAM: 4GB DDR4 - Sistem Operasi: macOS Monterey - Bootloader: OpenCore Deskripsi Masalah: Saya mengalami masalah dalam mengaktifkan akselerasi perangkat keras pada iGPU Intel UHD Graphics 630 saya. macOS Monterey berjalan dengan baik, tetapi VRAM tetap macet di 7MB. Berikut adalah konfigurasi yang telah dilakukan: 1. Pengaturan BIOS: DVMT Pre-Allocation diatur ke 64MB / 128MB, Total Memory diatur ke MAX. 2. DeviceProperties (PciRoot(0x0)/Pci(0x2,0x0)): - AAPL,ig-platform-id = 00009B3E - ID perangkat = 3E920000 - framebuffer-patch-enable = 01000000 - framebuffer-stolenmem = 00003001 - framebuffer-fbmem = 00009000 - framebuffer-unifiedmem = 00000080 - framebuffer-con0-enable = 01000000 - framebuffer-con0-type = 00080000 - Nilai framebuffer-con0-busid yang diuji: 01, 02, dan 04. 3. Kext yang digunakan: Lilu dan ApapunGreen keduanya diaktifkan di config.plist. 4. Reset NVRAM dilakukan setelah setiap perubahan konfigurasi. Meskipun pengaturan tersebut sudah benar, akselerasi grafis tidak berfungsi. Apakah ada konektor/pemetaan BusID khusus atau patch tambahan yang diperlukan untuk menampilkan tampilan pada motherboard MSI PRO H410M ini? Adakah solusi lain? Bantuan akan sangat dihargai!