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

iReborn · Jan 6, 2018

Hi. I initially followed all the advice on these posts on my MBP, but it would never get past the booting and would freeze. Btw, I had Mavericks installed.

During the process of attempting to fix it I managed to burn out the HDD so I have swapped it out with an SSD. I now have formatted and installed the original OS (Lion), but I'm still having the issue of not getting past the booting screen. The only way I'm able to access the system is if i start in Safe Mode.

While in safe mode, I'm looking at the MBP Graphics/Displays and it shows 2 video cards: AMD Radeon HD6490M (PCIe) and Intel HD Graphics 3000 (Built-In). It seems that the Intel HD Graphics 3000 is the active once since it shows "Display Type: LCD".

I've read a few posts on here that I should start in Safe Mode and reload the AMDRadeonX3000? But now that I have a new SSD installed with a new OS, I no longer have the disabled kexts directory (due to new SSD?). And when I view the "/Systems/Library/Extensions/" I'm not finding any of the "AMD" files. I see plenty of the "ATI" files, should I be moving those instead?

Sorry if my post seems confusing, as I am as well confused as what to do now. Let me know if I can provide any other information to clarify.

MikeBr101 · Jan 7, 2018

Hi to everyone on this excellent link

I successfully brought my late 2011 MBP back to life using the procedures within this link and I'm extremely grateful to all those who contributed their time and expertise.

I'm sure the question I'm going to ask has been raised somewhere within this link but at 56 pages it would take days to trawl through it!!

Basically I'm running MAC Sierra version 10.12.6 (16G1036) and keep getting reminders to update to High Sierra!!

Would that update remove the changes I made to use only the Intel Graphics as I really don't fancy going through it again!!!

Ordinarily I'd be happy just to continue using MAC Sierra but following the announcement that all Intel based system are potentially under threat I'd like to ensure that I'm running all the latest security fixes to at least try to be as safe as possible!!

Awediohead · Jan 7, 2018

Many thanks for all the work done to enable me to bring my dead MBP back to life. I actually followed a video to walk me through the process (Archlinux & EFI) but the video maker very decently gave all proper credit to you for doing all the hard work.
Just out of interest can anyone speculate how easy it would be for Apple to create some sort of preference pane to select integrated only graphics? I mean cost in terms of man hours to write the code?

I just wonder because if the idea is to force people to buy new machines from reading the comments on this thread it seems to have back fired on them pretty savagely - I for one am extremely unlikely to buy another new Apple computer after my first experience with my MP 1,1 and now this with the MBP 2011. Not that I don't appreciate that machines have a finite life span, but its not the same when that life is shortened by cynical decisions as opposed to sound technical reasons, especially from a company purporting to be "green".

SteelCees · Jan 8, 2018

MikeyN said:
There is not *one* guide to write up. Many roads lead to Rome. The best option would be if AppleMacFinder would update the first post of this thread pointing to the best alternatives.

Anyway. Even if this post now will quickly drown in the sheer length of this thread, I think this is currently one of the better guides:

#####__ The Guide __#####

This guide assumes that you run a stock system. Problem just occured. That means:
This guide assumes that all kexts are still in their default location /System/Library/Extensions.
Having all AMD-kexts there except one is beneficial for 'proper' operation.

To get some display acceleration back it will be necessary to force the machine to not boot into discrete graphics (dGPU) but directly into integrated graphics (iGPU). This will give you back your laptop – but you will lose some features: e.g. the ability to drive an external display. Thunderbolt data connections should work.

The initial procedure:

– To start from a clean slate: reset SMC and PRAM/NVRAM:

shutdown, unplug everything except power, now hold

<leftShift>+<Ctrl>+<Opt>+<Power>

release at the same time;

– Now power on again and hold

<Cmd>+<Opt>+<p>+<r>

at the same time until you hear the startup chime two times.

– Boot into Recovery by holding

<Cmd>+<r>+<s>

– Disable SIP:

csrutil disable

– disable dGPU on boot

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

– enable verbose boot mode:

nvram boot-args="-v"

– reboot into single user-mode by holding

<Cmd>+<s>

on boot

– mount root partition writeable

/sbin/mount -uw /

– make a kext-backup directory

mkdir -p /System/Library/Extensions-off

– only move ONE offending kext out of the way:

mv /System/Library/Extensions/AMDRadeonX3000.kext /System/Library/Extensions-off/

– let the system update its kextcache:

touch /System/Library/Extensions/

– wait for the kextcache process to finish
then

reboot

Reboot normally:
you will have an accelerated iGPU display.

But the system doesn't know how to power-management the failed AMD-chip.
For that you have to either manaully load the kext after boot by:

sudo kextload /System/Library/Extensions-off/AMDRadeonX3000.kext

Automate this with the following LoginHook:

sudo mkdir -p /Library/LoginHook
sudo nano /Library/LoginHook/LoadX3000.sh

with the following content:

#!/bin/bash
kextload /System/Library/Extensions-off/AMDRadeonX3000.kext
exit 0

then make it executable and active:

sudo chmod a+x /Library/LoginHook/LoadX3000.sh
sudo defaults write com.apple.loginwindow LoginHook /Library/LoginHook/LoadX3000.sh

Preventive measures for future use

There are two further caveats to know: This is reversible when the SMC/PRAM/NVRAM is reset. If that happens the GPU-power-pref nvram can/has to be set again to force the use of the iGPU from boot-time.

Since this can happen quite easily (and is often erroneously recommended way too many times than it is actually useful), you should probably prepare for such a scenario and create a simple script to greatly speed up the process and also make entering the necessary variable much less error prone:

sudo nano /force-iGPU-boot.sh

– Enter the following content to this file:

#/bin/sh
sudo nvram boot-args="-v"
sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
exit 0

– Now make that executable:

sudo chmod a+x /force-iGPU-boot.sh

In the future, when the SMC/PRAM/NVRAM gets reset to default values it is now possible to boot into SingleUser with:

<Cmd>+<s>

– And after mounting your boot-volume read-write to execute just:

sh /force-iGPU-boot.sh

This setup has now one kext in a place Apple's installers do not expect. That is why in this guide SIP has not been reenabled. If an update that contains changes to the AMD drivers is about to take place it is advisable to move back the AMDRadeonX3000.kext to its default location before the update process. Otherwise the updater writes at least another kext of a different version to its default location or at worst you end up with an undefined state of partially non-matching drivers.

After any system update the folder /System/Library/Extensions has to be checked for the offending kext. Its presence there will lead to e.g. a boot hang on Yosemite and Sierra, an overheating boot-loop in High Sierra.

Further: this laptop is overheating, no matter what you do. The cooling system is inadequate and the huge number of failing AMD chips are just proof of that.

To prolong the life of this now hacked machine it is advisable to abstain from really heavy lifting over prolonged stretches of time. Strictly follow the usual recommendations for laptops: use on hard surfaces, keep the fans and fins inside it clean. Using any fancontrol software with relatively aggressive settings should also help: like smcFanControl, MacsFanControl, or TGPro (the latter both commercial).

This is fairly complete and what I do recommend to everyone asking me.
Nevertheless. We're not done here, yet. Improvements are welcome. Share them!

MBPro17 · Jan 8, 2018

FGuarini said:
Fix for 17 inch dGPU switch issue

(Tested successfully in both “early” and “late” 2011 17 inch MacBook Pro)

This guide is based on the experience of many users (including me) while trying to fix the very well known issue with AMD dGPU on 17’’ MacBook Pro from 2011 (both early and late):

Step 0) As a starting point I made a clean installation of Sierra (Version 10.12.4) — This is just a step for establishing a common middle ground and is not really needed….

0.1) To do this just download the installer from the App Store and then use “DiskMaker X” to create a bootable installation.

0.2) After the bootable image is created, proceed to turn off your computer and hold the “Alt” or “Options” Key. Select the Sierra installer and proceed with the installation (I format the HDD partition to make a clean install on it)

Note: You might need to do this on another computer. Just buy one of those cheap usb to sata connectors and use it to connect it to another Mac so you don’t risk having your installation failed because of your machine.

Step 1) Prepare a Bootable USB pendrive with a non GUI Linux (Credits to AppleMacFinder)

1.1) Download ArchLinux ISO

You need a working computer for that and a spare CD/DVD/USB drive. Download the latest Arch Linux ISO image from this page - https://www.archlinux.org/download/ , at the time of writing it is archlinux-2017.03.01-dual.iso . Then you could either simply burn this ISO to CD/DVD (which later could be either inserted to MBP's SuperDrive or External DVD Drive connected to MBP by two USB cables) or create a bootable USB: use the great detailed instructions from this page, https://wiki.archlinux.org/index.php/USB_flash_installation_media

1.2) Creating the bootable USB with the .iso:

In macOS

First, you need to identify the USB device. Open /Applications/Utilities/Terminal and list all storage devices with the command:

*) diskutil list

Your USB device will appear as something like /dev/disk2 (external, physical). Verify that this is the device you want to erase by checking its name and size and then use its identifier for the commands below instead of /dev/diskX.

A USB device is normally auto-mounted in macOS, and you have to unmount (not eject) it before block-writing to it with dd. In Terminal, do:

*) diskutil unmountDisk /dev/diskX

Now copy the ISO image file to the device. The dd command is similar to its Linux counterpart, but notice the 'r' before 'disk' for raw mode which makes the transfer much faster:

*) sudo dd if=path/to/arch.iso of=/dev/rdiskX bs=1m

After completion, macOS may complain that "The disk you inserted was not readable by this computer". Select 'Ignore'. The USB device will be bootable.

Step 2) Boot to Linux (Credits to AppleMacFinder):

2.1) Boot to it: insert this CD/DVD/USB to Macbook Pro, hold Option key while booting, choose "EFI boot" (that is your bootable installation media), press "e" key to edit the GRUB options of the Arch Linux archiso x86_64 UEFI CD menu entry while it is selected at the main screen, add nomodeset to the end of this line and press Enter. If everything is done correctly, you will find yourself at the Linux console! (It takes some time so be patient and wait for the prompt)

2.2) Edit EFI vars: looks like efivarfs filesystem is mounted by default! So you can already cd /sys/firmware/efi/efivars and ls to explore this directory and see if there is a "gpu-power-prefs-..." variable (where ... is UUID of this variable).

2.2-Case 1:

If there is such a variable, its better to remove it with rm.

*) rm gpu-power-prefs-…

In my case the efivarfs has been mounted by default with read/write permissions, but if you are getting the "operation not permitted" message while attempting to rm, it means that in your case efivarfs has been mounted as read-only and you need to remount it with read-write permissions and try again (credits to totoe_84 for this valuable addition) (Try this and then try to remove it):

*) cd /

*) umount /sys/firmware/efi/efivars/

*) mount -t efivarfs rw /sys/firmware/efi/efivars/

*) cd /sys/firmware/efi/efivars/

*) rm gpu-power-prefs-…

If this also fails (If you still can’t erase the file) use chattr command to disable file immutability and then erase the file:

*) chattr -i "/sys/firmware/efi/efivars/gpu-power-prefs-…”

*) cd /sys/firmware/efi/efivars/

*) rm gpu-power-prefs-…

2.2-Case 2:

The file gpu-power-prefs-… doesn’t exist well then you don’t have to delete it hahaha. (I repaired 2 17 inch models and 1 didn’t have it, so it’s fine)

2.3) Create a new gpu-power-prefs-… file (Original credit mentioned above, https://github.com/0xbb/gpu-switch/blob/master/gpu-switch, Credits to AppleMacFinder):

*) printf "\x07\x00\x00\x00\x01\x00\x00\x00" > /sys/firmware/efi/efivars/gpu-power-prefs-fa4ce28d-b62f-4c99-9cc3-6815686e30f9

2.4) Add immutability to the gpu-power-prefs-… file (Credits to AppleMacFinder):

This chattr command is supposed to lock a file to make it accessible only by "superuser" - and so that, while booting, your EFI will have no chance to screw up your gpu-power-prefs-... variable under any circumstances

*) chattr +i "/sys/firmware/efi/efivars/gpu-power-prefs-fa4ce28d-b62f-4c99-9cc3-6815686e30f9"

2.5) Unmount efivars and reboot (Credits to AppleMacFinder):

Could not unmount efivars if you are inside this directory, so change to the root directory

*) cd /

*) umount /sys/firmware/efi/efivars/

Guarantees that your EFI variables are flushed to efivarfs filesystem, please unmount it safely before rebooting)

*) reboot

3) Eliminate AMD Kexts (Credits to newfield),
Note: You might need to do this every time you do an OS updates, since each update normally writes the AMD Kexts again.

(His words and this also happened to me!: After disabling the dGPU using Arch, normal boot would hang halfway. Although safe boot would work. I wound up having to remove all the AMD kext files in the Terminal in Recovery Console)

Trying to remove them in Single User just gave me sandbox errors. (Summary -> Don’t do it in Single User Mode the one that you boot with Cmd + S)

3.1) So what you have to do is:

If you have FileVault Unlock it first:

Unlock first.

Then Boot into Recovery (“cmd + r”, it will boot without failing, if it fails then repeat step 2 and then after that boot directly into recovery with command + R, I had to do this once because the dGPU got active again after booting into the os with AMD kexts)

*) Boot into recovery mode (Command + r)

*) Start Terminal

*) diskutil cs list (find UUID for drive)

*) diskutil coreStorage unlockVolume UUID

*) cd /Volumes/Macintosh\ HD

*) mkdir AMD_Kexts

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

*) reboot

(If you only have one storage with 1 partition just use "cd /Volumes/Macintosh\ HD" and the remaining commands after starting the terminal)

Extra STEP), if your PC is now working! Download “steveschow” branch of gfxCardStatus (gfxCardStatus v2.4.3i) or just download the app directly from:

URLS:

https://github.com/steveschow/gfxCardStatus/releases

https://github.com/steveschow/gfxCardStatus

With this application you can even prove that the dedicated GPU can't get activated. Even if you try to change the selected GPU to the dedicated one, it just won't change.

—————

The End!

AND VOILA!!! You have a working 17 inch MacBook Pro. As I said I tested this with an early 2011 and late 2011 17 inch MacBook Pro’s and both are now running (Before they were both dead)

Big thanks to AppleMacFinder, to the makers and contributors of this thread, to gfxCardStatus maker and forkers (steveschow) and to switch-gpu makers I can’t thank you guys enough as I am so happy to bring both of this incredible machines back to life. With this post I am not trying to take any credit, but as I had 2 machines I run into different issues with both, which could be helpful to others, thats why I was inclined to make “my own” guide and share it with you.

I just created an account here to share this, Hope it helps more people!

I did this with the assistance of someone fluent in Linux and Macs.

Well the solution above is what finally worked for us. At first we just did the part without killing the AMD drivers. It would boot once but then the EFI (or whatever you call it, the GPU-Power-Pref) would revert to how it was. After we killed the drivers and then did the EFI changes it worked every time.

I don't know why the changes kept reverting but they did.

Thank you to the thread starter and everyone else in this thread.

17" Macbook Pro for life!

vieaa · Jan 9, 2018

My early 2011 MBP is working well on the iGPU thanks to this thread. So happy to be using it again instead of being forced to upgrade to that dreadful butterfly keyboard on current models.

Monic · Jan 10, 2018

Awediohead said:
Many thanks for all the work done to enable me to bring my dead MBP back to life. I actually followed a video to walk me through the process (Archlinux & EFI) but the video maker very decently gave all proper credit to you for doing all the hard work.
Just out of interest can anyone speculate how easy it would be for Apple to create some sort of preference pane to select integrated only graphics? I mean cost in terms of man hours to write the code?

I just wonder because if the idea is to force people to buy new machines from reading the comments on this thread it seems to have back fired on them pretty savagely - I for one am extremely unlikely to buy another new Apple computer after my first experience with my MP 1,1 and now this with the MBP 2011. Not that I don't appreciate that machines have a finite life span, but its not the same when that life is shortened by cynical decisions as opposed to sound technical reasons, especially from a company purporting to be "green".

Hi Awediohead, could you link to the video you followed? Thanks!

MBPro17 · Jan 11, 2018

MBPro17 said:
I did this with the assistance of someone fluent in Linux and Macs.

Well the solution above is what finally worked for us. At first we just did the part without killing the AMD drivers. It would boot once but then the EFI (or whatever you call it, the GPU-Power-Pref) would revert to how it was. After we killed the drivers and then did the EFI changes it worked every time.

I don't know why the changes kept reverting but they did.

Thank you to the thread starter and everyone else in this thread.

17" Macbook Pro for life!

A little scare today. I had done multiple shut downs and start up since the fix. For some reason today it only gave me a black screen with no chime. FInally after 20 or 30 times it started.

Needhelp1998 · Jan 11, 2018

Hi what i do wrong ? My archlinux dosent start if i write nomodeset and press enter then comes blackscreen and nothing happen? But UEFI V1 and UEFI V2 starts when i write nomodeset? My macbook is macbook pro 8.2 2011 early i7 and boot stuck white screen or gray sometimes blue and sometimes right up on apple logo is pixel line:0

wilsondr · Jan 11, 2018

Made an account to say thanks to everyone involved in this.

I had an interesting time. Got a 2011 MacBook Pro 15 given to me by relative to extract hard drive from dead MacBook. Did some reading about the issue and came across this.

