Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

snapyshot

macrumors newbie
Aug 23, 2018
1
0
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!

I just made a login to this page to thank YOU, MikeyN!!! You made my macbook pro 2011 work again! It works as fine and good as ever before the classic GPU problem occured! I even don't experience any loss of graphic-power (i'm not a gamer).

I got the motherboard changed by apple on guarentee in 2015 after the problem first occured. In 2017 the same problem occured on the new motherboard. So i went to a specialist and he did a reballing (new soldering for 200 Euros). Then it worked again for about one year and in 2018 it broke again. Everyone was telling me to let this macbook go and put it to the grave.

I'm so happy to have this/my machine working again and that i don't have to through away – this would be such a shame because everything else beside the failed GPU works just great.

Thank you again MikeyN for your professional help and easy description for non-coders!
Cheers!
 

mikecwest

macrumors 65816
Jul 7, 2013
1,193
496
This one?

https://forums.macrumors.com/thread...fi-variable-fix.2037591/page-34#post-24944928


EDIT: yes, it is, works very good

Question, it is there any problem if I disable the boot-args="-v" ?
I mean, if I roll back to

sudo nvram boot-args=""
sudo nvram -d boot-args
Disabling the -v should not be a problem... I typically don't have it enabled. As of now, I believe that the kext developer mode is also no longer needed in High Sierra, but you do have to disable SIP, and maybe just partially will work.
 

JMVB

macrumors regular
May 16, 2016
186
51
Disabling the -v should not be a problem... I typically don't have it enabled. As of now, I believe that the kext developer mode is also no longer needed in High Sierra, but you do have to disable SIP, and maybe just partially will work.


Thank you.
One laptop have El capitan and the SIP disabled
The other one have Yosemite
 

KiDo

macrumors member
Oct 3, 2006
59
3
Amsterdam, Netherlands
By "Long Term" you mean? I have been doing this for more than a year.

I tried the Archlinux one, and it was much more complicated, and caused more issues.

I actually made a bash script, which can be found somewhere in here...so all have to do is go into single use mode, type "bash roxy" and it runs the nvram command....The only time I have to type the whole command, is when there is a software update....I have to be ready to hit CMD-S when the first portion of the update takes place.

Does your script make it wake up from sleep and adjust the brightness? Is the one you uploaded in #846 still up to date? I got everything working now except that. I think I have messed up the moving of kexts at some point, using a guide that made me make a AMD_KEXTS map at root and moving all of the kexts there. I ended up booting up with a blueish screen and weird artifacts at the mouse cursor etcetera. I think I fixed that by putting the files back in the map at some point.

Now I still have that AMD_KEXTS folder with all the amd kexts in system/library/extensions/ , and I tried deleting it but it won't empty the crash cause it say's theyre in use. The X3000 kext is still in Extensions as well.
 
Last edited:

mikecwest

macrumors 65816
Jul 7, 2013
1,193
496
Does your script make it wake up from sleep and adjust the brightness? Is the one you uploaded in #846 still up to date? I got everything working now except that. I think I have messed up the moving of kexts at some point, using a guide that made me make a AMD_KEXTS map at root and moving all of the kexts there. I ended up booting up with a blueish screen and weird artifacts at the mouse cursor etcetera. I think I fixed that by putting the files back in the map at some point.

Now I still have that AMD_KEXTS folder with all the amd kexts in system/library/extensions/ , and I tried deleting it but it won't empty the crash cause it say's theyre in use. The X3000 kext is still in Extensions as well.

As far as my "bash roxy" script goes, I have not changed it, since the time I posted it. I have read that the dev-mode enable portion is no longer needed, but there is no real reason to remove it.

I don't have the brightness issue, because I don't remove those kexts....when you remove the kexts, i believe that is what causes it..

When I wake up with a black screen, I can force shutdown if necessary.....No always ideal, but works.

Once you are shut down, you can two methods...hold CMD while booting, and just "feel it out" and wait about thirty seconds...press enter a few times to make sure that you have a blank line, type "bash roxy" (without quotation marks) and press enter.....You should chime, and reboot with the INTEL GPU...


You can also use a bright flash light, and shine it through the apple behind your screen or somewhere on the left side of your screen, if you are in single user mode, you should see a bunch of text, you probably can't read it, but if you see it, you know you are in the right place.

I try not to let the Mac die, because then I have more issues. I have also changed my airport card to use the C.A.T toolkit, and occasionally after having to zap the p-ram or reset the pmmu, the card will stop working....but that OK, I reboot and run bash roxy again, go into recovery, disable SIP, then reboot and run bash roxy, then all is good.

I rarely shutdown my Mac, or reboot it, so I don't need these things ofter.
 

JMVB

macrumors regular
May 16, 2016
186
51
Does your script make it wake up from sleep and adjust the brightness? Is the one you uploaded in #846 still up to date? I got everything working now except that. I think I have messed up the moving of kexts at some point, using a guide that made me make a AMD_KEXTS map at root and moving all of the kexts there. I ended up booting up with a blueish screen and weird artifacts at the mouse cursor etcetera. I think I fixed that by putting the files back in the map at some point.

Now I still have that AMD_KEXTS folder with all the amd kexts in system/library/extensions/ , and I tried deleting it but it won't empty the crash cause it say's theyre in use. The X3000 kext is still in Extensions as well.

Like I said, I did the procedure in 2 macbook's pro 2011

The first one, with the archlinux procedure (Yosemite, and also remove the AMD kexts)
The fix gone with a battery disconnection, and then I used the Bash Roxy

The second one, with El capitan, fixed with the realmacmods utility (it is an Ubuntu live distro and a script)
I removed the R8911. The AMD card is no longer visible in the system information

Both cases, the backlight bright and sleep is working fine
 

mikecwest

macrumors 65816
Jul 7, 2013
1,193
496
Like I said, I did the procedure in 2 macbook's pro 2011

The first one, with the archlinux procedure (Yosemite, and also remove the AMD kexts)
The fix gone with a battery disconnection, and then I used the Bash Roxy

The second one, with El capitan, fixed with the realmacmods utility (it is an Ubuntu live distro and a script)
I removed the R8911. The AMD card is no longer visible in the system information

Both cases, the backlight bright and sleep is working fine

Did you have to remove the logic board to take off r8911?
 

JMVB

macrumors regular
May 16, 2016
186
51
Did you have to remove the logic board to take off r8911?


No, i didnt

820resistor-1024x673.jpg
 

KiDo

macrumors member
Oct 3, 2006
59
3
Amsterdam, Netherlands
As far as my "bash roxy" script goes, I have not changed it, since the time I posted it. I have read that the dev-mode enable portion is no longer needed, but there is no real reason to remove it.

I don't have the brightness issue, because I don't remove those kexts....when you remove the kexts, i believe that is what causes it..

When I wake up with a black screen, I can force shutdown if necessary.....No always ideal, but works.

Once you are shut down, you can two methods...hold CMD while booting, and just "feel it out" and wait about thirty seconds...press enter a few times to make sure that you have a blank line, type "bash roxy" (without quotation marks) and press enter.....You should chime, and reboot with the INTEL GPU...


You can also use a bright flash light, and shine it through the apple behind your screen or somewhere on the left side of your screen, if you are in single user mode, you should see a bunch of text, you probably can't read it, but if you see it, you know you are in the right place.

I try not to let the Mac die, because then I have more issues. I have also changed my airport card to use the C.A.T toolkit, and occasionally after having to zap the p-ram or reset the pmmu, the card will stop working....but that OK, I reboot and run bash roxy again, go into recovery, disable SIP, then reboot and run bash roxy, then all is good.

I rarely shutdown my Mac, or reboot it, so I don't need these things ofter.
Sorry for the late reply, I have been doing other stuff the past few days. So as I said in my previous post: I put all the kexts back in place after the whole blue screen with artifacts scenario, but my system still does not have any brightness controls or wakes up from sleep.

Thats not the biggest issue, it's just that I travel a lot with my notebook and putting it in my bag (closed lid) while its awake makes me think the whole thing will just heat up like crazy in there.

I also have a feeling the card is draining my battery even faster than normal but I don't know for sure since my battery has been degrading pretty quickly anyway, the menu bar icon says Replace Soon for a while now..[/QUOTE]
 

SpiX-777

macrumors newbie
Aug 25, 2018
1
0
I did at thing that you has type and now i´m use igpu but os X is crashing. Do you have tips?
 

jon08

macrumors 68000
Nov 14, 2008
1,886
105
If you see an apple logo, that means you didn't get into the single user mode...Do you know how to get into single user mode?

You should zapping your p-ram, and resetting your PCM.

To reset your PCM, make sure your computer is turned off (force shut down by pressing and holding power if needed) and plugged in, press left-shift, option, and control while pressing power (hold for five seconds). Your light on your charging cable will cycle from orange to green.

Now, let go of power, press power and quickly press and hold option-command-p-r (all at the same time, let it chime three times and let go.)

Now, quickly press, CMD-S until you see a bunch of text on the screen.

Now at the prompt enter "nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00" press enter

type reboot and press enter


Alternately, you may have an additional issue that you are experiencing....If you have a 2011 MBP, it is possible that your drive is failing. Have you changed your drive before?

also, it is a very long code. Make sure you type it correctly.... and DON'T type the " " or it won't work.
[doublepost=1534820818][/doublepost]
None of those things are needed.....just use the

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

in single user mode, each time you experience the issue....
Thanks for your reply.

Last night my MBP’s battery depleted while it was sleeping, so this morning when I booted my MBP I was left with gray screen again.

OK, so I turned it off and booted into single user mode.

I inserted the “nvram” command and rebooted. So once it rebooted I was still left with gray screen, but this time it had the Apple logo and an empty progress bar below.

I’m on the latest version of High Sierra if this helps.

So what should I really do whenever I face this situation to get it to work again after the gray screen appears? Apparently just inserting the nvram command won’t help.

Please help?
 

jon08

macrumors 68000
Nov 14, 2008
1,886
105
Thanks for your reply.

Last night my MBP’s battery depleted while it was sleeping, so this morning when I booted my MBP I was left with gray screen again.

OK, so I turned it off and booted into single user mode.

I inserted the “nvram” command and rebooted. So once it rebooted I was still left with gray screen, but this time it had the Apple logo and an empty progress bar below.

I’m on the latest version of High Sierra if this helps.

So what should I really do whenever I face this situation to get it to work again after the gray screen appears? Apparently just inserting the nvram command won’t help.

Please help?
What I did afterwards was try resetting SMC (tho nothing seemed to have happened regarding the charging light switching color etc), then I reset PRAM and entered the “nvram” code and rebooted.

After that the gray screen with Apple logo appeared and the progress bar moved to cca. 2/3 of the bar then it got stuck. I had to manually shut down my MBP and only after turning it on again did it finally boot into the OS.

Now what can I do to reduce taking all these steps each time I were to reboot or when the battery gets depleted?
 

Eriamjh1138@DAN

macrumors 6502a
Sep 16, 2007
931
1,018
BFE, MI
I've been following this thread for years and trying like hell to understand what's going on and what to do, but based on a tip I saw in this thread, I decided to drop back to El Capitan from Sierra and my 15" 2011 MBP no longer KPs.

I never had any issues until Sierra and only had a problem launching programs like iPhoto, which I know Appel dropped support for, but I still used it. I just wanted everyone to know that if you don't need to have Sierra, stick with El Cap and maybe you'll be one of the few who don't really have a problem.

So far, so good. iPhoto did not crash my MBP!
 

jon08

macrumors 68000
Nov 14, 2008
1,886
105
I’m not sure. I have never used the one on the bottom. I wonder if it will do the same thing?
Apparently it does, yeah... tried it earlier.

How could I make my MBP work after reboot with a simple command or even avoid having to type any commands and let it use the integrated GPU permanently? :/
 

nerowolfe19

macrumors member
Aug 16, 2018
93
34
Apparently it does, yeah... tried it earlier.

How could I make my MBP work after reboot with a simple command or even avoid having to type any commands and let it use the integrated GPU permanently? :/

Try the following after disabling SIP.

1. Open terminal. Enter sudo nvram boot-args="agc=-1" and restart. It causes my machine to lose brightness control but auto-switching is disabled (it's the NVRAM equivalent to the hardware mod in this thread) so set the screen brightness to a desirable level before trying it out. You can reverse it using sudo nvram boot-args="" or zapping the NVRAM.

2. Open terminal. Enter sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-active=%01%00%00%00 and restart. Honestly, I'm not sure if it does anything at all, but it's documented and worth a shot if everything else fails.

3. Give dosdude1's dGPU disabler app a try. Again, I haven't tried it myself, but some have found success with it when other methods have failed.

4. Clean install an earlier OSX. El Cap, Sierra. In that order. Lots of work, but High Sierra and 2011 MBP with failed dGPUs often don't get along all that well.
 

nsgr

macrumors 6502
May 22, 2017
317
117
Apparently it does, yeah... tried it earlier.

How could I make my MBP work after reboot with a simple command or even avoid having to type any commands and let it use the integrated GPU permanently? :/

Yes, they do the same thing. They change to gpu-power-prefs to Intel GPU.
Code:
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
or
Code:
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01

The nvram gpu-power-prefs with GUID (fa4ce ... 30f9) command is written to an EFI chip and not to your HDD/SSD.
Even without a HDD/SSD, the gpu-power-prefs for Intel GPU will remain up and running.

If you are having trouble in Reboot or Power Off in Macbook Pro 2011 by switching to the AMD GPU, then there are two possibilities:

1 - You are using some application that forces the change to the AMD GPU.
2 - You have a problem with the EFI chip that is not holding the new configuration of nvram gpu-power-prefs.

I have tested these two files (reboot.sh and poweroff.sh) and they work.
They basically change the gpu-power-prefs to Intel GPU before reboot or power off the Macbook Pro 2011.

In this example, the reboot.sh and poweroff.sh files will be in the Downloads directory.

Some commands like nvram, reboot and shutdown need to be used with super user privilege. That is why the sudo command is used.


reboot.sh

0 - Finder -> Applications -> Utilities -> Terminal -> change to Downloads directory:
Code:
cd Downloads/


1 - Create reboot.sh file with nano editor:
Code:
sudo nano reboot.sh


2 - Copy and paste this code:
Code:
#!/bin/bash
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01
reboot
exit 0


3 - Save reboot.sh with CTRL+W keys and exit nano editor with CTRL+X keys.


4 - Change attribute reboot.sh to executable file.
Code:
 sudo chmod a+x reboot.sh


5 - To run the executable file reboot.sh and reboot Macbook Pro 2011, then you have to put ./ before the file name (UNIX/Linux system rules).
Code:
sudo ./reboot.sh


poweroff.sh

0 - Finder -> Applications -> Utilities -> Terminal -> change to Downloads directory:
Code:
cd Downloads/


1 - Create poweroff.sh file with nano editor:
Code:
sudo nano poweroff.sh


2 - Copy and paste this code:
Code:
#!/bin/bash
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01
shutdown -h now
exit 0


3 - Save poweroff.sh with CTRL+W keys and exit nano editor with CTRL+X keys.


4 - Change attribute poweroff.sh to executable file.
Code:
 sudo chmod a+x poweroff.sh


5 - To run the executable file poweroff.sh and reboot Macbook Pro 2011, then you have to put ./ before the file name (UNIX/Linux system rules).
Code:
sudo ./poweroff.sh


Update:

Each time you want to restart or power off the Macbook Pro 2011, then you have to run reboot.sh or poweroff.sh through the Terminal app.
 
Last edited:
  • Like
Reactions: Christopfhe

dosdude1

macrumors 68030
Feb 16, 2012
2,771
7,379
Hello all. Just wanted to let you all know that I've found an impeccable, PERMANENT solution to disable the dGPU on one of these 2011 15" or 17" systems! It is quite an involved hardware modification, but is well worth it, as it requires no modifications to OS X, no reliance on NVRAM variables, and will always work, regardless of the OS that you run or updates you install. Details can be found on the thread I started about it. The only things that don't work are the external display port (as it is wired directly to the dGPU), and the display backlight brightness control.
 

mikecwest

macrumors 65816
Jul 7, 2013
1,193
496
Yes, they do the same thing. They change to gpu-power-prefs to Intel GPU.
Code:
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
or
Code:
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01

The nvram gpu-power-prefs with GUID (fa4ce ... 30f9) command is written to an EFI chip and not to your HDD/SSD.
Even without a HDD/SSD, the gpu-power-prefs for Intel GPU will remain up and running.

If you are having trouble in Reboot or Power Off in Macbook Pro 2011 by switching to the AMD GPU, then there are two possibilities:

1 - You are using some application that forces the change to the AMD GPU.
2 - You have a problem with the EFI chip that is not holding the new configuration of nvram gpu-power-prefs.

I have tested these two files (reboot.sh and poweroff.sh) and they work.
They basically change the gpu-power-prefs to Intel GPU before reboot or power off the Macbook Pro 2011.

In this example, the reboot.sh and poweroff.sh files will be in the Downloads directory.

Some commands like nvram, reboot and shutdown need to be used with super user privilege. That is why the sudo command is used.


reboot.sh

0 - Finder -> Applications -> Utilities -> Terminal -> change to Downloads directory:
Code:
cd Downloads/


1 - Create reboot.sh file with nano editor:
Code:
sudo nano reboot.sh


2 - Copy and paste this code:
Code:
#!/bin/bash
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01
reboot
exit 0


3 - Save reboot.sh with CTRL+W keys and exit nano editor with CTRL+X keys.


4 - Change attribute reboot.sh to executable file.
Code:
 sudo chmod a+x reboot.sh


5 - To run the executable file reboot.sh and reboot Macbook Pro 2011, then you have to put ./ before the file name (UNIX/Linux system rules).
Code:
sudo ./reboot.sh


poweroff.sh

0 - Finder -> Applications -> Utilities -> Terminal -> change to Downloads directory:
Code:
cd Downloads/


1 - Create poweroff.sh file with nano editor:
Code:
sudo nano poweroff.sh


2 - Copy and paste this code:
Code:
#!/bin/bash
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01
shutdown -h now
exit 0


3 - Save poweroff.sh with CTRL+W keys and exit nano editor with CTRL+X keys.


4 - Change attribute poweroff.sh to executable file.
Code:
 sudo chmod a+x poweroff.sh


5 - To run the executable file poweroff.sh and reboot Macbook Pro 2011, then you have to put ./ before the file name (UNIX/Linux system rules).
Code:
sudo ./poweroff.sh


Are the scripts supposed to run automatically when you reboot or shut down?
 

nsgr

macrumors 6502
May 22, 2017
317
117
Are the scripts supposed to run automatically when you reboot or shut down?

Each time you want to restart or power off the Macbook Pro 2011, then you have to run reboot.sh or poweroff.sh through the Terminal app.
 

mikecwest

macrumors 65816
Jul 7, 2013
1,193
496
Each time you want to restart or power off the Macbook Pro 2011, then you have to run reboot.sh or poweroff.sh through the Terminal app.

So, its not much different than just running my own "bash roxy" each time that I reboot"
 

Bob B

macrumors newbie
Aug 27, 2018
4
0
Desert Hot Springs, CA
What happens if you connect external display?
I can't get external displays to work with my MBP late 2011. I know this thread is about forcing MBP to use the Integrated GPU because the AMD GPU failed. But both of my cards appear to be working, just won't switch (default) cards when I plug in display (via HDMI to Thunderbolt). MBP doesn't see display at all, but same display and connection/adapter works on a newer MacAir.

Is there anything I can do to get an external display to work while still using the internal GPU?

Thanks much!
 

dosdude1

macrumors 68030
Feb 16, 2012
2,771
7,379
I can't get external displays to work with my MBP late 2011. I know this thread is about forcing MBP to use the Integrated GPU because the AMD GPU failed. But both of my cards appear to be working, just won't switch (default) cards when I plug in display (via HDMI to Thunderbolt). MBP doesn't see display at all, but same display and connection/adapter works on a newer MacAir.

Is there anything I can do to get an external display to work while still using the internal GPU?

Thanks much!
The external display port is wired directly to the dedicated GPU. Dedicated GPU disabled/defective = No external display.
 

Bob B

macrumors newbie
Aug 27, 2018
4
0
Desert Hot Springs, CA
The external display port is wired directly to the dedicated GPU. Dedicated GPU disabled/defective = No external display.
Is there any way to 1) enable or replace the AMD Discrete GPU or 2) use an external GPU?
Would a TB dock like this one allow me to use an external monitor?

Desperately trying to get this to work somehow. Thanks for your help.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.