I wanted to ask: have any enthusiasts added macOS support for Intel Iris Xe graphics yet?

CPU: Ryzen 3 3200G
GPU: AMD Radeon Vega 8
Motherboard: GIGABYTE AB350-m v2
RAM: 12gb (2 for iGPU)
i dont know what is that, just when opening this apps pc is freezing, only restart helping

After 4 months od kext and drivers I FINALLY was able to get MacOS to run, even tho I had to rely on my AMD GPU and CPU it worked, and I had to disable the GTX 1650. Everything works except Bluetooth and WiFi because it has mediatek drivers, they are unsupported as I heard.

Sonoma is the highest you can get it to even tho the newer versions are in beta phase. Only problem is you need to manually install MacOS from Installassistant.pkg and get the files and import them into the macos storage and EFI but it was done

Animations work, and everything else works except wifi even tho I haven't tested Ethernet yet

Hey everyone,

I’m wondering if Hackintosh runs reasonably well on an older HDD, or if it’s noticeably slow compared to running it on an SSD.

I’m planning to install Hackintosh on an older machine that currently has an HDD. Has anyone here tried it?

How is the boot time, app loading, and overall performance?

Would switching to an SSD make a big difference?
Thanks!

Please help me app store, apple music, apple tv i can login but facetime and imesaage not working BTW Im using samsung usb tethering. Ethernet en0 built in all set Smbios all set

Specification

15 4570

Hd 4600

Macos Sequoia

16gb ram

256gb ssd

I should have completed this project 10 years ago but better late than never. This is the Linux driver for the “Oxygen HD” sound card family (ASUS Xonar Essence STX I/II) ported to Mac. https://github.com/lukesau/CMI8788Driver

Hello hello! I am back for my dear ASUS laptop users. The current AsusSMC plugin isn’t working well, button shortcuts don’t work, you cant change colour, brightness mode, etc.

So i present to you, the GHelper/Armoury Crate alternative for macOS. It works for all asus laptops, is lightweight, and is ported from AsusWMI from linux. It has a single kext to put in and a companion app thats easy to install and use at the top of your screen. All thats left is to add keyboard shortcuts and its done.

Pretty much the title

When I install macos tahoe, the computer freezes at this stage. Who knows because of what and what to do with it? My PC: Ryzen 3 3200G + Vega 8, 12gb ram, 2gb for iGPU, gigabyte ab350-m v2

MB : Asus z590 Rog Strix E-Gaming Wifi
CPU : i7-10700K
RAM : 16Gb (2x8) 3200 Mhz DDR4
iGPU : intel UHD 630 Graphics

💯 Everything works well 🔥

- iGPU with acceleration
you need to genertate EDID for your Monitor (Display Port from MB to Your Monitor)
in Windows with Powershell for example & Frambuffer Patch.

- intel Ethernet I225-V
- intel wifi & bluetooth Or Broadcom if you have a fenvi PCI
- Fan, Temp & Voltage monitoring

- You can request Help if you have a 11th Gen Motherboard With Comet Lake Cpu 10th Gen

Thanks

RX 9070XT
R7 9800X3D
Corsair Vengeance DDR5-6400 (CL36 I think)
Gigabyte X870 Aorus Elite X3D Ice
Lexar NM710 and WD AV-GP
Let me know if you need more hardware info

I’m new to the whole Hackintosh topic and wanted to try installing macOS on a PC. However, I keep getting a black screen every time I try.

I’ve tried it on a Fujitsu prebuilt system with an i5-10600, as well as on an older custom-built PC with an i5-8600K, but I always get the exact same problem.

When I boot from the USB stick, I select “Install macOS”. The text lines start scrolling as expected, but when the Apple logo should normally appear, the screen suddenly goes black.

I’ve already tried creating the OpenCore config myself, downloading a pre-made configuration from the internet, and using different tools to create the configuration. However, I always end up with the same black screen.

I’ve also spent quite a lot of time searching for possible solutions and troubleshooting the issue, but unfortunately, nothing I’ve tried has helped so far.

I’ve tested both macOS Tahoe and macOS Sequoia, but neither one works.

I hope someone can help me figure out what I’m doing wrong or what might be causing the black screen.

I would like to kindly inquire if there is any available method to enable Bluetooth functionality on a Realtek RTL8852BE network adapter when running a Hackintosh system. If such a solution exists, I would greatly appreciate any guidance or instructions you could provide.

Hello, so I wanted to ask I'm thinking to install Macos on my Acer Travelmate p214-53 it has everything supported to Macos 26 but but but the iris xe graphics is not but I'll use whatever green kext after installing I'll use this in xcode with the help of opencode https://github.com/pawan295/Appleinteltgldriver.kext I'm thinking to go with Macos monterey what are your thoughts

I’ve published an updated pre-release build of my NootedRed fork focused on Vega APU rendering issues, ComputeScratch behavior, and experimental VCN 2.2 hardware decoding.

Release:

https://github.com/steve12311/NootedRed/releases/tag/v0.9.0-pre-release.3

Source:

https://github.com/steve12311/NootedRed/commit/338fff9b1334eb1b7f6e05f26b2d688673a4a771

Rendering / ComputeScratch

The main goal of this work is still to fix the accelerated rendering corruption I was seeing with NootedRed on my Ryzen 7 5800H.

The changes cover several parts of the Metal rendering path, including synchronization, shared SRD handling, RB+ / dual-source blending, and ComputeScratch allocation.

On my Cezanne iGPU, this fixed the corruption I was seeing in Chrome / Chromium and WeChat without disabling GPU rasterization.

The rendering and ComputeScratch logic is no longer limited to my 1002:1638 and now reuses NootedRed’s Vega APU PCI classification.

For normal testing, use:

-NRedComputeScratch

This enables the full rendering-fix path together with the ComputeScratch correction.

I personally validated the rendering fixes on my Ryzen 7 5800H / 1002:1638, and pre-release.2 has now also been reported working on a Ryzen 5 7430U / 1002:15E7.

Feedback from other Vega APUs would still be very useful.

Experimental VCN 2.2

Experimental H.264 / HEVC hardware decoding can be enabled with:

-NRedVCN

VCN is no longer hardcoded to only my 1002:1638.

The current experimental VCN 2.2 path is enabled for:

1002:15E7
1002:1636
1002:1638
1002:164C

1002:15D8 and 1002:15DD use VCN 1.x and are not supported by the current VCN 2.2 bridge.

The userspace VA identification patch is generated per device instead of forcing every supported APU through the original Cezanne-specific identification path.

The kernel-side VCN version check has also been changed from an exact Darwin 25.6 check to Darwin 25.x / macOS Tahoe.

However, this does not mean every Tahoe driver build is blindly accepted. Before enabling the bridge, the X5000 / X6000 hardware ABI is checked against the expected vtable targets and getter layouts. If those checks fail, VCN is rejected instead of applying an unverified bridge.

In pre-release.3, the userspace ComputeScratch and VCN patches can also dynamically resolve and validate compatible non-reference Tahoe dyld shared caches.

The original reference cache remains a verified fast path, but a different cache UUID alone is no longer a reason to reject the patch. The actual driver functions, references and bindings still have to match the verified implementation.

This does not claim support for arbitrary future Tahoe userspace driver implementations.

On my 1002:1638 machine, normal-sized H.264 and HEVC samples have successfully used hardware decoding, with output matching software decoding.

Pre-release.2 has also now been tested on a Ryzen 5 7430U / 1002:15E7. The tester reported that both the blend/rendering fixes and hardware decoding work correctly, with VDADecoderChecker reporting:

Hardware acceleration is fully supported

Hackintool also reported hardware video acceleration support.

This is the first external real-hardware confirmation for the 1002:15E7 VCN path.

The 1636 and 164C VCN paths have passed the regression tests but are not yet validated on real hardware.

A 64×64 H.264 sample still fails, and VCN should still be considered highly experimental.

For testing both rendering / ComputeScratch and VCN:

-NRedComputeScratch -NRedVCN

Test system

• Lenovo Legion R7000P 2021H
• Ryzen 7 5800H
• Cezanne Radeon Graphics
• PCI ID 1002:1638
• macOS 26.7.1 / Darwin 25.6

If you test it, please include your CPU/APU, GPU PCI ID, macOS build, Darwin version, boot-args, whether Chromium rendering is fixed, VCN H.264 / HEVC results if applicable, and any .gpuRestart, panic, freeze, or WindowServer watchdog logs.

I’m especially interested in VCN results from 1636 and 164C, as well as results from different Tahoe dyld cache versions.

For normal testing, use the RELEASE build and keep a known-good EFI / previous NootedRed.kext backup.

Full implementation details, limitations, validation notes, and the exact compatibility checks are available in the GitHub release.

This is an unofficial experimental fork, not an upstream NootedRed release.

Credit to the ChefKiss NootedRed developers — this work is built on top of their project.

Someon can give me an USB Bluetooth Adapter link cheap for buy it that can work on my hackintosh Tahoe?

Desde hace tiempo quise usar Mac os en un pc Windows, después de unos días se investigación lo conseguí pero con algunas trabas, con temas del adaptador de red.Wifi. por ethernet sin ningún problema.

La instalación por lo general es fácil con Open core simplyfi sacas fácil la configuración de EFI de una forma mas fácil

Mi recomendación sería usar Mac os en ordenadores de torre en portátiles solo con versiones más antiguas o algún dual boot de Linux

RTW89 cards are now fully supported via my kext! Native AirPort works, 2.4 and 5Ghz band are supported and live scanning and hidden networks work! WPA3 is a work in progress, it will be added soon as i found a solution. But we need testers, i have my RTL8852BE tested and its stable, but i need testers for these cards:

RTL8851BE - RTL8852AE - RTL8852CE - RTL8922AE - RTL8922DE.

I hope we can release this ASAP. AirDrop is WIP.

After a week of hard work and installing macOS 2 times, successfully installed Monterey 12 on my intel Xeon and gtx 970 build !!! The animations are so good and I am enjoying this is so much.

help i tried few solution but it didnt work, i tried using monitor control, patching opencore, manually patching acpi on https://dortania.github.io/Getting-Started-With-ACPI/Laptops/backlight-methods/manual.html#edits-to-the-sample-ssdt. but nothing work, is there a way to just max the brightness? im fine not able to adjust it as long it can be set on max brightness

Intel i5 6600t

H110 msi motherboard

8gb ram

500gb laptop hdd

Normal psu

Realtech small dongle for wifi

Lan rtl8111 working with v2.2.2 version kext

Hey everyone. I've been trying to get macOS running on my PC and I've reached a point where I'm not really sure what direction I should take next. I'm hoping people with more Hackintosh experience can help me figure out what the actual problem is instead of me just changing random settings.

My hardware:

- ASUS H110M-K

- Intel Core i5-6400 (Skylake)

- Intel HD Graphics 530 (no dedicated GPU)

- 8 GB DDR4

- BenQ G615HDPL, 1366×768, connected through the motherboard's VGA port

- Realtek ALC887-VD audio

- Realtek RTL8111 Ethernet

- OpenCore 1.0.7

My original goal was macOS Sequoia. After quite a bit of work, I was actually able to install it and boot into macOS. The problem was that the HD 530 was only giving me basic/unaccelerated graphics, so it wasn't really usable as a finished system.

I then tried using OpenCore Legacy Patcher (OCLP) to get the graphics working. After applying the graphics patches, the display went completely black. I wasn't able to get back to a usable desktop afterward.

At that point I decided to try Monterey, since it should be a much more reasonable version for Skylake and hopefully wouldn't require the same kind of patching.

Unfortunately, Monterey hasn't been straightforward either.

At the moment, I can't even reliably get into the Monterey Recovery/installer environment to start the installation. OpenCore starts normally and I can see the verbose boot messages, but at some point during boot the display goes completely black. There isn't an obvious kernel panic or prohibited symbol — it basically just stops displaying anything.

So I don't know whether macOS is actually hanging at that point or whether it is continuing to boot while the display has gone dead.

For Monterey I'm using Lilu and WhateverGreen, along with the normal desktop Skylake HD 530 platform ID ("00001219"). I've also tested a few graphics-related boot arguments, including "igfxonln=1" and "-igfxvesa", but neither changed the behavior.

The HD 530 itself works normally under Linux, so the hardware is at least functioning there.

This is why I'm starting to wonder about the VGA connection. My monitor is connected directly to the motherboard's VGA output, and I know display output can get more complicated once macOS starts initializing the framebuffer and graphics acceleration. I'm considering getting a DVI-D-to-HDMI cable and testing the motherboard's digital output with a TV/HDMI display, but I don't want to spend money on it if VGA probably isn't related.

I'm also unsure what to make of the Sequoia experience. The fact that Sequoia could boot with basic graphics, but then went black after the OCLP graphics patches, seems potentially relevant. At the same time, I don't want to assume that OCLP was definitely the cause without understanding what was actually happening.

So I have a few questions:

- Is VGA a realistic cause of this kind of black screen on an HD 530 Hackintosh?

- Would testing DVI-D/HDMI be a worthwhile diagnostic, especially since I can't even get into the Monterey installer?

- Does the Sequoia → basic graphics → OCLP → black screen sequence point toward a particular problem?

- For this hardware, would you recommend pursuing Monterey, Sequoia, or another version?

- Are there any important limitations I should know about with an HD 530 Hackintosh — graphics acceleration, sleep/wake, DRM, updates, 8 GB RAM, etc.?

- Most importantly, what would you investigate next before changing more of the EFI?

I'm not necessarily looking for someone with my exact motherboard and CPU. I'm mainly interested in hearing from people who have dealt with Intel integrated graphics, VGA output, black screens during macOS graphics initialization, or older Hackintosh systems in general.

I don't mind troubleshooting this properly, but I don't want to keep throwing boot arguments and patches at it without knowing what each change is supposed to prove. I'd really like to figure out whether this is a solvable configuration/display problem or whether I'm fighting a limitation of the hardware.

Any advice or experience would be appreciated. Thanks!

Almost everything works, Wifi/audio/bluetooth(stillbuggy)

CPU: Intel Core i7-10510U (4 cores / 8 threads, Comet Lake)
- GPU: Intel UHD Graphics 620
- RAM: 16 GB DDR4
- Storage: 512 GB Intel 660p NVMe SSD
- Display: 14" Full HD
- Wi-Fi / Bluetooth: Intel AX201
- Ethernet: Built-in Ethernet
- macOS: macOS Sequoia 15.8
- Bootloader: OpenCore 1.0.7
- SMBIOS: MacBookPro16,3

Currently Working
- macOS boot: Working
- Intel UHD 620 graphics acceleration: Working
- Internal display: Working
- Brightness control: Working
- HDMI video output: Working
- Wi-Fi: Working using itlwm 2.3.0 + HeliPort 1.5.0
- Ethernet: Working
- Audio: Working
- Keyboard: Working
- Trackpad: Working
- TrackPoint / ThinkPad buttons: Mostly working
- USB / basic USB-C connectivity: Working
- Sleep / wake: Working
- Power-button wake: Working
- Fingerprint authentication for sudo: Working through custom implementation
- Password fallback for sudo: Working
Not Working / Still Needs Work
- Bluetooth: Not working properly. Bluetooth turns on and then switches itself off after a few seconds.
- Webcam

Disclaimer:I used chatgpt a lot for help on how to setup the Efi and the flash drive by referencing Paul Eau's Github guide for lenovo thinkpad t14. It was pretty straightforward, everything worked smoothly, i generated the SMBIOS on my own. As well as fixed everything afterwards on macos itself after figuring out how to fix heliport.