Skip to content

Instantly share code, notes, and snippets.

@cdleon
Last active February 15, 2024 10:24
Show Gist options
  • Star 89 You must be signed in to star a gist
  • Fork 20 You must be signed in to fork a gist
  • Save cdleon/ae1542279598fe80f527400cc354a956 to your computer and use it in GitHub Desktop.
Save cdleon/ae1542279598fe80f527400cc354a956 to your computer and use it in GitHub Desktop.
Macbook Pro 2011 GPU Defect fix macOS Sierra and High Sierra

Works for macOS Sierra and High Sierra

Taken from 2011 Macbook Pro Graphics Card FIX 100% WORKING!!!

EDIT This method works! But there is an improved version for better thermal management and brightness keys functionality. See improved version -> https://gist.github.com/cdleon/d1eff7246a25193304284ecec40445b0

Enter Recovery Mode (text mode)

if you are on high sierra 10.13.6+ you might need to use Command + r instead

Boot up holding down Command + r + s

Disable SIP

SIP locks System folder so cannot move kexts to another folder. SIP (csrutil) only enabled or disabled on Recovery Mode.

csrutil disable

Restart the system

reboot

Enter Single User mode

boot up holding down the CMD and S keys

Check a disk

use /sbin/fsck if you get fsck command not found

fsck -fy

Mount a root filesystem with read/write permissions

use /sbin/mount if you get mount command not found

mount -uw /

Make a directory to store the AMD drivers in case you'll need them in future

sudo mkdir /AMD_Kexts/

Move the AMD drivers

sudo mv /System/Library/Extensions/AMD*.* /AMD_Kexts/

Remove the AMD drivers cache

sudo rm -rf /System/Library/Caches/com.apple.kext.caches/

Just in case OS X will be dumb and will not recreate this directory, we create it again

sudo mkdir /System/Library/Caches/com.apple.kext.caches/

Update the timestamps so that new driver caches - without AMD drivers - will be rebuilt

sudo touch /System/Library/Extensions/

Unmount a partition to guarantee that your changes are flushed to it. Use /sbin/umount if you get umount command not found. It might say resource busy, ignore that and proceed to next step)

sudo umount /

Reboot

sudo reboot

Before enabling SIP again, try the normal boot without pressing any key. The Mac OS will rebuild the kernel cache and restart. See if the system starts normally. If it does, still keep going through the remaining steps.

You might encounter that you are still using discrete GPU but computer works (if you are using gfx it might say can't change to discrete while external display is connected), keep going until last step and this will be resolved

Enable SIP again by restarting the system and entering Recovery Mode (text mode)

if you are on high sierra 10.13.6+ you might need to use Command + r instead

Command + r + s

Enable SIP

csrutil enable

Restart the system

reboot

Open Terminal (Finder -> Applications -> Utilities -> Terminal (copy and paste):

sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00

Restart the system

sudo shutdown -r now

You might need to do this again after macOS system updates Brightness keys might not work use app like brightness-slider to handle that

@jeepeegit
Copy link

jeepeegit commented Feb 14, 2024

You can use OpenCore Legacy Patcher also for installing the latest yosemite for MB 2011 and it will solve the GDI problem by switching it off. so there is no fraught. And it would behoove Apple if they provided a program so that turning that GID on and off would be simple for everyone.

@MoldyOldie
Copy link

You can use OpenCore Legacy Patcher also for installing the latest yosemite for MB 2011 and it will solve the GDI problem by switching it off. so there is no fraught. And it would behoove Apple if they provided a program so that turning that GID on and off would be simple for everyone.

Unless you have tested this procedure on the specific hardware in question, and are willing to support any issues encountered by the user, you shouldn’t be suggesting it. Especially to someone who isn’t technically advanced, as is the case here. You yourself stated it didn’t run well when you did this. For basic users who aren’t highly technical, it’s irresponsible to suggest going beyond the OS version Apple officially supports, or recommending other technical modifications to the OS. I doubt the user here has any idea what “OpenCore Legacy Patcher” is, let alone what to do with it.

I could try doing this myself, but I also have almost 50 years of experience working with computer systems. I know what precautions to take, so that if anything goes wrong, I have the knowledge and tools to get my system working again.

(I won’t be making any further replies to subsequent comments regarding this. So, if your ego insists you “put me in my place”, feel free to do so. I couldn’t care less.)

@jeepeegit
Copy link

Everyone is allowed to have an opinion of course :-) I think Ale337-s can decide for himself what he wants and can do.
Have a nice day.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment