MaLd0n

Go to Monterey and use our efi folder haswell mobile

HDAUniversal-Release.zip Use alcid=170

Save codec dump with clover o linux

🇧🇷 Olarila — Links de Pagamento e Doações Apoie o Olarila! Aqui você encontra os links para pagamentos e doações. Sua contribuição é fundamental para manter o projeto ativo, apoiar seu desenvolvimento e garantir melhorias contínuas. Obrigado pelo apoio! 🇺🇸 Olarila — Payment & Donation Links Support Olarila! Here you can find our payment and donation links. Your contribution helps keep the project running, supports its development, and makes continuous improvements possible. Thank you for your support! Paypal HERE - Ko-Fi HERE - Revolut HERE - Remitly HERE - Mercado Livre HERE - Binance ID 182969561 - Pix olarilaforum@gmail.com

U need to use .command from first post

U need reproduce these problems and save log after. This audio codec is not common. Linux have extra quirks, etc too.

Report it in github project

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!

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!

The Realtek ALC888B/ALC887 has only two physical analog ADCs. In this layout, the Rear Microphone uses one ADC, while the Front Microphone and Rear Line-In share the other. Because of this, Front Mic and Line-In cannot capture audio simultaneously. The main issue was the ADC handoff: when switching between them, macOS could try to start the new input before the previous one had fully released the shared ADC. The latest fix keeps all three inputs as separate devices while safely waiting for the shared ADC to be released before activating the next source. Use this and save new logs HDAUniversal-Release.zip

HDAUniversal-Release.ziptest 03

Wrong bootloader config

Test 02 HDAUniversal-Release.zipalcid=170

Reporting Issues If you find a problem with HDAUniversal, please report it with proper logs. Before posting, run the included log collector: Collect-HDAUniversal.command Download HERE

HDAUniversal-Release.zip Use alcid=170 and check if work

U need extract codec dump on linux or clover

HDAUniversal-Release.zip Test this

Yes. Have support for Tahoe. Enjoy!

SystemPulse-Release.zip This app is for Ventura+. Check if this version work, I changed support to Bigsur+.

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

U just need to use imac20 smbios

Dont use internal graphics, use RX6600m

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.

no support for this

Yes. Have support.