Update 2017.12.12-14.20 EET: whether or not I use the AMDGPUWakeHandler and whether I sleep or hibernate I can’t wake up of the hibernation/sleep. Depending on if I have AMDGPUWakeHandler on or off I get different outputs, but none of those end in a successful wakeup.
Update 2017.12.13-09.08 EET: After checking about the wake up problem after sleeping / hibernating with the people form MacRumors, I reached some conclusions.
- You don’t use AMDGPUWakeHandler with this solution, since it could create a kernel panic… so for that reason doesn’t work.
pmset gpuswitchoption can help, but it’s really undocumented officially, so we really don’t know what the values for 0, 1 and 2 stand for, and can vary from machine to machine I guess, or at least to macOS version to version.
- gfxCardStatus can help since the problem after wake up is the dGPU activates and the computer freezes.
I’ve updated steps 11 and 12 in consequence.
Update 2017.12.18-14.42 EET: I’ve tried to wake up from hibernation without gxfCardStatus and it worked pretty well I didn’t have any issue, so if you don’t want to have it installed or at least running in the background I think it’s OK.
Update 2018.01.09-21.35 EET: After install the security update to mitigate the effects of Spectre, I have to apply the fix again as explained here. Everything worked fine, but on wake up of hibernation I got a black screen a couple of times. Also the computer didn’t turn off and got stuck in a black screen. I really don’t know what is the reason, but seems it’s related to the
gpuswitch parameter. I changed to 0 and then to 2 again, and seems that everything is normal again. But I don’t know if it’s really that or it’s other thing.
Update 2018.01.21-09.20 EET: I just installed macOS update 10.13.3 and after testing a little bit I got to the conclusion that what work best for me is to set
pmset -a gpuswitch 1
Update 2019.10.20-22.10 EEST: I don’t have this computer anymore, so I’m sorry but probably I’m not going to be able to help you.
Ok!!!!!! There is a third, and I think final, solution to totally deactivate the dGPU. Till this moment this is my favorite solution and I even have the brightness back to my computer. Also it sleeps correctly. You can check my previous post also 1 & 2.
We all have to thank to MacRumors community that all of them have been working really hard to create a workable solution to all of us. This guide is almost a exact copy of the one posted by MikeyN here. I’ve just changed somethings and added the AMDGPUWakeHandler to manage the sleep.
Let’s explain how it’s done:
- As always you have to reset SMC and PRAM/NVRAM before you do anything else.
SMC: shutdown, unplug everything except power, now hold
leftShift + Ctrl + Opt/Alt + Powerfor about 10” and release at the same time.
PRAM/NVRAM: with the power cord on, power on and immediately later and before the chime hold
cmd + Opt/Alt + P + Rat the same time until you hear the chime for the second time. Try to do the following step just right after, so you don’t let the computer to load —and fail.
- SMC: shutdown, unplug everything except power, now hold
Now, boot into recovery single user mode by holding:
cmd + R + S. When finish to load, you run:
1 2 3 4
$ csrutil disable # to disable SIP $ nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00 # to disable the dGPU on boot. $ nvram boot-args="-v" # Load in verbose mode $ reboot
Reboot in single user mode holding on boot
cmd + S
Now we are going to mount the hard drive and move the driver of the dGPU
AMDRadeonX3000.kextout of the drivers folder.
1 2 3 4 5
$ /sbin/mount -uw / # mount root partition writeable $ mkdir -p /System/Library/Extensions-off # make a kext-backup directory $ mv /System/Library/Extensions/AMDRadeonX3000.kext /System/Library/Extensions-off/ # only move ONE offending kext out of the way $ touch /System/Library/Extensions/ # let the system update its kextcache $ reboot
Now you’re going to be able to load your desktop normally, but with an accelerated iGPU display. However, the system doesn’t know how to power-management the failed AMD-chip, so you are going to need to load it manually.
$ sudo kextload /System/Library/Extensions-off/AMDRadeonX3000.kext
You can automate the loading with the doing the following:
$ sudo mkdir -p /Library/LoginHook # Creating a folder to store the script. $ sudo nano /Library/LoginHook/LoadX3000.sh # Creating the script.
On nano you type/paste:
1 2 3 4
#!/bin/bash kextload /System/Library/Extensions-off/AMDRadeonX3000.kext # pmset -a gpuswitch 0 # to prevent to switch to the dGPU exit 0
* I’ve decided to comment the line 3 since I’m not sure that 0 is the correct value. Besides, in the step 12 I set
You make it executable active:
$ sudo chmod a+x /Library/LoginHook/LoadX3000.sh $ sudo defaults write com.apple.loginwindow LoginHook /Library/LoginHook/LoadX3000.sh
This is what I like the most. You create a script in the root of your hard drive to automate the process in case of an update.
$ sudo nano /force-iGPU-boot.sh # Creates the script in the root
With the following content.
1 2 3 4
#/bin/sh sudo nvram boot-args="-v" sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00 exit 0
Now you make it executable and I hide to avoid delete it:
$ sudo chmod a+x /force-iGPU-boot.sh # make ir executable $ sudo chflags hidden /force-iGPU-boot.sh # hide the file.
In the future if you reset SMC and PRAM/NVRAM you just have to load in single user mode holding
cmd + Sand run:
$ sh /force-iGPU-boot.sh
Then, you can copy the AMDGPUWakeHandler, or the one I created AMDGPUWakeHandler.kext, to
/Library/Extensionsand run the following commands:
1 2 3
$ # sudo chmod -R 755 /Library/Extensions/AMDGPUWakeHandler.kext $ # sudo chown -R root:wheel /Library/Extensions/AMDGPUWakeHandler.kext $ # sudo touch /Library/Extensions
This time you don’t need to change the way the machine sleeps. And you can reboot
I recommend you the way the machine sleeps to hibernate, but I haven’t tested if it can sleeps normally after we apply the following step
$ sudo pmset -a hibernatemode 25
All the fuss about the wake up after sleep / hibernate is related to when the computer wake ups checks the GPUs and somehow it gets stuck to dGPU. For that reason some people has changed the variable gpuswitch in pmset. Nevertheless, this variable is really undocumented and you find explanations to what the values to that variable (0, 1 and 2) do on internet.
At this moment I have it set as default 2I’ve decided to change to 1.
$ sudo pmset -a gpuswitch 1
Which I thing it’s the default value.The default value is 2.
You can try the different values, reboot and then close the lid and wake up and see the results.
What has worked for me is leave it in
and install gfxCardStatus, and every time I boot change togfxCardStatus can help, but at least I’m not using it right now. I wake up from hibernation without it perfectly.
integrated only. But still testing. I’ve tried to wake up from hibernation without gfxCardStatus and it also worked, so I guess it’s optional.
After you reboot and if everything goes smoothly, perhaps you wan to return to the normal boot mode. You can room in terminal:
$ sudo nvram boot-args=""
Now I just going to copy paste from MikeyN’s post
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.
In case you have to update
So, before you update the system, please remember to run:
1 $ sudo cp -r /System/Library/Extensions-off/AMDRadeonX3000.kext /System/Library/Extensions/
Then you update. If you can’t normally load your computer, you can hold
cmd + S and run:
1 $ sh /force-iGPU-boot.sh
Then you can reboot again on single user mode holding
cmd + S and then run
1 $ sudo mv /System/Library/Extensions/AMDRadeonX3000.kext /System/Library/Extensions-off/
To move again the kext. Keep in mid that the other one still there do you are going to probably rename it in this fashion:
1 $ sudo mv /System/Library/Extensions/AMDRadeonX3000.kext /System/Library/Extensions-off/AMDRadeonX3000-1.kext
Checking that everything is OK
If you run in terminal
1 $ kextstat | grep AMD
You have to get something similar to this:
1 2 3 4 111 2 0xffffff7f82da8000 0x122000 0x122000 com.apple.kext.AMDLegacySupport (1.6.0) 3BE3756A-6D69-3CD0-B18A-BC844EE2A4DF <105 12 11 7 5 4 3 1> 130 0 0xffffff7f83631000 0x12e000 0x12e000 com.apple.kext.AMD6000Controller (1.6.0) DC45A18B-6F81-38D5-85CB-06BFBD74B524 <111 105 12 11 5 4 3 1> 146 0 0xffffff7f83126000 0x22000 0x22000 com.apple.kext.AMDLegacyFramebuffer (1.6.0) 5F948DD4-8D1E-31BD-A7EE-C44254CBA506 <111 105 12 11 7 5 4 3 1> 174 0 0xffffff7f83ab3000 0x56c000 0x56c000 com.apple.kext.AMDRadeonX3000 (1.6.0) 7E721EBE-AD4B-3C53-A70A-1FFF3C231968 <173 147 105 12 7 5 4 3 1>
In the beginning I wasn’t getting any of these and the system just loaded AMDRadeonX3000. That resulting in a little bit of overheating in the dGPU and I wasn’t able to sleep the computer. The reason for the system to not load the kext was I moved them that much that I changed the ownership of the files. If that is your case you can run in terminal:
1 2 $ sudo chown -R root:wheel /System/Library/Extensions/AMD*.* $ sudo chown -R root:wheel /System/Library/Extensions-off/AMD*.*
to return the ownership to the System / Root
Let’s hope that everything goes smoothly from now on. You have to see the bright side of life, now you have a quite cold running Mac since the dGPU is totally deactivated. After a while your temps have to be something similar to this: