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.

hcgaron

macrumors newbie
Aug 14, 2018
1
0
I have to thank OP for this solution. For the time being, it has allowed me to continue using my computer.

Two things to note, that I read briefly about:

1) Apple apps that use the camera tell me there is no camera connected (FaceTime and Photo Booth). I don't particularly care... but seems noteworthy. Apps like skype are unaffected and the camera works fine.

2) This is more interesting, which is that the AMD Radeon card still seems to switch on at times. Or at least, according to 'About this mac' it seems to come on. I boot to integrated graphics, but when I begin running certain apps it tells me the AMD card is switched on (I go back to 'About this Mac' and the graphics processor has changed). However, the computer is (momentarily) still working. I'm wondering if anyone else has this same experience? Is the AMD card actually switching on or is my OS being fooled?

Thank you for this solution. You've helped a lot of people.

Cheers,

Hanzy
 

nsgr

macrumors 6502
May 22, 2017
317
117
... You have to move the AMDRadeonX3000.kext that is inside the /System/Library/Extensions directory. ...
I've tried that after multiple readings of the above. I know I also read somewhere the solution to the 'Operation not permitted' error.
I tried working with the crsutils file on the recovery partition - but it isn't there.
Can you stand another go at finding my way through this ?
My next trick is to try the actions via the now sluggingly working but totally readable desktop rather than via terminal. I have tried that in the past also, but, I have reset, reuploaded and rechecked so much that there is a chance it will get me yet another small step forward. I am a patient man.

You did not say which version of Mac OS you are using. Before you said that you had the High Sierra Beta and then you said that you would install Mountain Lion.

System Integrity Protection (SIP) is only available on El Capitan, Sierra and High Sierra - csrutil command.

If you are using Mountain Lion, then there is no SIP - csrutil command.


But guess what? Some people upgraded (no fresh/clean install) from an older version (Mountain Lion) to a newer version (High Sierra), and the system was updated but the Recovery Mode partition continued with the old system (Mountain Lion).

Consequence: When you boot from Recovery Mode, you then load a Mountain Lion system that does not have the csrutil command.

https://forums.macrumors.com/threads/disable-sip-command-not-found.1961216/

- - -
When you boot through Recovery Mode, then which icon appears in the Reinstall OS X option?
If it is the icon of Mountain Lion, then you need to do a fresh / clean installation through a USB stick to update all partitions (system and Recovery).

Or try an installation on the Internet and see if the High Sierra icon appears in the Reinstall OS X option.
Option-Command-R or Shift-Option-Command-R at startup.

https://support.apple.com/en-us/HT201314


Mountain Lion icon:
https://forums.macrumors.com/attachments/image-jpeg.621183/

High Sierra icon:
https://support.apple.com/library/c...macos-high-sierra-recovery-mode-reinstall.jpg


Move AMDRadeonX3000.kext with boot Recovery Mode - You do not need to disable SIP - csrutil disable:

You can move AMDRadeonX3000.kext through Recovery Mode. If you are using the APFS file system, then Mountain Lion Recovery Mode may not work.

If the system partition is Mac OS Extended, then the driver for this file system automatically loads itself.


1 - Boot Recovery Mode (Command + R at boot).


2 - After show graphical screen, choose Disk Utility.


3 - See if your System Partition is mounted (mount point). And see the name of System Partition.
Example: label Macintosh HD or MacOS.

If the system partition is not mounted, then click on the partition name and then click Mount.

If your system partition is encrypted (FileVault), then this partition is not mounted automatically because you need to enter the partition password.


4 - Close Disk Utility, click menu Utilities Terminal.


5 - Check the names of partitions mounted with the ls command.
Code:
ls /Volumes


6 - If the name of your system partition has spaces, then use the TAB key to autocomplete the name. Otherwise you may have the answer: "No such file or directory".

Example list files and directories with ls command:
Code:
ls /Volumes/Macintosh HD
ls: HD: No such file or directory
ls: Macintosh: No such file or directory

Code:
ls /Volumes/Macintosh\ HD/
Applications            Users                etc                sbin
DisableExtensions        Volumes                home                tmp
Library                bin                installer.failurerequests    usr
Network                cores                net                var
System                dev                private


7 - Create directory to move AMDRadeonX3000.kext. The MikeyN Guide - #875 - example will be used.
Code:
mkdir -pv /Volumes/Macintosh\ HD/System/Library/Extensions-off


8 - Move AMDRadeonX3000.kext from /System/Library/Extensions to /System/Library/Extensions-off .
Code:
mv -v /System/Library/Extensions/AMDRadeonX3000.kext /System/Library/Extensions-off/


9 - Close Terminal:
Code:
exit


10 - Unmount system partition with Disk Utility.


11 - Restart the Macbook Pro -> Apple logo left up corner -> Restart


12 - Boot in Single User Mode (Command + S at boot) and rebuild cache:


12.2 - Verify system file integrity with fsck command:
Code:
fsck -fy


12.3 - Mount system partition with Read and Write flag. Do not forget final Slash ( / ) after -uw. Otherwise you may have the message Operation not permitted.

Code:
mount -uw /


12.4 - Use touch command to change time stamp and force rebuild cache.
Code:
touch /System/Library/Extensions/


12.5 - Wait 2 minutes, and then restart the system.
Code:
reboot


13 - Mac OS rebuild cache and show login screen.

For Power Off AMD GPU with faulty chip, manually load the AMDRadeonX3000.kext with the kextload command or the kextutil command.

The kextutil command provides more information when loading a kext. If you have a kext problem not being loaded by the kextload command, then use the kextutil command to know the reason for the error when trying to load kext.

Code:
kextload /System/Library/Extensions-off/AMDRadeonX3000.kext

or

Code:
kextutil /System/Library/Extensions-off/AMDRadeonX3000.kext


To automate the process, follow the MikeyN Guide - #875 - LoginHook.

Remember that with each update, a new AMDRadeonX3000.kext will be placed inside the /System/Library/Extensions -> and will freeze the Macbook Pro again on the grey screen.

If after the update, the Macbook Pro does not freeze on the gray screen, so probably not an update of the kexts or the team of Apple developers put an AMDRadeonX3000.kext incomplete.

The most common is not having the Info.plist file.
AMDRadeonX3000.kext/Contents/Info.plist

This AMDRadeonX3000.kext will not be loaded by kextload or kextutil because it does not have Info.plist
So it's always nice to have a full AMDRadeonX3000.kext backup.

If you have a complete AMDRadeonX3000.kext inside /System/Library/Extensions-off/, then the system will work normally with the manual loading of kextload, kextutil or LoginHook.


Follow:

MikeyN Guide deacrese AMD GPU - System temperature - Page 35 - #875

Rename old AMDRadeonX3000.kext - move new AMDRadeonX3000.kext after update - Page 57 - #1425

Shutdown-Restart Macbook-black screen-Page 57-#1425 / Close Lid-Sleep-Wake Pages 43-50 #1066 #1243
 
Last edited:

nsgr

macrumors 6502
May 22, 2017
317
117
please help me.

I've done all the steps. But sometimes(not always) when my macbook pro 2011 wakes from sleep, it will reboot.
What I found from the system crash log is below:
===========================================
Anonymous UUID: 78A24FE3-35B4-E388-A981-61269F7CB666

Tue Aug 14 16:30:22 2018

*** Panic Report ***
panic(cpu 6 caller 0xffffff7fb01b58d7): "GPU Panic: mux-regs 2 0 1 0 0 0 severity 3 WS-ready 1 switch-state 0 IG FBs 1 EG FBs 0:0 power-state 6 3D idle HDA idle system-state 1 power-level 20:20 connect-change 0 : UH eHlPH
E0L H(L @ H HH
: GPU is not found. PCI config access fails!!!
============================================
What should I do?


GPU is not found. PCI config access fails!!! ---> Macbook Pro 2011 -> AMD6000Controller.kext

Code:
grep -iRl "GPU is not found" /System/Library/Extensions/

/System/Library/Extensions/AMD6000Controller.kext/Contents/MacOS/AMD6000Controller
/System/Library/Extensions/AMD7000Controller.kext/Contents/MacOS/AMD7000Controller
/System/Library/Extensions/AMD5000Controller.kext/Contents/MacOS/AMD5000Controller
/System/Library/Extensions/AMD8000Controller.kext/Contents/MacOS/AMD8000Controller
/System/Library/Extensions/AMD9000Controller.kext/Contents/MacOS/AMD9000Controller
/System/Library/Extensions/AMD9500Controller.kext/Contents/MacOS/AMD9500Controller
/System/Library/Extensions/AMD10000Controller.kext/Contents/MacOS/AMD10000Controller

Code:
 grep -iRl "PCI config access fails" /System/Library/Extensions/

/System/Library/Extensions/AMD6000Controller.kext/Contents/MacOS/AMD6000Controller
/System/Library/Extensions/AMD7000Controller.kext/Contents/MacOS/AMD7000Controller
/System/Library/Extensions/AMD5000Controller.kext/Contents/MacOS/AMD5000Controller
/System/Library/Extensions/AMD8000Controller.kext/Contents/MacOS/AMD8000Controller
/System/Library/Extensions/AMD9000Controller.kext/Contents/MacOS/AMD9000Controller
/System/Library/Extensions/AMD9500Controller.kext/Contents/MacOS/AMD9500Controller
/System/Library/Extensions/AMD10000Controller.kext/Contents/MacOS/AMD10000Controller


You may have to test the pmset command for gpuswitch.
Close Lid-Sleep-Wake Pages 43-50 #1066


Or test GRUB Solution to isolate the load of the AMD6000Controller.kext.

https://forums.macrumors.com/thread...-on-a-2011-macbook-pro-grub-solution.2087527/

https://gist.github.com/blackgate/17ac402e35d2f7e0f1c9708db3dc7a44


Other links:

GPU Panic: mux-regs after sleep mode
https://discussions.apple.com/thread/8159576


kernel panic GPU not found
https://discussions.apple.com/thread/6658206



Follow:

MikeyN Guide deacrese AMD GPU - System temperature - Page 35 - #875

Rename old AMDRadeonX3000.kext - move new AMDRadeonX3000.kext after update - Page 57 - #1425

Shutdown-Restart Macbook-black screen-Page 57-#1425 / Close Lid-Sleep-Wake Pages 43-50 #1066 #1243


Update:

I have only these AMD kexts inside the /System/Library/Extensions - for precaution:
AMD6000Controller.kext
AMDLegacyFramebuffer.kext
AMDLegacySupport.kext
 
Last edited:

Ken DL

macrumors newbie
Aug 14, 2018
15
1
Georgia
I want to share my experience and ask a question. I followed @AppleMacFinder 's instructions using Mac OS only, not the Unix boot. It disabled the GPU but it didn't persist past reboots. At least I knew the machine would run. I then followed @MikeyN 's guide at post #875 and it is working like a charm. Thanks to both of you for sharing your knowledge!

Now my question: Is the command 'nvram boot-args="-v"' essential? It seems as if this just makes the boot process visible in detail, but it's not part of the fix. Will the fix work without it? If so, how do I set boot-args back to it's default?
 

KiDo

macrumors member
Oct 3, 2006
59
3
Amsterdam, Netherlands
So I have a late 2011 macbook pro 15" with a 6750 AMD card inside. Logic board has already been replaced once under the repair program, but problems are occuring now again. Macbook is running latest official High Sierra version.

I have used Gfxcardstatus for a while, but it doesn't seem to work anymore as when I open certain apps the mac just crashes with the known video tearing etc.

I have tried following the steps to completely disable the GPU, but I think something is not working as intended. I made a bootable USB for the linux distro, but starting that with nomodeset doesnt work, and when I load the linux the notebook still uses its discrete card and stops working before i can enter all the commands.

I found the workaround involving entering sudo nvram in single user mode, did that but didnt see anything happen.

Now I removed the kext files as instructed, and upon rebooting it uses the discrete card by default, and gfxcardstatus cannot switch to internal cause it says I'm using an external screen. (I already found this is caused by me removing the drivers, but I can't seem to get it back in order now.

Is there anyone here with knowledge/knowhow on how to fix what I broke, and maybe finish the job of disabling the GPU properly? Thanks in advance, the machine is not working properly at all now..


EDIT: I did some more reading, apparantly I didn't do the nvram bootargs -v thing at SU mode, just did the SU mode commands again and now the notebook launches very quickly and I cant seem to switch to dedicated now. It appears to be working.

I manually moved over the kexts from the backup folder back into extensions, that didnt fix anything I broke so I don't know if I have to delete them again now?
 
Last edited:

Ken DL

macrumors newbie
Aug 14, 2018
15
1
Georgia
So I have a late 2011 macbook pro 15" with a 6750 AMD card inside. Logic board has already been replaced once under the repair program, but problems are occuring now again. Macbook is running latest official High Sierra version.

I have used Gfxcardstatus for a while, but it doesn't seem to work anymore as when I open certain apps the mac just crashes with the known video tearing etc.

I have tried following the steps to completely disable the GPU, but I think something is not working as intended. I made a bootable USB for the linux distro, but starting that with nomodeset doesnt work, and when I load the linux the notebook still uses its discrete card and stops working before i can enter all the commands.

I found the workaround involving entering sudo nvram in single user mode, did that but didnt see anything happen.

Now I removed the kext files as instructed, and upon rebooting it uses the discrete card by default, and gfxcardstatus cannot switch to internal cause it says I'm using an external screen. (I already found this is caused by me removing the drivers, but I can't seem to get it back in order now.

Is there anyone here with knowledge/knowhow on how to fix what I broke, and maybe finish the job of disabling the GPU properly? Thanks in advance, the machine is not working properly at all now..


EDIT: I did some more reading, apparantly I didn't do the nvram bootargs -v thing at SU mode, just did the SU mode commands again and now the notebook launches very quickly and I cant seem to switch to dedicated now. It appears to be working.

I manually moved over the kexts from the backup folder back into extensions, that didnt fix anything I broke so I don't know if I have to delete them again now?

I would follow MikeyN's procedure exactly as specified in #875. I'm on day 2 and it's working through various sleep/wake/power down/let-battery-drain cycles. Start at the beginning.
 
  • Like
Reactions: pckrullenbol

nsgr

macrumors 6502
May 22, 2017
317
117
I want to share my experience and ask a question. I followed @AppleMacFinder 's instructions using Mac OS only, not the Unix boot. It disabled the GPU but it didn't persist past reboots. At least I knew the machine would run. I then followed @MikeyN 's guide at post #875 and it is working like a charm. Thanks to both of you for sharing your knowledge!

Now my question: Is the command 'nvram boot-args="-v"' essential? It seems as if this just makes the boot process visible in detail, but it's not part of the fix. Will the fix work without it? If so, how do I set boot-args back to it's default?

The boot-args "-v" is only to see the boot in verbose mode. It does not affect the gpu-power-prefs.

To undo/delete boot-args="-v" -----> boot screen change to Apple Logo and Apple progress bar.
Code:
nvram -d boot-args

or

Code:
sudo nvram -d boot-args
 
  • Like
Reactions: pckrullenbol

nerowolfe19

macrumors member
Aug 16, 2018
93
34
My 2012 15" rMBP has a dead nvidia gpu, and by dead I mean it takes no more than a fraction of a second before the screen goes pitch black on boot.

What fixed the problem in my case was unplugging the battery and then pressing the power button while connecting the magsafe to the power port. This causes the computer to work long enough for me to open terminal and type in the nvram string mentioned and the restart the machine.

I then removed all kexts starting with geforce* and nv*, rebuild cache and all was set

I found that agc=-1 negates the need for removing kexts, but it does mess up screen brightness controls so it was a no-go and I removed it

My machine is fine as it is. Sleep/wake/controls/power are all good. Only potential downside is hdmi not working, but I rarely use it if at all.
 

cristian.calin

macrumors newbie
Nov 27, 2013
17
0
Hi there and huge thanks to @AppleMacFinder for sharing his findings with the community.

I have successfully used the method posted at the beginning of the thread to switch to integrated GPU.

I want to do a fresh install of El Capitan, and redo the procedure, because the install was very old with lots of software and tweaks. How can I safely reinstall El Capitan with a dead discrete GPU? When I tried to entered in Internet Recovery, I got an white screen, before doing this procedure.

Is it safe to follow the normal steps of reinstalling El Capitan?

Thank you again, great community.

Edit: I can enter Internet Recovery after applying the GPU fix, but it is safe to format the drive and follow the normal procedure? Or the white screen will come back immediately I format the drive?
anybody can please point me in the right direction about how to reinstall the OS with a dead discrete GPU?

I tried using search on this topic, but my "google fu" is weak apparently.
 

nerowolfe19

macrumors member
Aug 16, 2018
93
34
anybody can please point me in the right direction about how to reinstall the OS with a dead discrete GPU?

I tried using search on this topic, but my "google fu" is weak apparently.

You should be fine as long as you don't zap the nvram. You'll have to re-do all non-nvram related steps I reckon.

I'd make a bootable clone of the HD using carbon copy cloner just in case.
 

jon08

macrumors 68000
Nov 14, 2008
1,886
105
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!
Many thanks for the write-up. After executing the initial procedure, your suggestion works but seemingly only until I reboot my MBP. Then upon reboot I get stuck on the gray screen.

Is there a way to make it work even when you reboot?
 

mikecwest

macrumors 65816
Jul 7, 2013
1,193
496
Many thanks for the write-up. After executing the initial procedure, your suggestion works but seemingly only until I reboot my MBP. Then upon reboot I get stuck on the gray screen.

Is there a way to make it work even when you reboot?

if you get the grey screen, you can reboot into single user mode by pressing CMD S at start up.....

once you get to the prompt you can type:

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

press enter

type:

reboot


I know it’s a P.I.T.A, but it works.......I avoid reboots whenever I can...
 

jon08

macrumors 68000
Nov 14, 2008
1,886
105
if you get the grey screen, you can reboot into single user mode by pressing CMD S at start up.....

once you get to the prompt you can type:

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

press enter

type:

reboot


I know it’s a P.I.T.A, but it works.......I avoid reboots whenever I can...
This doesn’t seem to help - now I get a gray screen with Apple logo and a progress bar that won’t budge, as opposed to a blank gray screen from before... Please advise?
 

jon08

macrumors 68000
Nov 14, 2008
1,886
105
This doesn’t seem to help - now I get a gray screen with Apple logo and a progress bar that won’t budge, as opposed to a blank gray screen from before... Please advise?
I cannot even get it to work anymore... it keeps getting stuck at gray screen now. :(

Is there a way to reset all that code from the above??
 

Zom

macrumors newbie
Aug 20, 2018
2
0
Thank you so much for this, I just made my sisters MacBook Pro usable again.
 

jon08

macrumors 68000
Nov 14, 2008
1,886
105
I cannot even get it to work anymore... it keeps getting stuck at gray screen now. :(

Is there a way to reset all that code from the above??
I really don't understand how this "hack" really works.. Just now I tried turning on my MBP again and after like 30 secs of it running through the single-mode commands by itself it booted normally into the system and now I'm able to use it again.

However, I'm afraid that upon restart I'll have trouble again.

How can I make this thing work even on restart??
 

JMVB

macrumors regular
May 16, 2016
186
51
After spend about 1 hour, I figure out the procedure, I have a success!!

Thank you!!

I tried to do the fix in a second MBP 15 2011, but no joy

I had the "operation not permitted" error while attempting to rm, even with the:

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

Then I tried to use chattr command to disable file immutability and then erase the file:chattr -i "gpu-power-prefs-…”, but get a "quote" command before every line that I tried to write

The difference, this one have El Capitan instead Yosemite and I Just realize that didn't remove the kext before the fix like the last time

Finally, bought the Realmacmods "Automated Utility" and I succeeded.

I removed the R8911 also
 

mikecwest

macrumors 65816
Jul 7, 2013
1,193
496
I cannot even get it to work anymore... it keeps getting stuck at gray screen now. :(

Is there a way to reset all that code from the above??

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]
I tried to do the fix in a second MBP 15 2011, but no joy

I had the "operation not permitted" error while attempting to rm, even with the:

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

Then I tried to use chattr command to disable file immutability and then erase the file:chattr -i "gpu-power-prefs-…”, but get a "quote" command before every line that I tried to write

The difference, this one have El Capitan instead Yosemite and I Just realize that didn't remove the kext before the fix like the last time

Finally, bought the Realmacmods "Automated Utility" and I succeeded.

I removed the R8911 also
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....
 
Last edited:

JMVB

macrumors regular
May 16, 2016
186
51
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....

So, which procedure is better and which one is long term solution? the Archlinux or the Single User one?
 
Last edited:

nerowolfe19

macrumors member
Aug 16, 2018
93
34
I really don't understand how this "hack" really works.. Just now I tried turning on my MBP again and after like 30 secs of it running through the single-mode commands by itself it booted normally into the system and now I'm able to use it again.

However, I'm afraid that upon restart I'll have trouble again.

How can I make this thing work even on restart??

I really have no idea why the nvram string works so well on my 2012 rMBP but not on those 2011 machines. Literally all I have to do is disable SIP and enter the NVRAM string and it's a perfectly fuctioning device unless I manually reset the NVRAM. It never reverts back to dGPU on its own. Heck, I've even realized I don't have to move any kexts and can safely enable SIP back again, it's all superfluous once the computer boots using the igpu. One of many reasons I'm sticking with Sierra until I buy a new machine.

Come to think of it, I'd test entering the nvram commaned using terminal before restarting and see if it fixes the problem, provided SIP is already disabled using "csrutil disable" in recovery mode ofcourse. Be sure to add "sudo" and enter password when prompted if pw-protected.

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

jon08

macrumors 68000
Nov 14, 2008
1,886
105
I really have no idea why the nvram string works so well on my 2012 rMBP but not on those 2011 machines. Literally all I have to do is disable SIP and enter the NVRAM string and it's a perfectly fuctioning device unless I manually reset the NVRAM. It never reverts back to dGPU on its own. Heck, I've even realized I don't have to move any kexts and can safely enable SIP back again, it's all superfluous once the computer boots using the igpu. One of many reasons I'm sticking with Sierra until I buy a new machine.

Come to think of it, I'd test entering the nvram commaned using terminal before restarting and see if it fixes the problem, provided SIP is already disabled using "csrutil disable" in recovery mode ofcourse. Be sure to add "sudo" and enter password when prompted if pw-protected.

sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
Hm, I think each time I enter the “csrutil disable” command in single usef mode it says something like that it’s only possible to do it in recovery mode - even if I boot into cmd+s+r, which is supposedly recovery mode?
 

nerowolfe19

macrumors member
Aug 16, 2018
93
34
If you're running high-sierra I think there's an update that's removed single-user recovery mode, 10.13.6 if what I've read's accurate. Anyway, if you type "csrutil status" and it says it's disable then you can go ahead and test the sudo nvram and restart method.
 

mikecwest

macrumors 65816
Jul 7, 2013
1,193
496
So, which procedure is better and which one is long term solution? the Archlinux or the Single User one?

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.
 

JMVB

macrumors regular
May 16, 2016
186
51
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.


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
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.