MBP 1,1-10,2 Force 2011 MacBook Pro 8,2 with failed AMD GPU to ALWAYS use Intel integrated GPU (EFI variable fix)

[pckrullenbol]

Warning!
Look out for the latest security update 2018-002 10.13.6, it will install a fresh copy of AMDRadeonX3000.kext!
I screwed up things and had to recover from Timemachine backup...

 

[RTouris]

Warning!
Look out for the latest security update 2018-002 10.13.6, it will install a fresh copy of AMDRadeonX3000.kext!
I screwed up things and had to recover from Timemachine backup...

This is common practice with Security updates unfortunately. You'll have to keep a good copy aside and don't forget to bless the folder when you're done with the procedure, otherwise you may run into peculiarities.

 

[Miou]

Been skimming through this thread, and it's been a lot of help with the 2011 MBP I'm working with. The AMD GPU was so bad that I couldn't boot to anything. It would freeze up on power on half the time.

I used this method as a workaround. All is well except... On wake, the Macbook has no display. (I can hear audio feedback and what not.) I implemented the Handler fix on the page I linked, but it didn't resolve the issue.

I've tried a few methods here and haven't had much luck. These include moving/automating the kext from post #875 as well as the recent post that recommends changing the CFG_FB_LIMIT value to 3.

It might be worth mentioning that this MBP is running High Sierra. Anyone have any other recommendations? I've got other projects to work on and I can't keep wasting time on this one. Thanks!

 

[jfrubiom]

Hi again, after the installation of MacOS High Sierra and disable the AMD GPU with "nvram" options all works fine except the sound. The MBP sounds on boot, but when I use the OS the sounds not works, is like the sound are disable. Headphones works, the internal sound of MBP not

 

[LupoBello]

Hi All.
Yesterday I applied the GPU fix by modifying the gpu-power-prefs... and everything was perfect -- for 24 hrs.
MPB 15, Early 2011 running High Sierra. I didn't have any issues with sleep - it would sleep exactly when it was supposed to. The Mac worked perfectly.

Alas only 24 hrs.
Today, it started acting up and the fix doesn't survive a reboot (i.e., I apply the fix and reboot and all is fine. If I reboot once more, fix is gone). ?!

Additional info:
(a) prior to yesterday, I knew I had a bad gpu only because I was crashing to a white screen through the boot process; today, I can see red artifacts right from the start. It seems that the gpu has deteriorated further?!
(b) today, when booting to arch_linux (2019/03 distribution) the screen background is red (it was black yesterday). It looks like in spite of nomodeset, it's using the GPU ?!
(c) I did not remove any kexts. I cannot make out from this thread what is the accepted solution - to remove anything or not?
(d) I do remember to put immutability back on.

Does anyone know what is going on?

One more question. After printf to efivar, pow can one display the value of that efivar (or any other)?

Also, if I try to use gfxCardStatus 2.3 then:
1. it displays dynamic switching (even though only the Intel card is shown) and if I try to choose "integrated only", then I get a freeze crash;
2. It eventually crashes and restarts.
So I had to remove it

 

[lpuerto]

Been skimming through this thread, and it's been a lot of help with the 2011 MBP I'm working with. The AMD GPU was so bad that I couldn't boot to anything. It would freeze up on power on half the time.

I used this method as a workaround. All is well except... On wake, the Macbook has no display. (I can hear audio feedback and what not.) I implemented the Handler fix on the page I linked, but it didn't resolve the issue.

I've tried a few methods here and haven't had much luck. These include moving/automating the kext from post #875 as well as the recent post that recommends changing the CFG_FB_LIMIT value to 3.

It might be worth mentioning that this MBP is running High Sierra. Anyone have any other recommendations? I've got other projects to work on and I can't keep wasting time on this one. Thanks!

I'm in the same boat as you... everything works fine but the wakeup from sleeping/hibernation. It's not an incredible bit deal, but if it could be fixed would be great.

The funny thing is that it looks pretty random. Sometimes works and sometimes doesn't.
[doublepost=1553759433][/doublepost]

This is common practice with Security updates unfortunately. You'll have to keep a good copy aside and don't forget to bless the folder when you're done with the procedure, otherwise you may run into peculiarities.

What kind of peculiarities? do you mean the `extensions` and `extensions-off` folder? can you tell us what bless command exactly?

Did you fixed the sleeping/hibernating problem with the blessing? or that is going on here?

Thanks!

 

[Timur]

Did anyone try to completely remove the AMD GPU (hardware)? Maybe this even enables the iGPU for Bootcamp?

 

[Jester8]

First of all: In my experience Sierra is the sweet spot in terms of usability, reliability and applicability of the fix in this situation. For me at least.

For the sleep problems:

1. Disable automatic sleep, because:

2. Do not let it sleep while peripherals like disks or docks are connected via Thunderbolt.

3. Do not let it sleep via just closing the lid.

4. Make sure you have the start-up disk selected in the System Preferences


Instead of lid-closing: issue a software command to let it sleep, like "Apple Menu > Sleep" or the key combo. Automatic sleep is not a problem *if* no Thunderbolt peripherals are attached. But with software-induced sleep and waiting before lid-close the dark-screen is a very rare occurrence.

In my voodoo experience it seems hardware triggered sleep or sleep with Thunderbolt peripherals attached cause the black screen issue. Once that happens it seems to screw up an NVRAM or SMC variable, requiring a reset of those. Clearing those variables then also requires you to repeat setting the fix again.

That is of course just conjecture, but it seems to help if you really wait with closing the lid until the sleep indicator is in snoring-mode. That may take up to minute. Slowing you down occasionally is way better than a hard switch-off.

I have a problem with waking up MBP, I always go to sleep via apple logo, and after a minute computer starts to snoring. But can't wake up after that! The snoring light turns off, backlight on keyboard illuminates but screen stays black, i can hear the fans starting to work a little harder. Any solutions? Please, it sucks to always turn off mac for every short movement. Should i change status to 0, like pckrullenbol said? I run EL capitan. Thanks in advance!

 

[pckrullenbol]

Did anyone try to completely remove the AMD GPU (hardware)? Maybe this even enables the iGPU for Bootcamp?

Yes, see post permanently-disable-2011-15-17-macbook-pro-dedicated-gpu-gmux-ic-bypass.

 

[LupoBello]

Did anyone try to completely remove the AMD GPU (hardware)? Maybe this even enables the iGPU for Bootcamp?

See this hardware fix on youtube - not for the faint of heart!
Permanently Disabling the Defective GPU on a 2011 15" MacBook Pro - Hardware Mod Overviewhttps://www.youtube.com/watch?v=vbXb0gfRxEY

 

[Flexter]

Firstly, huge thanks to AppleMacFinder for posting the original solution.

I've got a 2011 MBP running Sierra (and repowered with new Samsung SSD and 16GB RAM) and have been using the software solution (CMD+S...nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00...nvram boot-args="-v"...reboot) with absolute success. However, a recent system update from Apple has created a problem. I can still get to the main login screen with my login and guest login, but only the guest login works. That is, when attempting to login to my profile it stalls and then eventually crashes and restarts back to the main login screen. The guest login however works perfectly fine. I've reset SMC and PRAM and am at loss now as to how to fix this. I had the same issue after a previous system update, but the SMC and PRAM resets seemed to do the trick. Not this time however. Has anyone encountered this and can advise on a simple solution? It's very odd that the guest login works fine, but my login doesn't. Many thanks in advance!

I managed to resolve this by removing my SSD and starting it up in my wife's MBP (13" 2011 model), then putting it back in my MBP (15" 2011) and running the noted software solution above. All fine. Now I see a new Security Update: 2019-002 10.12.6 (Sierra). Given the previous Security Update created an issue, I'm reluctant to run this one. Has anyone encountered problems running it?

 

[alberto7619]

Hi, I followed your suggestions but nothing happen after fsck -fy. I mean: when It said localhost:/ root# I wrote fsck -fy and enter but It reported: fsck usage: fsck [-fdnypq] [-t number] and again localhost:/ root# my screen Is so distorted I'm not able to read what I digit (- seems = t is similar to l...). Thanks for your help

 

[mrzo]

Hello, thanks a lot for this solution,

I applied the first method in August 2017 ( arch Linux key ) and it brings back my MBP pro-2011 to live.

2 days ago, I reapplied this solution after a PRAM, I tried with the new solution " simplest way - No needed ArchLinux - Only MacOS " It doesn't work on my laptop.

So, I reapplied arch Linux key method, It works great but now, my system starts with 6 go ram memory used.

Before, with exactly the same system, only 3go of Ram was used, ( with the method applied the first time in 2017).

Could you explain why?

 

[mrzo]

Hello, thanks a lot for this solution,

I applied the first method in August 2017 ( arch Linux key ) and it brings back my MBP pro-2011 to live.

2 days ago, I reapplied this solution after a PRAM, I tried with the new solution " simplest way - No needed ArchLinux - Only MacOS " It doesn't work on my laptop.

So, I reapplied arch Linux key method, It works great but now, my system starts with 6 go ram memory used.

Before, with exactly the same system, only 3go of Ram was used, ( with the method applied the first time in 2017).

Could you explain why?

I fixed it with Onyx, " Maintenance ".
back to normal, my system starts with 3GO of ram memory used.

 

[Ken DL]

Thank you so much for your response (Spectrum). This what I get when I tried your method.
Please chech the uploaded image.

2012 MacBook pro, MacOS High Seirra, 10.13.0.
Busted video card and I'm trying to follow mikeN fix.
I just can't get into recovery mode it doesn't matter how much I try.
Command R
Command R S
Please help,

I had this same problem with one of my 2 MBP late 2011 models - recovery partition missing. The solution for that machine was here: https://realmacmods.com/macbook-2011-radeon-gpu-disable/

 

[jfrubiom]

Hi again, after the installation of MacOS High Sierra and disable the AMD GPU with "nvram" options all works fine except the sound. The MBP sounds on boot, but when I use the OS the sounds not works, is like the sound are disable. Headphones works, the internal sound of MBP not

Hi... Can anybody help me? There is no sound when entering the system (but it does sound when you turn it on) and the brightness buttons do not work either. Thanks!!!

 

[yukari]

I managed to resolve this by removing my SSD and starting it up in my wife's MBP (13" 2011 model), then putting it back in my MBP (15" 2011) and running the noted software solution above. All fine. Now I see a new Security Update: 2019-002 10.12.6 (Sierra). Given the previous Security Update created an issue, I'm reluctant to run this one. Has anyone encountered problems running it?

I ran that Security Update and it crashed my 2011 MBP. I had to go back to the previous version via time machine. I am NOT touching any more Security Updates as it is pain in the a$$.

 

[MikeyN]

I ran that Security Update and it crashed my 2011 MBP. I had to go back to the previous version via time machine. I am NOT touching any more Security Updates as it is pain in the a$$.

Try the following:

- disable SIP
- boot normally
- apply security update
- on reboot, hold down shift (SafeMode, prevent AMD kexts from loading)
- navigate with Finder to /System/Library/Extensions
- simply trash AMDRadeonX3000.kext
- reboot (and decide whether to keep SIP disabled or not)

Reason: the latest security updates all re-install a fully working AMD.kext, at the same version as previously. That causes the hang. As it is identical to the one you moved to Extensions-off and routinely load after boot, it is easiest to just delete the new one. Up to 2019-002, all security updates should be fine.

 

[pinboll]

Throughout 10.13.6 update I am still working this way on High Sierrra.

In short: each reboot, normal or reboot during system update requires the interception of that reboot with the USB based boot image and some limited command prompt action in Ubuntu booted from USB stick prepared by https://realmacmods.com/macbook-2011-radeon-gpu-disable/. (no affiliation)
From there a shutdown and then a restart right into MacOS untill next reboot or update required.


Easy enough to get used to and takes no more time than waiting for your old magnetic HD based system too boot.



Summarized steps are based on on having ready that particular USB stick so if you are not prepared to get that USB image for your convenience at a small price, check other posts in this thread instead and please continue sharing your successes.

USB Stick boot during every reboot.

-As said, every reboot be it for system updates or critical software updates like firewall require to run the script from USB drive, then shutdown, then reboot into MacOS.

- To apply Apple update: monitor carefully, ready to intercept the system update reboot with option key and boot to USB stick mentioned above to run the script

- Doing that is easy because the USB stick provides a noob reassuring GUI in Ubuntu. Start command prompt (terminal) , issue exactly 2 command to launch RadionDisable.sh (script by website above)


- Shut down and reboot into MacOS and remember to do this in between reboot phases of MacOS update if not the system update reboot process will provide blank screen or whatever is wrong with the Macbook..


Recommended: stable and clean operating system that allows one to work without often reboot.

Reward: everything works as it should: brightness, sleep, updates (so far) and no soldering work is required. Not the one recommended by website I refer to or the full procedure.



MBP 2011 , 15" 1680x1050 display, Core i7, 2.4Ghz.

Periodically sharing what still works for me and allows me to be very lazy and NOT follow any command prompt instructions in this thread that -even though appreciating very much the sharing and that I might need those one day- so far have cost me a lot of time with no better result or convenience..
Maybe I am just lucky with my particular MBP and your mileage may differ.

 

[yukari]

Try the following:

- disable SIP
- boot normally
- apply security update
- on reboot, hold down shift (SafeMode, prevent AMD kexts from loading)
- navigate with Finder to /System/Library/Extensions
- simply trash AMDRadeonX3000.kext
- reboot (and decide whether to keep SIP disabled or not)

Reason: the latest security updates all re-install a fully working AMD.kext, at the same version as previously. That causes the hang. As it is identical to the one you moved to Extensions-off and routinely load after boot, it is easiest to just delete the new one. Up to 2019-002, all security updates should be fine.

Thanks for the tip!!!
I'll give this a go and report back.

 

[egonegon]

A temperature issue to all DAW (here Ableton) user of this thread with a MBP2011early / 15in with a broken AMD GPU:

I've recently upgraded to Sierra and have a problem with the displayed temperature of my GPU & CPU while using Ableton Live 9 or 10. After a few minutes the GPU diode shows 126 C and the CPU rises to 80-90 C (iStat). This seems arbitrary, but I think that it mainly occurs when using audio recordings / samples.

Now I do not know if this is the temperature of the deactivated AMD GPU or the Intel HD3000 ("GPU Diode" in iStat) and wonder if other users also have a similar problem. Maybe a hardware deactivation of the AMD GPU might be a solution.

Do you have any ideas?

Thanks in advance

 

[Jonathan50]

A temperature issue to all DAW (here Ableton) user of this thread with a MBP2011early / 15in with a broken AMD GPU:

I've recently upgraded to Sierra and have a problem with the displayed temperature of my GPU & CPU while using Ableton Live 9 or 10. After a few minutes the GPU diode shows 126 C and the CPU rises to 80-90 C (iStat). This seems arbitrary, but I think that it mainly occurs when using audio recordings / samples.

Now I do not know if this is the temperature of the deactivated AMD GPU or the Intel HD3000 ("GPU Diode" in iStat) and wonder if other users also have a similar problem. Maybe a hardware deactivation of the AMD GPU might be a solution.

Do you have any ideas?

Thanks in advance

Haven't used iStat, I use macsfancontrol with a 45C-70C profile, one fan on cpu core 1 sensor, other fan on gpu diode sensor. This is what the people who serviced (heated up) the logic board regularly in the past advised me. Maybe the "gpu diode" refers to the dgpu. I currently use the nvram hack - this means the amd dgpu receives full power. Those temp/fan utilities only kick in after the os has fully booted. The mbp gets seriously hot when updating the os or doing a fresh os install, during which time the temp/fan utility has not loaded and the fans just idle. In the end I just prolong the inevitable.

 

[robertmca1]

Hi,

Anyone know a reliable source of motherboards with a good replacement AMD chip on them?

Thanks a lot for this solution but I can't seem to get it to work for my mid 2010 macbook Pro 2017.. removed efivars okay using archlinux but couldn't get the printf command to work no matter what I tried, then also couldn't get through the steps in recovery mode concerning AMD kexts.

Anyway, I can't spend much more time on it, either I buy a new MBP or change the motherboard.. unless someone is interested: I can transfer $ for your time if you can walk me through the bits I'm stuck on..

 

[eggnchips]

Hi there,
I got my Macbook 2011 running El Capitan back to life by taking it apart and baking the board, and ended up on here looking for a more permanent solution.
Really nooby question: What's the advantage of follwing the instructions in this thread compared to choosing 'Better battery life' in Energy saver and then choosing 'Integrated only' in gfxstatus?
All the programing intimidates me.

 

[johnnycashfl0w]

Hello,

Recently got this problem awhile ago and followed this guide step by step and it didn't work. I knew I messed up somewhere and I think I found the problem.

When I check ls with the Arch Live ISO, I made a typo in the gpu-power-prefs "...9cc3-6815686e39d9" Whereas the 9 is supposed to be a 0, thanks chubby fingers. Is there any way to edit this as I can't for the life of me figure out how.

Also, when I bought this Mac it didn't have an OS installed. So all this work is being done without an OS. Is it possible to just install a Linux distro after this work-around? Or do I need MacOS to fix this computer? I had planned on trying to install Manjaro or ElementaryOS on this Mac as I don't use MacOS and got this laptop cheap, as it needed repairs.

Thanks, any help would be appreciated!
[doublepost=1554830006][/doublepost]

Hello,

Recently got this problem awhile ago and followed this guide step by step and it didn't work. I knew I messed up somewhere and I think I found the problem.

When I check ls with the Arch Live ISO, I made a typo in the gpu-power-prefs "...9cc3-6815686e39d9" Whereas the 9 is supposed to be a 0, thanks chubby fingers. Is there any way to edit this as I can't for the life of me figure out how.

Also, when I bought this Mac it didn't have an OS installed. So all this work is being done without an OS. Is it possible to just install a Linux distro after this work-around? Or do I need MacOS to fix this computer? I had planned on trying to install Manjaro or ElementaryOS on this Mac as I don't use MacOS and got this laptop cheap, as it needed repairs.

Thanks, any help would be appreciated!

Also, I'll add a photo of just what I mean in case there is some confusion as to where I'm at.