iATKOS | United Kingdom: How to Troubleshoot Using dGPU instead of iGPU (macOS sees both of them) [HELP] on macOS

How to Troubleshoot Using dGPU instead of iGPU (macOS sees both of them) [HELP] on macOS

Graphics and media-app issues are normally caused by missing Metal acceleration, an unsupported GPU path, or a fragile patch combination. macOS needs a supported graphics stack; WhateverGreen, NootRX or NootedRed can help only when the underlying GPU path is viable.

Quick Checks

Backup current state: Save a copy of your working EFI and run a full system backup before changing settings.
Identify hardware components: Note down your exact CPU, GPU, Wi-Fi card, and motherboard/laptop model.
Ensure utility alignment: Keep OpenCore, OCLP, and ProperTree updated.

Fix Steps

Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
Verify GPU support first: Confirm the exact GPU model and whether that macOS version supports Metal acceleration for it.
Update graphics kexts: Refresh WhateverGreen, Lilu and any AMD-specific kexts together, not one at a time.
Check boot arguments: Remove old experimental GPU boot args, then add back only the ones required for your hardware.
Test acceleration: Open About This Mac, System Information and a Metal app before testing browsers, GarageBand or Pro Tools.
Reduce app variables: Disable browser hardware acceleration or test another app build if only Chromium, Electron or CEF apps fail.

Do Not Continue If

Do not continue if: you do not have a working EFI backup, a Time Machine backup, or another bootable macOS installer.
Stop and capture evidence: if the machine stops booting, take a photo of the last verbose line before changing more settings.

Verify It Worked

The GPU reports Metal support in System Information.
Window animations are smooth and not CPU-bound.
The affected app opens after a clean reboot.
No repeated GPU restart messages appear in Console.

Rollback

Boot with a known-good EFI snapshot.
Temporarily remove experimental graphics patches.
Return to the last macOS version where acceleration was stable.

Next Action

Test now: reboot twice, reproduce the original problem, and confirm whether the same symptom returns.
If it still fails: record the Mac model, macOS build, OpenCore or OCLP version, GPU, Wi-Fi/Bluetooth chipset, and the last visible error.
Read next: use the related searches below for the nearest OpenCore or OCLP fix before making another change.

Original Question: "Using dGPU instead of iGPU (macOS sees both of them) [HELP]"

Hello everyone,

I have a Sandy Bridge CPU with Nvidia GT550M as the GPU, I'm using macOS 12 Monterey.

I firstly disabled my dGPU by using the "-wegnoegpu" boot argument in my config.plist, then installed macOS using only the iGPU (Intel HD Graphics 30000).

After the installation, i installed OCLP and installed drivers for my iGPU while my dGPU is still de-activated. After that, i wanted to be able to use my dGPU and used Dortania's Post-Install guide to activate my dGPU and remove the "wegnoegpu" boot argument.

macOS (12) succesfully booted after that, and OCLP saw all the needed drivers for my dGPU and i installed them. The problem is, i can't use my dGPU even though my macOS installation sees it (my SMBIOS is for MacBookPro11,5, could this be the problem?). Also there's no option to use dGPU in battery section.

About This Mac (system still uses the iGPU)

System Information Page (iGPU)

System Information Page (dGPU)

Battery options page (no option for dGPU)

submitted by /u/Sarpmanon
[link] [comments]

[► Source]