![]() ![]() (as far as just the SIP issues goes: is correct: Cmd + R + S, at least on Sierra, gets you recovery and single user and you can csrutil disable from there). which fails because it is a graphical environment and I have a failing GPU. SIP can only be disabled in Recovery mode. crutils disable, to disable SIP, won't work in Single User mode. Unfortunately, the System/Library/Extensions directory fall under Sierra's SIP protection so I can't carry out those instructions.Basically, boot into Single User mode and move some of AMD*.kext files from /System/Library/Extensions/ elsewhere. You can revert to using just the internal Intel graphics. My local repair shop, which is usually pretty handy, says it can't fix it. This has been a known problem, and Apple addressed with an extended warranty on these models's GPUs, which ended Dec 31st 2016. This is what I understand from my research: ![]() More information for this can be found in this rather long thread or in this amusing youtube video.My trusty MBP 17" 2011 is now hitting the failing AMD GPU issues. The cost for the parts will make you laugh with tears. That means owners holding on to these machines have to look for a trustworthy hardware repair shop that is not an AASP and willing to do this. Apple will not do that at all out of a bizarre principle and Apple also forbids AASPs do this kind of repair (the machine in question also is way out of warranty and AppleCare). ![]() If that is the case, then a good, and permanent, proper, fix would be to replace the cheap capacitor. The algorithm is based on a solution provided by user fabioroberto on MacRumors forums. MBPMid2010_GPUFix is an utility program that allows to fix MacBook Pro (15-inch, Mid 2010) intermittent black screen or loss of video. Performance will be a bit reduced by that. That can be made easier by using a ready made patch for that. That can be achieved by altering the kext AppleGraphicsPowerManagement.kext. If the capacitor is the problem, then one 'halfway' good solution is to circumvent the most problematic part of power management by lowering the power allowance for these dGPUs. But in reality it is most often only a tiny little capacitor that really has a flaw and interferes with power management of the dGPU. It is entirely possible that indeed the NVidia dGPU might be defective. It just appears like that because you notice the problems when the dGPU is 'switched on'. On most of these models it is not really the dGPU that is defective. While that circumvention is possible – either electrically, or with EFI/NVRAM hacking, or with moving the video driver kexts related to the NVidia-chip, it is by far not the best solution. Most owners of MBPs from 2010 with an apparently flawed NVidia dGPU should not seek to disable the GPU. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |