It all started when my MacBook Pro showed me black screen after waking from sleep. After that, many times I would boot straight into Black Screen, and the only sign that the machine was awake could be just tested by pressing the CAPS LOCK key (turns on the button-light) or connecting an External USB with a indicator light.
I started asking myself why would this happen? Was it due to upgrade to High Sierra 10.13.3 or was it that my machine really developed some hardware problem? I asked a friend of mine what can I do and he suggested SMC Reset followed by PRAM (NVRAM) Reset. I tried all that, but it refused to work. I got my MacBook cleaned and then it booted fine. But as soon as, I started using it, all of a sudden it would show a Black Screen, but CAPS LOCK would still glow green and so I would then reboot it again, only to Black screen. Sometimes, upon restarting the first problem message that I got was GPU panic like the one shown below:
Anonymous UUID: 32BD6DA8-14C2-38AD-E466-F3B6DDCE6F7F Fri May 18 19:43:24 2018 *** Panic Report *** panic(cpu 2 caller 0xffffff7f916c29cf): "GPU Panic: mux-regs 4 0 a0 99 0 8 severity 3 WS-ready 1 switch-state 3 IG FBs 1 EG FBs 0:0 power-state 3 3D idle HDA idle : AGC GPU REGISTER RESTORE FAILED : rdar://7254528, VendorID invalid\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleGraphicsControl/AppleGraphicsControl-3.18.48/src/AppleMuxControl/kext/GPUPanic.cpp:162 Backtrace (CPU 2), Frame : Return Address 0xffffff81f9073a90 : 0xffffff800e66e166 0xffffff81f9073ae0 : 0xffffff800e796714 0xffffff81f9073b20 : 0xffffff800e788a00 0xffffff81f9073ba0 : 0xffffff800e620180 0xffffff81f9073bc0 : 0xffffff800e66dbdc 0xffffff81f9073cf0 : 0xffffff800e66d99c 0xffffff81f9073d50 : 0xffffff7f916c29cf 0xffffff81f9073db0 : 0xffffff7f916bf1ae 0xffffff81f9073df0 : 0xffffff7f916c2443 0xffffff81f9073e30 : 0xffffff800ec9f71c 0xffffff81f9073ea0 : 0xffffff800ec9f646 0xffffff81f9073ed0 : 0xffffff800e6a77e4 0xffffff81f9073f40 : 0xffffff800e6a7345 0xffffff81f9073fa0 : 0xffffff800e61f4f7 Kernel Extensions in backtrace: com.apple.driver.AppleMuxControl(3.18.48)[09DFEF11-0A5B-369B-91C5-FD32B3E62DD3]@0xffffff7f916b4000->0xffffff7f916c6fff dependency: com.apple.driver.AppleGraphicsControl(3.18.48)[91D747FB-F341-33F2-BBDD-0CA45A3CC1B2]@0xffffff7f916b1000 dependency: com.apple.iokit.IOACPIFamily(1.4)[95DA39BB-7C39-3742-A2E5-86C555E21D67]@0xffffff7f8f35a000 dependency: com.apple.iokit.IOPCIFamily(2.9)[1850E7DA-E707-3027-A3AA-637C80B57219]@0xffffff7f8ef34000 dependency: com.apple.iokit.IOGraphicsFamily(519.15)[D5F2A20D-CAB0-33B2-91B9-E8755DFC34CB]@0xffffff7f8fdb3000 dependency: com.apple.AppleGraphicsDeviceControl(3.18.48)[89491182-0B41-3BC3-B16F-D5043425D66F]@0xffffff7f91219000 BSD process name corresponding to current thread: kernel_task ----
So, I started Googling for this GPU Panic problem and found that many laptops had this issue and that many forums said it was all due to a faulty discrete GPU on the logic board. I missed the replacement program (as I was not even aware that it existed until I hit this problem) and now my machine is out of warranty (more than 51/2 years now). The machine is a 15″ MBP 10,1 (mid-2012) with dual GPU system. I thought, if I could get Logic board changed, I should be okay, but in many forums many users who got that done were not still immune from that problem. It had all the possibilities of appearing once more (even after changed GPU). Secondly, Logic board replacement is an expensive affair! Last option, of course, is to get a new MPB, but I wanted to wait till the WWDC June 2018 announcement.
Anyways, I still wanted to make sure that this is indeed the same GPU problem that I was facing. So, I thought may be I should downgrade the OS X to El Capitan or Sierra and rule out my High Sierra upgrade. After checking with both the older OS X, I started getting very frequent GPU panics, like the one pasted above. With laptop in comatose mode 😉 I literally had to resuscitate it using SHIFT + OPT + COMMAND + Power (SMC reset) by counting 10 and then do a CMD+OPT+R+P+POWER (NVRAM Reset) and the wait for sometime and power up again. It all then depended on the spirit to re-enter the machine and bring it to life again :)) Many times, it had barely woken up and slipped into coma again. Then sometimes it would work for 2/3 days straight, until I don’t open up any BIG IDEs like Intellij or any program like Chrome or Firefox that caused a switch to dGPU.
In the Apple forums, I saw people had already disabled the on-board dGPU and they had a working system with only the built-in iGPU. However, it was done for older makes (year 2011) of the MBP. I searched for my particular make with NVIDIA GeForce GT650M Graphics card. I stumbled upon 2 links:
1) https://github.com/mayankk2308/purge-nvda/blob/master/purge-nvda.sh (NVIDIA driver)
2) http://www.javajirawat.com/2018/02/macbook-pro-2012-broken-gpu-work-around.html (AMD driver)
Thanks to them and I combined both their solutions to disable the dGPU on my system.
The Steps:
-
- You can either go to Apple Menu > About This Mac… > Overview Tab > Press System Report…Under Hardware, look for Graphics/Displays…
- Or you can type at terminal (and it displays the same information)
$ system_profiler SPDisplaysDataType Built-In GPU (Integrated GPU - iGPU): Intel HD Graphics 4000 1536 MB ... ... Second GPU (Discrete GPU - dGPU): NVIDIA GeForce GT 650M gMux Version: 3.2.19 [3.2.8] ... ... Display - Color LCD Resolution - 2880 x 1800 Retina Framebuffer Depth: 24-Bit Color (ARGB8888) Metal: Supported, feature set macOS GPUFamily1 v3
- Boot into Recovery Mode (by holding Command+R while pressing the power button). At terminal prompt, we will disable SIP (System Integrity Protection)
$ csrutil disable System Integrity Protection now disabled.
- Reboot again in Single User mode.
$ reboot $ # and then hold Command+S keyboard buttons $ # to boot in single user mode.
- Do a Hard disk Check:
$ /sbin/fsck -fy $
- Mount Root file system in Read-Write (uw) mode:
$ /sbin/mount -uw / $
- Create a backup directory to hold existing GeForce drivers:
$ mkdir /GeForce_save $
- Move all the GeForce drivers to the backup directory:
$ mv /System/Library/Extensions/GeForce* /GeForce_save $
- Delete Driver Cache
$ rm -rf /System/Library/Caches/com.apple.kext.caches/ $
- Force refresh of Driver cache:
$ touch /System/Library/Extensions $ kextcache -q -update-volume / $
- Reboot again (into Recovery mode while holding Command+R)
$ reboot
- Remove Nvda Booting GPU
$ nvram boot-args="nv_disable=1" # OR append existing boot-args $ nvram boot-args="nv_disable=1 $(nvram boot-args 2>/dev/null | cut -f 2-)" $ nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00 $
- Enable SIP (System Integrity Protection)
$ csrutil enable System Integrity Protection now enabled.
- Reboot machine in normal mode
$ reboot
I. Sanity Check (find the number of GPUs):
II. In Recovery Mode, do the following (Using the Recovery Terminal Utility), do the following:
III. In Single User Mode, do the following:
IV. In Recovery Mode, do the following (Using the Recovery Terminal Utility):
IMPORTANT NOTE:
- By using nvram boot-args=”nv_disable=1″, you will lose brightness control (F1/F2 keys) and sleep mode (clamshell open/close) does not work. When the computer awakes after sleep, it shows a black display. Also, the brightness slider will no longer show up in System Prefs -> Display. However, you can adjust the backlight to a fixed value. For example, I prefer the low backlight-level. In the recovery terminal,
$ nvram backlight-level="\%00"
Various valid values in the increasing order of brightness are: 0%00, C%00, \%00, z%00, %9f%00, %cb%00, %01%01, A%01, %8c%01, %e6%01, P%02, %d2%02, \%03, %ff%03.
- Once you use this patch, you won’t be able to connect to external displays and project on that screen (as MacBook-Pro routes to external ports – HDMI and thunderbolt using the dGPU)
- When the computer after sleep, it shows a black display but the machine is still running the OS. To get the screen back, I need to turn the machine off. But this means, its improper shutdown when you have processes running. One solution is that you can remote desktop into the system by using Screen Sharing or VNC. Using this you can get back into the machine, and work like usual until the process completes and then shutdown the machine. Also, while using Screen Sharing, you can project the shared screen on an external display from that client machine.
22nd Nov 2020 Update: I updated to Catalina 10.15.7 from 10.15.6. I could boot back into my Mac and work without any hiccups! I’ll try installing Docker and see if it crashes again.
18th Nov 2020 Update: Yesterday I directly updated to Catalina 10.15.6 skipping Mojave and it went fine. I could boot back into my Mac and work with it just like before. I was not able to run Docker, as it would cause the OS to crash and I had no option but to remove it. Next step would be to apply the 10.15.7 Combo Supplemental update. Once I am able to get that done as well, I’ll share my findings on this post. Stay tuned!
Earlier Update: I’ve updated to High Sierra 10.13.6. After this I applied the Security Update 2019-001 and it went fine. I could boot back into my Mac and work with it just like before. I have not updated to Mojave yet.
RAFH said:
I managed to fix the laptop awhile back following this guide, and its been fine for months…
but this morning i reset my PRAM (CMD + OPTION + P +R) because my when my laptop was booting it wasnt playing the usual chime sound as the apple logo/loading bar was displayed.
So i did this command, and my display went black, and now I’m stuck with a black screen again… did i mess something up? Any help would be appreciated, as I was a happy camper, and now worried that I wont be able to see / navigate the computer to do any fix… to fix the laptop awhile back following this guide, and its been fine for months…
but this morning i reset my PRAM (CMD + OPTION + P +R) because my when my laptop was booting it wasnt playing the usual chime sound as the apple logo/loading bar was displayed.
So i did this command, and my display went black, and now I’m stuck with a black screen again… did i mess something up? Any help would be appreciated, as I was a happy camper, and now worried that I wont be able to see / navigate the computer to do any fix…please help!
LikeLike
Dhaval Dalal said:
Follow the same process again and hopefully you should be fine.
LikeLike
RAFH said:
Any idea what resetting the PRAM would have done to cause the issue to resurface?
I cannot get the screen to turn on at all…not sure how I can go about navigating the computer to try and fix the issue again…
LikeLike
Dhaval Dalal said:
I think your settings are reset to old and hence this problem. You can try resetting the PRAM again and maybe retry again 3-4 times and if LUCK favors the screen will be back and then follow this process again. Hope that may solve your issue.
LikeLiked by 1 person
SamIam said:
Sometimes the easiest solution is the correct one…long story short I had same issue where my screen would go black after some use I read this article and it sounded like the solution to my problem luckily I didn’t try it instead my dad a computer technician took a look at it and quickly determined that the fans weren’t turning at a proper speed not allowing for sufficient cooling of the heatsink that keeps the cpu and gpu cool … I bought 2 new fans on amazon and some thermal paste removed the old fans and heat sink, cleaned the cpu and gpu from the old worn out thermal paste and applied a new layer, installed the new fans and now my MacBook is working just like it should, please before you try any of the above mentioned suggestions make sure that the cpu and or the gpu are not over heating the solution could be as simple as just changing out your fans
LikeLike
Fishek said:
does anyone know if it works on catalina?
LikeLike
Stefan said:
Yes, on my system (MacBook Pro, 2012, Retina) it worked fine with Catalina
LikeLiked by 1 person
dodo said:
Yes I had this patch applied on high sierra and yesterday I went to upgrade to Catalina and it works as before.
I’ve got a macbook pro mid 2012 15″ with nvidia dgpu
Hope this will help you, Cheers
LikeLike
shalin said:
Yes, do this in sierra, then update to catalina. it works
LikeLike
Dalton Grimm said:
Just tried. It did not. Could not get it to reboot after.
LikeLike
Jim said:
It has been working for a day on my mid 2012 macbook pro retina.
LikeLike
Vince Aguil said:
Thanks for the code it worked perfectly I wanted to ask how to do you revert back to having the driver work normally. I’m afraid of messing up the computer and im not sure how to make these changes.
Thank you.
LikeLike
Faz said:
Hi, were you able to revert the settings ?
LikeLike
Kevin H. Weiss said:
I’m also having trouble on Catalina. Anybody tried this?
LikeLike
sc said:
the side effects like no display, brightness, and black screen after sleep seem brutal and unacceptable. Isn’t there a better way than this to bypass Nvidia GPU more simply? Gfxconfig 2.4.1 util seems to be crashing the system too.
LikeLiked by 1 person
sc said:
This procedure does not work overall. My system is stuck while booting after the last reboot. Seems like this bogus procedure hosed my system completely! The hint was that rm -rf /System/Library/Caches/com.apple.kext.caches/ step didn’t not work in single user mode. Tried with sudo as well. It gave an error that operation not permitted on this read only file system (which I thought we had addressed with the -uw step above). Anyway, I will look to revert these changes. Meanwhile PLEASE DO NOT USE THIS PROCEDURE, IT IS FAULTY!
LikeLike
faz said:
Did you find a way to revert to the original settings ? As I’m scared doing a PRAM reset after doing this disable will make it worse.
LikeLike
Martin said:
Actually i didnt… Because when i reset the pram my macbook just broke… There is something wrong with the power rails to the cpu/gpu part. So I would advise to not reset to original settings, keep using the computer with only the integrated gpu and that is it. Maybe a good repair shop could help you, but i dont think it is financially acceptable. Better buying a new one. Its fixable, but not cheap.
LikeLike
psk said:
I had the failing GPU problem since 2 years ago. I found acceptable solution by booting with:
$ sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
and by using gSwitch (https://codyschrank.github.io/gSwitch/) to force MacOs to use integrated GPU only. However, unexpected blank screen could occur as some applications may temporary force the use of discrete GPU.
A week ago I found an optimal solution. I’m using MacOs Catalina 10.15.5 with discrete GPU powered off and both screen brightness and sleep/awake functioning normally.
I followed the instruction posted hese by ferakles:
then, as NativeDisplayControl was not working on my system (don’t ask me why), I followed this post to replace AppleMuxControl.kext after installing Catalina:
https://forums.macrumors.com/threads/disable-a-failed-amd-gpu-on-a-2011-macbook-pro-grub-solution.2087527/post-27525770
Basically, I’m using the GRUB solution to power-off the Nvidia GeForce before booting. Then, I replaced the MacOs Catalina version of AppleMuxControl.kext with the Sierra version to resolve the screen brightness and the sleep/awake issue.
LikeLike
Kang said:
Can you post command line of how you replaced the kexts? -Seems impossible in Catalina due to read/write and splitting of system and date..
LikeLike
Alex said:
MacBook early 2013 A1398 turned off in NVRam GeForce, it worked perfectly on the integrated Intel, after installing update 10.15.4 it stopped coming out of sleep. The black screen and for a second every 7-10 seconds the keyboard backlight lights up.
Installation 10.15.5 did not change anything.
LikeLike
Doug said:
Tried this on my 2012 Retina with Mojave, and now it won’t boot. Fun!
LikeLike
Felix said:
Hi, worked for me too 🙂 Not working brightness keys aren’t the problem but know my screen brightness is significantly darker than before. Any idea to get back the 100% of display brightness?
LikeLike
Felix said:
*now (excuse for my English please)
LikeLike
RAFH said:
I accidentally reset my pram / smc , and i believe it reset the brightness of the display to zero. Does anyone have any advice on how I could change it back to a higher level of brightness, but doing this while I cannot see anything? It would really be appreciated as everything was working fine after I disabled the GPU, until I did this pram /smc reset…
Thanks in advance
LikeLike
faz said:
Were you able to fix this ? Please let men now! thanks.
LikeLike
Minhazul Huda said:
It worked with my Catalina!!! thanks a lot. You saved my life. One thing, I cannot adjust the brightness to a fixed value using the way you mentioned. Any suggestion about it. Thanks again.
LikeLike
Minhazul Huda said:
Also there is now way to set a fix value for the screen brightness? It’s really too bright. Thanks again.
LikeLike
sundar said:
Hi, can you please let me know how to increase the brightness. Tx.
LikeLike
morph said:
is there any difference in just using gfxcardstatus https://gfx.io/ and setting it to integrated only. that way at least you can continue to use screen brightness etc.
LikeLike
morph said:
i have seen similar issues on a MBP 2012 Retina with Nvidia dGPU, it works erractically. Other advantage of just using the integrated setting is that fans don’t spin up all the time.
LikeLike
umashankarkv said:
Hi, did this patch on my mid 2012 MBP with Catalina, but it is getting stuck when I try to boot normally…it never boots normal. Any suggestion?
LikeLike
Dhaval Dalal said:
no idea…I have not yet tried Catalina
LikeLike
umashankarkv said:
Finally, it worked – (without the brightness and awake from sleep features). I just downgraded to High Sierra and did the patch. Later upgraded to Catalina.
Thanks a ton Dhaval!
Couple of things I encountered.
1. When I tried to apply this patch with Catalina OS, Step8 – Delete drive cache never happened – returned error with read only access. (May be that is something to do with the file system I believe (Despite mounting the disk with read and write access)
2. After updating to Catalina 10.15.4 the Nvidia information is not available/visible in the system report – Graphics/Displays. But once you update the OS to 10.15.6 the Nvidia information is back. No need to worry, that won’t affect the applied patch.
LikeLiked by 1 person
Giorgio said:
I had the failing GPU problem since 2 years ago. I found acceptable solution by booting with:
$ sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
and by using gSwitch (https://codyschrank.github.io/gSwitch/) to force MacOs to use integrated GPU only. However, unexpected blank screen could occur as some applications may temporary force the use of discrete GPU.
A week ago I found an optimal solution. I’m using MacOs Catalina 10.15.5 with discrete GPU powered off and both screen brightness and sleep/awake functioning normally.
I followed the instruction posted here by ferakles:
then, as NativeDisplayControl was not working on my system (don’t ask me why), I followed this post to replace AppleMuxControl.kext after installing Catalina:
https://forums.macrumors.com/threads/disable-a-failed-amd-gpu-on-a-2011-macbook-pro-grub-solution.2087527/post-27525770
Basically, I’m using the GRUB solution to power-off the Nvidia GeForce before booting. Then, I replaced the MacOs Catalina version of AppleMuxControl.kext with the Sierra version to resolve the screen brightness and the sleep/awake issue.
LikeLike
Andy said:
Which macbook pro do you have? Can you use it properly with an external display?
LikeLike
Giorgio said:
Dear Andy,
I have an early 2013 15” Retina MBP. I haven’t tried the MBP with this solution with an external display, but I would bet it will work.
LikeLike
Emiliiano said:
Hello Giorgio. I followed your recommendation. I have successfully set the GRUB solution to power-off the Nvidia GeForce before booting and now trying to resolve the screen brightness and the sleep/awake issue. NativeDisplayControl is not working for me either. My question is: by following the instructions to replace the MacOs Catalina version of AppleMuxControl.kext with the Sierra version would I solve both issues?
Or should I also install the kext from https://github.com/timpalpant/NVDAGPUWakeHandler ?
My problem is that I don’t know how to compile from the github content to get the kext. Any guide or help to get this done?
LikeLike
Giorgio said:
Dear Emiliano,
follow the post #179 by nsgr here: https://forums.macrumors.com/threads/disable-a-failed-amd-gpu-on-a-2011-macbook-pro-grub-solution.2087527/post-27525770
You can download the Sierra kext and then follow the instruction to install ths Sierra version of AppleMuxControl.kext on Catalina.
LikeLike
Major said:
Hi guys – great to see this thread evolve. I am about to upgrade a MBP 15 inch Mid 2012 (A1286) with a SSD. This is a lovely 2.3 Ghz/Core i7 (non Retina) machine that has issues with the dGPU and was modified some time ago to boot without dGPU enablesd. Amazingly is works with WakeFromSleep and the screen brightness also works… I did not do the modification myself but understand it was done using a bootable Linux to make the changes. SO… my lazy question.. Once I swap out the drive what is the best way to proceed? Also – has anyone trued this technique to resolve the IC as per Louis Rossman for (A1398) : https://www.youtube.com/watch?v=4gH1gBRneZk
Thanks again all!
LikeLike
zcream said:
@Major Did you try the Rossman IC fix for the mid 2012 MBP unibody ?
LikeLike
George Vlahakis said:
Thank you for a great guide and to the point! I have an early 2013 retina MBP and I set the GRUB.cfg as per – ferakles instructions and all works.
However, for unknown to me reasons, during boot the time to show the grub menu is rather huge (more than 10-15 sec) and then again when selecting the Mac partition I wait for another 10 secs.
Furthermore, when trying restarting OSX I get into a weird reboot situation where I also need to wait for extend time and eventually spawns the Apple logo and then reboots.
Any idea why these are happening and how I can go about speeding things up on this side?
PS: I have not done the sleep patch or the brightness kext.
LikeLike
andy said:
Anyone has a solution that could work with an external display?
LikeLike
Archer said:
I managed to fix the laptop awhile back following this guide, and its been fine for months…
but this morning i reset my PRAM (CMD + OPTION + P +R) because my when my laptop was booting it wasnt playing the usual chime sound as the apple logo/loading bar was displayed.
So i did this command, and my display went black, and now I’m stuck with a black screen again… did i mess something up? Any help would be appreciated, as I was a happy camper, and now worried that I wont be able to see / navigate the computer to do any fix… to fix the laptop awhile back following this guide, and its been fine for months…
but this morning i reset my PRAM (CMD + OPTION + P +R) because my when my laptop was booting it wasnt playing the usual chime sound as the apple logo/loading bar was displayed.
So i did this command, and my display went black, and now I’m stuck with a black screen again… did i mess something up? Any help would be appreciated, as I was a happy camper, and now worried that I wont be able to see / navigate the computer to do any fix…please help!
LikeLike
Luis Alberto said:
Yes, i had the same problem, i had the great idea of restart my VRAM and the PRAM as you. And after a long time of work (aplying this tutorial) my 2013 MP Retina 15″ showed the blackscreen again.
First of all its important to stand that the blackscreen problem is a problem generated for heat on the GPU, in my case i opened the macbook and i changed the termal paste, and put a mid size fan (one of those used to cool a room) pointed directly to the motherboard I turned on the Mac again without put the chassis (this gave me a few minutes) until the black screen will appeared again and i applied this tutorial quickly .
I hope the idea was understood, it works for me but sometimes you will have turn on the Mac until the Mac logo appears, because it doesn’t appear the first time that you change the termal paste.
Sorry for my english my native languaje is spanish if you want to correct me i will thank you.
LikeLike
Dhaval Dalal said:
I used to put ice-packs below the mac to let it cool down and have a USB fan…and then have worked out this solution, after lots of tries! I did not do any soldering or thermal paste change.
LikeLike
Jeevan Devasia said:
I think you can also disable SIP in the single user mode itself instead of going all the way to the recovery (cmd + R)
LikeLike
vince said:
Hello I wanted to ask what are the steps to revert back to normal.
LikeLike
John Doe said:
Ok but all this method works if you can startup the system. What can I do if only a glitched screen is displayed while startipng up the system?
LikeLike
sw1002 said:
Can You post a guide how to reactivate the dGPU ? I will have a repair of the logic board soon, therefore I need it,
Many thanks!!
Thomas
LikeLike
Thomas Lodzinski said:
How can I revert the patch to the previous state (and have the GPU enabled)?
I assume I have to move back the drivers from the directory and enable the GPU?
Can You please write the appropriate lines of code I have to type?
Many thanks,
LikeLike
KC said:
I just applied this fix on my Retina – mid 2012, and it has resolved the issue. I was using Catalina 10.15.5 or 10.15.6 and after applying this fix, I applied the update to 10.15.7 and still everything is working as expected. Only issue now is that I don’t have sleep option, and brightness control. Hope this helps anyone else in my position.
Also, a request I have 1 => if any one knows sleep/brightness fix then please share.
LikeLike
Giorgio said:
In order to get brightness and sleep/awake functioning, you have to replace the MacOs Catalina version of AppleMuxControl.kext with the Sierra version to resolve the screen brightness and the sleep/awake issue. Read my post here of June 18th 2020.
LikeLike
KING KIFLU said:
Dear Giorgio I can’t completely input this command line “sudo cp -vR /Users/Shared/Kext-Sierra-10.12.1/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleMuxControl.kext /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/” in the single user mode…. how do I fix that?
LikeLike
Martin said:
Just found out (after 1 year of using this trick and today I hopefully resolved the issue), that there is brightness slider app in the app store… it lets you change brightness on the fly by software. No sleep solution though.
LikeLike
Dhaval Dalal said:
Thanks!
LikeLike
Michel B said:
I applied the fix to my early 2013 PWB Retina 15″ which runs Mojave 10.14.6 and it works perfectly. Many thanks. Note that the Command+S single user mode has been deactivated in Mojave, but Command+S+R still works, though it is no documented by Apple.
LikeLike
zcream said:
Hi Dhaval. This was for the mid-2012 unibody MacBook pro right? It has 2 models i7 2.3 ghz and 2.6 ghz respectively.
Just making sure I have the same model 🙂 I have a black screen and the display went white when I disconnected an external monitor. After that u get black screen on boot.
LikeLike
gstar said:
After applying these fixes to a MBP 15, Retina Early 2013 running Catalina 10.15, has anyone else had an issue where the system goes into a very deep sleep state, where absolutely nothing will wake it? I’ve had this occur twice now, and was in the process of disposing the Macbook months after the first occurence, when it came back to life after one last attempt.
In my case, only a full battery discharge (basically, leave it unplugged for at least 3-4 months) and then powering it on will clear this bug. It’s really strange, I’ve not seen anyone else report this issue.
LikeLike
Cat_lina said:
Tried this patch on Catalina 10.15.4, worked well. No issues so far, will report if I see any issues.
LikeLike
Martin said:
Hey! I thank you first of all, since I didn’t thank you when I was “repairing” the problem with my MBP mid2012. The solution you posted is indeed working, with some cons, the biggest being not having the ability to put the MBP to sleep. I found a little app to control the screen brightness through software (search for brightness slider). Anyway, today I had a sip of wine and said to myself I need to try and repair the issue, hopefully it’s only bad solder joints on the U8900. I did, it went smoothly, the computer still works and the solder joints look way better than before and luckily I got rid of the micro cracks.
Now the question is, how do I revert this back? How do I disable, thus re-enable the Nvidia graphics in verbose mode?
Thanks again…
LikeLike
Dhaval Dalal said:
Sorry I would not know that
LikeLike
Vivian Fernandes said:
Hey Dhaval. I am trying to follow the steps you mentioned, but my system does not start in the recovery mode. It starts in internet recovery mode. I am on Mojave.
LikeLike
Panos said:
how do we revert the procedure .
LikeLike
Krzysztof Starzyński said:
I couldnt boot into recovery mode cause of freeze so in single user mode ive typed
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
That let me in and ive installed system then ive done everything step by step like in tutorial but now when i boot the spinning wheel below Apple logo is spinning and spinning. Before it was freeze and Game over so i think im closer to boot this mid 2012 15” MacBook Pro. Any solutions?
LikeLike
Dhaval Dalal said:
Not that I’m aware of!
LikeLike
SamIam said:
Sometimes the easiest solution is the correct one…long story short I had same issue where my screen would go black after some use I read this article and it sounded like the solution to my problem luckily I didn’t try it instead my dad a computer technician took a look at it and quickly determined that the fans weren’t turning at a proper speed not allowing for sufficient cooling of the heatsink that keeps the cpu and gpu cool … I bought 2 new fans on amazon and some thermal paste removed the old fans and heat sink, cleaned the cpu and gpu from the old worn out thermal paste and applied a new layer, installed the new fans and now my MacBook is working just like it should, please before you try any of the above mentioned suggestions make sure that the cpu and or the gpu are not over heating the solution could be as simple as just changing out your fans
LikeLike