In my excitement I didn't really read though enough so just cracked on with solution in the first post.
Managed to boot into native El Capitan to my surprise using Arch linux, but it revered on reboot. Happy with the knowledge there was something to salvage, I gave the native hard drive back to relative and inserted blank SSD ready to do a "proper fix"

Here are when my problems really began.

I tried everything to install an OSX onto the new hard drive. I made bootable UBS stick which I wasn't able to get into without the WSOD (white screen of death). I tired using various methods (mainly Arch and single user mode) to remove GPU-Power-Prefs to varying degrees of success.

I'd be able to boot into the bootable USB, but when I tried to install it, it would return an error message saying the application failed to install.

This was the same story for putting the bootable image onto the new SSD.

The furthest I got was removing GPU-power-prefs and then going onto internet recovery to download Lion, which I imagine the laptop originally shipped with. It got so far as setting the keyboard preferences and then froze. No matter what I did it wouldn't get past this screen.

Other parts of the guides didn't work e.g. removing AMDRadeonx3000 kexts- probably because they weren't actually installed yet.

In the end, I removed the fan connects from the logic board and turned the laptop on. It got bloody hot over the course of 5 minutes even though it wasn't really doing anything. I then rebooted and I managed to finish the instillation of Lion! I imagine heating it sufficiently temporarily reconnected the iGPU to the logic board properly.

I saw MikeyNs guide quoted in #1379 and decided to give this a go now I finally have a "fresh" system. Before I tried I managed to update to Sierra, having to overheat the laptop a few times to complete instillation.

Then I followed the guide word for word and it's working! Happy days.

I won't be upgrading to High Sierra or any other OSX until I'm confident I'll be able to do the extra steps he suggests i.e. putting Kexts back into their original places before updating etc.

Thanks again!

wilsondr · Jan 11, 2018

Needhelp1998 said:
Hi what i do wrong ? My archlinux dosent start if i write nomodeset and press enter then comes blackscreen and nothing happen? But UEFI V1 and UEFI V2 starts when i write nomodeset? My macbook is macbook pro 8.2 2011 early i7 and boot stuck white screen or gray sometimes blue and sometimes right up on apple logo is pixel line:0

Have you put a space between the pre written command and nomodeset ? It also takes about 15s to load if done correctly

rsindex · Jan 11, 2018

wilsondr said:
Have you put a space between the pre written command and nomodeset ? It also takes about 15s to load if done correctly

Not sure if you are asking but if so, yes friend, you have to add a space between whatever is thereand nomodeset. A bit weird because I was having the same issue so I tested the USB Archlinux on my Macbook Air and that one booted ok withouth the space.
[doublepost=1515714415][/doublepost]test
[doublepost=1515715434][/doublepost]Thank you everyone involved!!!! My MBP is great again! Btw WTF with Apple?

Needhelp1998 · Jan 11, 2018

wilsondr said:
Have you put a space between the pre written command and nomodeset ? It also takes about 15s to load if done correctly

rsindex said:
Not sure if you are asking but if so, yes friend, you have to add a space between whatever is thereand nomodeset. A bit weird because I was having the same issue so I tested the USB Archlinux on my Macbook Air and that one booted ok withouth the space.
[doublepost=1515714415][/doublepost]test
[doublepost=1515715434][/doublepost]Thank you everyone involved!!!! My MBP is great again! Btw WTF with Apple?

Yes i putted space but nothing happen only blackscreen and i am waited about 5-10minutes but still no

source21 · Jan 12, 2018

Hello everyone! This guide working with iMac 2011 Mid ??? Radeon 6750M graphic

MBPro17 · Jan 12, 2018

I had the problem again afte rthe fix. Shutdown normally

When I went to start up all I got was a black screen and no chime sound. Tried about 20 times before it finally started up again.

Anyone experience similar?

chnapo · Jan 13, 2018

Hi guys. I did the EFI fix as decribed in the original post. My MCB Pro late 2011 ran again. But the thing is, that when I try to run photoshop, or some demanding app, it WILL turn on the AMD GPU = it will get stuck and I only can force turn off. After several attempts to run PC, it is now stuck at apple logo with bar loaded at cca 75% - at the same spot as it used to be before the fix. I tried to reset NVRAM, SMC and do the fix again, but whatever I do, it does not get through that point anymore. I didn´t delete kexts, as the EFI fix was presented as 100% working solution. Any help please?

xanderx007 · Jan 13, 2018

chnapo said:
Hi guys. I did the EFI fix as decribed in the original post. My MCB Pro late 2011 ran again. But the thing is, that when I try to run photoshop, or some demanding app, it WILL turn on the AMD GPU = it will get stuck and I only can force turn off. After several attempts to run PC, it is now stuck at apple logo with bar loaded at cca 75% - at the same spot as it used to be before the fix. I tried to reset NVRAM, SMC and do the fix again, but whatever I do, it does not get through that point anymore. I didn´t delete kexts, as the EFI fix was presented as 100% working solution. Any help please?

At this point, I suggest you try to the GRUB solution.

GreenFreaK · Jan 14, 2018

This guide was perfect and worked flawlessly on a Macbookpro8,3 (Late 2011 - 17" 2.4GHz). Thank you so much for posting this!!!

I spent 2 days trying to figure out what was going on. All methods of starting OS/X failed at the infamous "white screen of death" where the loaders would work, then when it went to boot into the GUI, the white screen would appear and the fans would spin up high.

These methods included:

OS/X El Capitan Installer
Internet Recovery Mode Installer
ASD - OS Boot Method
Original HDD with OS/X Snow Leopard

This is on a computer that was reporting graphic issues so that's why I turned to google to search possible symptoms and I remember the AMD GPU had issues on these systems. I'll be book-marking this post for sure!

ididntmemeto · Jan 14, 2018

hey everyone,

using the solutions posted above, I am able to run sierra, but the computer won't wake up from sleep and the only way to get it to boot up is to force shut down and boot into single user mode and run the shell script again that disables the dedicated GPU. Does anyone have any suggestions? 2012 Retina MacBook Pro 15"

xanderx007 · Jan 14, 2018

ididntmemeto said:
hey everyone,

using the solutions posted above, I am able to run sierra, but the computer won't wake up from sleep and the only way to get it to boot up is to force shut down and boot into single user mode and run the shell script again that disables the dedicated GPU. Does anyone have any suggestions? 2012 Retina MacBook Pro 15"

That also happened to me a few times. I suggest you try to the GRUB solution.

ididntmemeto · Jan 14, 2018

xanderx007 said:
That also happened to me a few times. I suggest you try to the GRUB solution.

thanks. Trying the GRUB solution but after following all the instructions it just boots to the GRUB command line.

partysoft · Jan 15, 2018

is it possible to run the the install cd without getting the grey screen?
I think I have a corrupted filesystem that won't boot anymore after I messed around with the kexts but I can't run the el capitan installation usb/cd
Same goes for recovery mode or timemachine disk

thompsam · Jan 15, 2018

I had similar experiences, but after going through this a few times, I seem to have resurrected my machine so that it will survive reboots. By the way, my machine is a 15”, late 2011 Mcbook Pro running High Sierra. My thanks to all who have pioneered this process and even more importantly, took the time to document it and share with all of us.

I do have 2 questions for others who have succeeded with this process:

1. Can you sleep your machine? Shutting the lid or manually trying to put mine to sleep via the Apple menu seems to have no effect.

2. My brightness keys on the keyboard no longer seem to have any effect. My screen is bright enough to be usable, but since I can’t “sleep” it, I thought i’d Use the brightness keys to turn off the screen. No dice, hitting the keys, either increase or decrease has no effect.

Are others experiencing this and if so, has anyone found aa fix for either. Note that if this is discussed in one of the earlier 56 pages and I have missed it, I apologize.

mercury_22 · Jan 17, 2018

Late 2011 15" Macbook Pro for sale in Leeds, UK.

New logic board and this method would surely get it running again.

https://www.gumtree.com/p/macs/appl...ro-for-spares-or-repairs-fresh-ram/1283224114

Please contact if you're interested.

Pete

spinko · Jan 17, 2018

Bwil10 said:
This fix works for the 15" also?

Yes, I can confirm it works on a late 2011 MBP. A great thanks to all who contributed to build this delicious recipe

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

macrumors newbie

macrumors newbie

macrumors newbie

macrumors newbie

macrumors member

macrumors newbie

macrumors newbie

macrumors member

macrumors newbie

macrumors newbie

macrumors newbie

macrumors newbie

macrumors newbie

macrumors newbie

macrumors member

macrumors newbie

macrumors 6502

macrumors member

macrumors newbie

macrumors 6502

macrumors newbie

macrumors newbie

macrumors newbie

macrumors newbie

macrumors regular

Our Staff