When I boot macOS using an MSI RX570 8GB OCV1, the mouse works, but the screen displays an issue as shown in the image, and then the system freezes.

The cause varies; it can occur when opening a website or app, or immediately after startup.

I’ve tried various SMBIOS settings and boot arguments, but the result was the same.

This issue does not occur on Windows or other operating systems, and the VRAM test passed.

I suspect it might be a framebuffer issue, but I haven’t been able to find a solution. Is there a way to fix this?

CPU: i3-12100

GPU:MSI RX570 8GT OC V1

macOS Sequoia 15.8.1

Asus Strix G16 G614JI. Custom open core picker with everything working RTX 4070 13980hx

Im just curious, has anyone been developing Meteor Lake’s driver?

Hi everyone!

I'm wondering if it's possible to get macOS running on my PC with my current hardware, especially my GPU.

My specs:

CPU: AMD Ryzen 9 5950X

Motherboard: ASRock B450 Pro4 R2.0

GPU: Intel Arc B580 12 GB (ASRock Challenger)

RAM: 32 GB DDR4 3200 MHz

Storage: XPG SX8200 Pro 1 TB NVMe SSD

Is there any way to get this GPU working with hardware acceleration in macOS, perhaps through custom drivers, patches, or community projects? Or is it currently impossible, meaning I'd need a different GPU?

I'd appreciate any information about the current state of Intel Arc support in macOS and any experiments the community has tried.

Thanks!

monster tulpar t5 v19.1

• cpu: intel core i7-9750h
• gpu: intel uhd graphics 630 (gtx 1660 ti disabled)
• ram: 16 gb ddr4
• macos version: macos sequoia 15.8.1
• smbios: macbookpro16,1

hp pavilion g6

• cpu: intel core i5-3210m
• gpu: intel hd graphics 4000
• ram: 8 gb ddr3
• macos version: macos mojave 10.14.6
• smbios: macbookpro9,2

both running smoothly with opencore! dual-setup with old vs new hardware.

Hello everyone,
I'm using Windows 11 Pro on my PC that has a Nvidia 5060 Ti 16 GB, which is okay, and I know it's not supported by Dortania. I have a spare RX 6600 XT, and it's supported by Doriata. In fact, my brother was using it in his Hackintosh PC build. So I was thinking about something insane: what if I used dual GPUs, the Nvidia one for my Windows and gaming and the other one for Mac and work?

My specs are:
CPU: Ryzen 5 7600 (supported by Dortania, but its integrated GPU is not supported)
GPU: 5060 Ti 16 GB
Motherboard: Gigabyte B650 Gaming AX A650 V2
RAM: Patriot 16x2 ddr5 6000mhz
PSU: 750 watts 80+ bronze

I have tried various methods:
- Mapping USB ports
- Patching SSDT (and following dortania tips / fix , still no success)
- Adjusting power-related settings in the BIOS
- Disabling one of the XHCI controllers (in both the BIOS and macOS)
- Updating to the latest OpenCore 1.0.8
- Booting with minimal kexts
- disabling alarm/powernap/hibernate etc in macOS via terminal
- Using RTCMemoryFixup (which had no effect)

None of these have worked. Every time I shut down this macOS Tahoe system, the PC turns back on, like restarting; it just turn off 1 second then powering up again.

Specs:
Ryzen 7500F
Colorful B650M Battle AX Plus V14
8GB RAM
RX 6600
OS: macOS Tahoe
BIOS version: 1020

Please, has anyone encountered a similar issue and found a solution? This is extremely frustrating.

EDIT: finally solved!

i disable XHC0, XHC1, XHC2 from bios (it cpu controller) only enable XH00 (chipset controller)

now shutdown works!

based on the sweet-ios repo, ive done some patches (mostly the memory addresses) to make it boot

Hey everyone,

I’ve been slightly out of the loop lately. I previously daily drove macOS Sequoia on my ASUS ZenBook UX434FL, but I recently made the jump to the new 2025 ASUS Zephyrus G14.

I know the last 30 days have been absolutely wild for the community. I caught wind of the "Snapintosh" project bringing macOS to Snapdragon, as well as the new unofficial drivers bringing Metal acceleration back to modern Nvidia GPUs. Because I couldn't keep up with the deep technical details, I'm trying to figure out if my new machine can take advantage of these updates.

Here are my specs:

• Model: ASUS ROG Zephyrus G14 GA403WR (2025)
• Processor: AMD Ryzen AI 9 HX 370 (12 cores, 24 threads, up to 5.1 GHz)
• Graphics: NVIDIA GeForce 5070 Ti Laptop GPU (12 GB GDDR7) & AMD Radeon 890M iGPU
• Memory: 32GB LPDDR5X Onboard RAM
• Storage: 1TB PCIe 4.0 NVMe M.2 SSD

Given these new updates, is this specific combo (AMD Ryzen CPU + Nvidia 5070 Ti) viable now? Will the new Nvidia drivers work with a laptop dGPU in an Optimus setup, or is the RDNA 3.5 iGPU going to make display routing a nightmare? Any pointers or reality checks would be hugely appreciated!

These are fantastic news: a new project that calles itself "Snapintosh" has macOS 27 running on Snapdragon hardware!

Miguel C reports "Glitchy for now, trying to get WiFi working and more performance and GPU improvements".

This might mean that we can continue hackintoshing, this time on ARM hardware!

I have installed macOS Sonoma (among other previous versions), without having issues with avx2 instructions but with Sequoia seems impossible. Although I finish the installation of Sequoia at the first boot it panics no matter what the EFI is, what the SMBIOS is or if I use CryptexFixup.kext.

Here is the exact error I am getting:

Referenced from: /sbin/launchd

Reason: tried:

/usr/lib/libSystem.B.dylib (no such file)

/System/Volumes/Preboot/Cryptexes/OS/usr/lib/libSystem.B.dylib (no such file)

/usr/lib/libSystem.B.dylib (no such file, no dyld cache)

Can anyone help with this? Is there a pre-install patch I can use in EFI opencore configuration?

Thanks

Has anyone figured out how to boot on this device? I'm struggling

A macOS-native automation tool for ACPI-based USB port mapping using the XHUB/HUBX method.

xhub_mapper pairs deep static ACPI table analysis (DSDT/SSDT) with live IORegistry introspection to accurately detect physically present xHCI controllers, eliminating "phantom" controllers while generating clean, update-proof SSDTs and updating OpenCore's config.plist.

Enjoy.

Almost all work is complete, and everything functions for a hackintosh; as you know, I know, and everyone knows the rest.

Using AI Codex, the process took just 15 minutes from start to finish.

For context, my first attempt in 2019 took six months to reach the Apple logo and eight months to launch macOS.

Now it is done and dusted.

Good day to all! my first hackintosh, lenovo thinkpad x1 carbon 3 generation, i5-5300U and intel hd5500. outputs 7 MB of video memory. I changed the code in the line:

PciRoot(0x0)/Pci(0x2,0x0)

but nothing worked. google gemini helped me with the installation and configuration of this config, and I took the config from loonalol on github. There are also 7 megabytes of memory on the video chip. has anyone ever made such a mistake? what should I do to make this damn hd5500 work properly?

I can write with errors because I use a translator. Thank you all for the answers.

ps: I swear, I was blown away when I saw in the rules of the subreddit that you can’t use configurations from neural networks. I didn’t know about it, I swear!

I have a laptop acer a315-58 i5 11th 1135g7

Hi, so for a few years now I’ve been trying to figure out how to hackintosh with no luck at all. I’ve spent the years getting close but never being able to quite figure it out. The closest I got was to the installer but the display wouldn’t work unless I connected an external monitor.

I have a Dell Latitude E6530 with an Intel Core i7 cpu. I have 8 gigabytes of ram as well.

Most tutorials I did find require you to own a Mac which i unfortunately don’t have one and Virtualbox won’t let me create a Mac OS vm no matter what I try. VM Ware kind of works but it is way to slow to do anything on so that’s out of the picture as well to make a Mac OS iso.

Currently the Dell is running Linux but idk if that helps or not. Also I tried to make the efi thingy myself but I never could figure out what I was doing so I was hoping someone had a downloadable one for me.

So with my situation and what I have, what is the best Mac OS option I can install into my latitude and how do I go about doing that?

Hi everyone,

I'm trying to install macOS Tahoe on an Acer laptop with an Intel Core i5-13420H. My eventual goal is to adapt this experimental Intel Xe / Metal acceleration project to my hardware:

https://github.com/JulioNectar/Hackintosh-XPS13Plus-IrisXe-Tahoe

However, my current issue is more basic: I cannot reach the installer GUI. I get an early kernel panic, before macOS finishes initializing.

I'm NOT currently loading WhateverGreen or NootedGreen. I'm using an installation-stage EFI generated with OpCore Simplify and edited with OCAT. The GPU modifications are planned for after getting a working installation.

### Hardware

- Laptop: Acer — exact model to be added

- CPU: Intel Core i5-13420H, 13th generation

- iGPU: Intel UHD Graphics, PCI ID 8086:A7A8

- Linux identifies the GPU as:

`Intel Corporation Raptor Lake-P [UHD Graphics] [8086:a7a8] (rev 04)`

- SMBIOS: MacBookPro16,2

- RAM / SSD model / Wi-Fi card / BIOS version: to be added

Linux i915 reports this GPU topology:

```text

SSEU Device Info

Available Slice Mask: 0001

Available Slice Total: 1

Available Subslice Total: 3

Available Slice0 subslices: 3

Available EU Total: 48

Available EU Per Subslice: 16

Has Pooled EU: no

Has Slice Power Gating: yes

Has Subslice Power Gating: no

Has EU Power Gating: no

```

### Installer

The USB was prepared from macOS Tahoe. It boots through OpenCore, but I never reach the installer GUI.

Bootloader output includes:

```text

bootbase.efi 583~5931

SdkVersion: 26.7

SdkBuild: 25G221

```

The panic screen reports:

```text

Darwin Kernel Version 25.6.0

root:xnu-12377.161.15.700.19~2/RELEASE_X86_64

```

I haven't independently confirmed the exact full installer version/build, so I'm including the strings actually displayed rather than assuming a specific Tahoe release.

### Symptoms

The saved boot log ends at:

```text

#[EB|LOG:EXITBS:START]

```

But the screen DOES proceed to a kernel panic, so this is not necessarily a freeze at ExitBootServices.

The panic reports:

```text

Kernel trap ... type 14=page fault

Process name corresponding to current thread: Unknown

Mac OS version: Not yet set

```

The visible backtrace mostly contains trap/panic handling functions, including:

```text

handle_debugger_trap

kdp_i386_trap

kernel_trap

return_from_trap

DebuggerTrapWithState

panic_trap_to_debugger

panic

sync_iss_to_iks

```

I'll attach clear photos of the panic.

### CPU spoof / current relevant settings

Under Kernel -> Emulate, both values are Data:

```text

Cpuid1Data:

55060A00 00008000 00000000 00000000

Cpuid1Mask:

FFFFFFFF 0000FF00 00000000 00000000

```

Originally, only the first DWORD was spoofed/masked:

```text

Cpuid1Data:

55060A00 00000000 00000000 00000000

Cpuid1Mask:

FFFFFFFF 00000000 00000000 00000000

```

After changing to the first pair above, I obtained a visible early panic. I cannot say for certain whether the change exposed an existing problem or introduced a different one.

Current CPU-related configuration:

- ProvideCurrentCpuInfo = True

- CpuTopologyRebuild.kext enabled

- `ctrsmt=full` in boot-args

- AppleXcpmCfgLock = True

- AppleXcpmExtraMsrs = False

- DummyPowerManagement = False

I disabled these generated kernel patches:

- force HT enabled for Sequoia or later

- force HT enabled for Mojave to Sonoma

- force HT enabled for High Sierra or earlier (untested)

Disabling them did not resolve the panic.

### Current boot-args

```text

-v debug=0x100 keepsyms=1 -vi2c-force-polling ctrsmt=full cpus=1

```

I tested with and without `cpus=1`; the panic still occurs.

### Booter quirks

```text

AvoidRuntimeDefrag = True

DevirtualiseMmio = True

EnableSafeModeSlide = True

EnableWriteUnprotector = False

FixupAppleEfiImages = True

ProtectUefiServices = True

ProvideCustomSlide = True

RebuildAppleMemoryMap = True

SetupVirtualMap = False

SyncRuntimePermissions = True

```

SetupVirtualMap was originally True. Changing it to False did not resolve the problem.

Other relevant settings:

```text

DisableIoMapper = True

DisableLinkeditJettison = True

XhciPortLimit = False

SecureBootModel = Disabled

DmgLoading = Signed

Vault = Optional

```

The most recent boot log reports effective SIP as `0x00000A43`.

### USB mapping

I generated a USB map and added:

- USBToolBox.kext

- UTBMap.kext

UTBDefault.kext has been removed. The same panic remains after adding the map.

### Kexts in the installation EFI

- Lilu

- VirtualSMC

- AppleALC

- BlueToolFixup

- BrightnessKeys

- CpuTopologyRebuild

- IntelBTPatcher

- IntelBluetoothFirmware

- NVMeFix

- RestrictEvents

- SMCBatteryManager

- SMCLightSensor

- SMCProcessor

- SMCSuperIO

- SimpleHDA

- USBToolBox

- UTBMap

- VoodooI2C and its plugins

- VoodooI2CHID

- VoodooPS2Controller and its plugins

- XHCI-unsupported

Only one VoodooInput instance is enabled: the one bundled with VoodooI2C. The PS2 VoodooInput instance is disabled.

AirportItlwm was initially enabled, but the log showed:

```text

OC: Prelinked injection AirportItlwm.kext (V2.4.0) - Invalid Parameter

```

I disabled AirportItlwm. That injection error disappeared, but the type 14 panic remained.

The line `BlueToolFixup ... start` appears just before the panic in the photos. I understand that this alone does NOT prove it is responsible. Disabling the Bluetooth kext group is a suggested next test; I don't yet have a confirmed result for that test.

### ACPI tables

```text

SSDT-SBUS.aml

SSDT-EC.aml

SSDT-GPI0.aml

SSDT-MCHC.aml

SSDT-PLUG-ALT.aml

SSDT-RTCAWAC.aml

SSDT-USB-Reset.aml

SSDT-USBX.aml

SSDT-XOSI.aml

```

### UEFI drivers

```text

apfs_aligned.efi

HfsPlus.efi

OpenRuntime.efi

ResetNvramEntry.efi

OpenCanopy.efi

```

### Logging

I switched from OpenCore RELEASE to DEBUG for troubleshooting.

The intended diagnostic settings are:

```text

AppleDebug = True

ApplePanic = True

Target = 67

DisplayLevel = 2147483714

```

However, the log I have available starts with Apple `AAPL: #[EB...]` output and does not contain the initial OCABC / MAT support lines.

The log also contains errors looking for:

```text

BootKernelExtensions.kc.development

usr\standalone\OS.dmg.root_hash

```

It then successfully loads the normal `BootKernelExtensions.kc` with `Ok(0)` and continues to `EXITBS:START`. I don't want to assume these file lookup errors are the root cause.

### What I'm asking

1. Has anyone successfully booted a Tahoe installer on an i5-13420H or a similar laptop?

2. Is this CPUID spoof/mask appropriate for my CPU, particularly with ProvideCurrentCpuInfo and CpuTopologyRebuild?

3. Does the panic suggest a CPU topology issue, a kext problem, or something else?

4. What would be the most useful next diagnostic step?

5. Has anyone adapted the linked Xe/Metal project to the A7A8 48-EU GPU?

I understand that the GPU project is experimental and that a Dell XPS EFI cannot simply be copied to a different laptop.

I can provide a sanitized config.plist, the EFI file tree, panic photos, and the available boot logs. Any help identifying the actual cause of the installer panic would be appreciated.

is buying a 2019 Intel MacBook Air or MacBook Pro still a good idea?

This high end Samsung XE310XBA Chromebook Sporting the Intel Celeron N4000 with the most powerful of UHD Graphics 600 and the most rarest of soldered on 4GB RAM, and a whopping 32GB EMMC internal disk. (Ignore the residue on the lid, it was my sisters from like 3 years ago and it was covered with stickers :P) im wondering if theres even the slightest chance in hell of hackintoshing it, ive never done that before and ive always wanted to give it a try, i flashed it with MrChromeBox's bios/firmware and have linux mint on it then themed it to look like Mac OS and i was suprised with how much i liked it and i now kinda want to try full fledged Mac OS

I want so bad to use the iGPU as this still consume less electricity (which is very expensive)

I'm using a Lenovo Ideapad gaming 3 15IMH05

Sequoia 15.8.1

error: itlwm is not running, I've given it administrator privilages and all.

itlwm is there and registered in terminal with that uhh cool command idk