Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

2011 MacBook Pro and Discrete Graphics Card

I have an early 2011 MacBook Pro (2.2 GHz Intel Core i7, 8 GB 1333 MHz DDR3 memory) running OS 10.8.2. It has two graphics components: an AMD Radeon HD 6750M and a built-in Intel HD Graphics 3000. Since I've had the computer, the screen would get a blue tint when the computer switched between them.


However, as of two days ago, the problem has become substantially more severe. The computer was working fine, when all of a suddent the screen when completely blue. I had to force restart the computer. Since then, the screen has gone awry on numerous occassions - each time necessitating a hard reset.


I installed gfxCardStatus, and have discovered that the computer runs fine using the integrated card, but as soon as I switch to the discrete card - the screen goes .


I am just wondering what my options are (any input on any of these would be appreciated!):


1) Replace the logic board. Would this necessarily fix the issue?


2) Is there any way to "fix" the graphics card?


3) Keep using gfxCardStatus and only use the integrated graphics card. This is definitely the easiest/cheapest option, but to have such a computer and not be able to use the graphics card seems like a real shame.


4) Is there any other alternative?


MacBook Pro, OS X Mountain Lion (10.8.2), 2.2 GHz Intel Core i7, 8 GB memory

Posted on Feb 1, 2013 4:45 PM

Reply
13,550 replies

Oct 6, 2016 12:53 PM in response to abelliveau

i had the same problem last year when I made an update to mavericks to yosemite ..


I made the cheaper method as said above, they re-sold the ATI processor, I could use the mac for 2 days after crash the video again, when i was going to use Photoshop again.


I Send to Apple and expand more the 1.700,00 USD to put a new logic board.

Now I made the Sierra update and again problems with the graphic ATI RADEON.





My config:


MacBook Pro (17-inch, Late 2011)

Processor: 2.4 GHz Intel Core i7

Memory: 16 GB 1600 MHz DDR3

Startup Disk: MAC OSX 120 GB Solid State SATA Drive


AMD Radeon HD 6770M:



Chipset Model: AMD Radeon HD 6770M

Type: GPU

Bus: PCIe

PCIe Lane Width: x8

VRAM (Total): 1024 MB

Vendor: ATI (0x1002)

Device ID: 0x6740

Revision ID: 0x0000

ROM Revision: 113-C0170L-573

gMux Version: 1.9.24

EFI Driver Version: 01.00.57

Oct 7, 2016 11:56 PM in response to 5 string

That's good news, although the fact you were initially given excuses is pretty bad. They probably reset your password to gain root access to run some tests. I always create a 'test_repair' account that has full admin right, so they don't have to touch my accounts, but I wouldn't worry about it.

Oct 16, 2016 5:23 PM in response to abelliveau

I've resolved this problem…after reading loads and loads of other threads. It was a problem with the dedicated AMD GPU. The solution was to force the computer to use the Intel graphics processor rather than the dedicated AMD graphics processor. I can't tell exactly why my AMD processor stopped working but from what others have said it appears the problem could lie with the lead free solder used to attach the AMD processor to the motherboard i.e. it wasn't ideal and tends to fail.


The solution that worked for me, and it appears that different people with roughly the same problem have found slightly different solutions, was to move the AMD AND ATI processor extensions out of the System/Library/Extensions folder and place them in a newly created DisabledExtensions folder. This is done using the Single User mode (with your computer off, hold the command and s buttons and press the power key to turn the computer on. You have to be very careful doing this because you're editing code and to would be easy to screw things up.


The discovery I made, which made my particular solution work, was that apparently identical MacBook Pros (Early 2011) can use different AMD processors. So the first solution I found, which looked to be perfect for me, wasn't because I didn't have the exactly the same extensions - the solution required me to type in four named extension.


On first try I managed to progress as far as the instruction which asked for the extensions to be moved, but I got a response saying "file does not exist". On further investigation I found another thread which suggested using a slightly different command which moved any extensions which started with AMD, but didn't need to precise extension name.


To put this all into context, my MacBook Pro is as follows:


MackBook Pro 15" Early 2001

Processor 2 GHz Intel Core i7

AMD Radeon HD 6490M 256 MB

Serial Number beginning: C02F…...


The first set of instructions I found was a YouTube video here:


https://www.youtube.com/watch?v=iyDu-Y_G1D8


This contained the following Single User mode instructions:


fsck -fy [once this file check has run and come back saying "The volume Mac HD appears to be OK" move to the next instruction]

mount -uw / [return]

mkdir /DisabledExtensions [return - this creates the folder the extensions will be placed in]

cd /System/Library/Extensions [return - this takes you to where the extensions to me moved reside]


The next command is were is stopped working for me. The next command wants to move specific named extensions, which I clearly didn't have in my Extensions folder. This fix I found was, as stated above, in a command which simply moves all extensions starting with AMD. This fix is here:


2011 MacBook Pro and Discrete Graphics Card


The next command I used was:


sudo mv AMD* / DisabledExtensions/ [return]


However, there's a bit of a contentious issue in the Discussion Forum page listed above. There are some post saying that you have to move the AMD extensions AND the ATI extensions. There are also some posts rubbishing this, saying that you don't need to move the ATI extensions. I certainly needed to move the ATI extensions, because I got to the end of the original instructions - which I'll detail below - rebooted and it hadn't fixed the problem.


So I found another web page which listed the precise extensions that needed to be moved for my particular AMD Radeon HD 6490M processor, and it listed the ATI extensions. So I went back in to Single User mode and added:


sudo mv ATI* / DisabledExtensions/ [return]


I then came back out with the remaining commands from the original video instructions:


cd /

sudo touch /System/Library/Extensions

ls /DisabledExtensions [return - this lists the moved extensions but it's l as in lima, not a cap i:]

reboot


And it worked. As various people have stated, this is a workaround and not a fix. You're now using the onboard graphics processor, which is OK but doesn't run video very well at all, has trouble with certain web pages and means you can't adjust the screen brightness. And you can't use an external monitor…although I haven't been able to verify this.


So if, like me,you have an AMD Radeon HD 6490M processor, try this in Single User mode:


fsck -fy [once this file check has run and come back saying "The volume Mac HD appears to be OK" move to the next instruction]

mount -uw / [return]

mkdir /DisabledExtensions [return - this creates the folder the extensions will be placed in]

cd /System/Library/Extensions [return - this takes you to where the extensions to me moved reside]

sudo mv AMD* / DisabledExtensions/ [return]

sudo mv ATI* / DisabledExtensions/ [return]

cd /

sudo touch /System/Library/Extensions

ls /DisabledExtensions [return - this lists the moved extensions but it's l as in lima, not a cap i:]

reboot


I hope this helps. I'm off to the local Apple store now to see if I can get a permeant fix under Apple's MacBook Pro Early 2011 AMD Replacement programme.


Regards

Oct 16, 2016 11:07 PM in response to Mr Badger

Like you stated yourself, that does not fix the problem but is merely a workaround. And no, the internal GPU will not let you use an external display. With graphics intensive programs your mileage may vary as well. So this is just a temporary workaround.

And you can use gfxCardStatus ( https://gfx.io/ ) to achieve this as well without resorting to the command line, should the computer be in a usable condition.

Oct 17, 2016 4:31 AM in response to Mr Badger

Thanks for your advice, but I believe the forward slash is not the cause of the "Operation not allowed" problem. I've found the trick from another guy of using "csrutil disable" in Recovery Mode to make this operation possible. However, the problem is, when I trigger the Recovery Mode and have seen a little globe turning for a while, the screen turns into pale grey and gets frozen since then. What a wonderful world.

Oct 17, 2016 11:10 AM in response to abelliveau

I've had my macbook's logic board replaced twice and I started to suspect that it's beginning to fail again. I tried running one of the benchmarking programs and this is what it looks like:


http://imgur.com/a/wd5Wv


Outside of that my graphics seem to be working fine. But since that's how my graphics look while running the program, does that mean that there are issues with my GPU? Would I be able to show this to the Genius bar or does it have to actually be an issue with the system and not the benchmarking tool?


Thanks

Nov 8, 2016 3:49 AM in response to Kanimies

Kanimies, I subsequently tested the external display and you're right, you can't run one. I did look at the gfxCardStatus solution, the trouble is I couldn't boot up the lapdog to download the application and run it, so the command line solution was the only one available to me. If your lapdog is showing early signs of the problem and you can still boot it up, then I agree gfxCardStatus is a far easier solution.

2011 MacBook Pro and Discrete Graphics Card

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.