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.
Does anyone else have the problem, where the screen stays black after standby? the computer is still responsive, but I can't get the screen to work.

Yes I have met this issue as well a couple of times, but i cannot see any pattern in the occurings. Sometimes the black screen is occuring during a shutdown, or restart. The computer fails to shut down it just hangs with the black screen.
 
Last edited:
  • Like
Reactions: GDBO
The first time I put the mac to sleep after utilizing procedure #429, getting it out of sleep the screen went black and it basically froze. It may also get stuck while shutting down with a black screen.

Can anyone lead me through having procedure #429 done also for the other two OSX installed on my system (Lion and Mavericks) ?

By default, it changes the settings for Sierra I believe.

When going into single user mode to move the kext file to a "backup" folder, how do you make it affect Lion or Mavericks on the same computer ?
 
Last edited:
So I restored my 10.12.5 Time Machine in an attempt to get my old thermal performance back and am once again not having luck. Every combination of Kexts I've tried are sitting me somewhere beetween 41-43C after extended idle time whereas previously I would be sitting at 34-36C if I didn't touch the laptop for 30 minutes or so.
 
In 10.12.6 I had it once when I left all of the kexts in the Extensions folder when waking up and it just happened to me again during the shutdown phase of a restart.

Leaving all of the kexts in the folder might not be the ideal shortcut.

Does anyone else have the problem, where the screen stays black after standby? the computer is still responsive, but I can't get the screen to work.
 
Thanks

But:

1. Will the apps asking for the AMD, still load after the mod ?

2. Will this mod affect all OSX's installed on my system (i.e Lion, Sierra, Mavericks) ? Should it be made 3 times, each for any of these systems?

3. What tools are required ? does it involve replacing the GPU, or simple soldering?

Thanks again!

Here is the hardware solution:


Like I said. It's complicated, and not worth it for a five year old machine...
[doublepost=1500733984][/doublepost]
The first time I put the mac to sleep after utilizing procedure #429, getting it out of sleep the screen went black and it basically froze. It may also get stuck while shutting down with a black screen.

Can anyone lead me through having procedure #429 done also for the other two OSX installed on my system (Lion and Mavericks) ?

By default, it changes the settings for Sierra I believe.

When going into single user mode to move the kext file to a "backup" folder, how do you make it affect Lion or Mavericks on the same computer ?

When you run different versions of MacOS on the same hard drive, don't they install on different partitions? If so, it would seem that you would have to install this mod on each of the partitions?
 
Last edited:
Yes I have met this issue as well a couple of times, but i cannot see any pattern in the occurings. Sometimes the black screen is occuring during a shutdown, or restart. The computer fails to shut down it just hangs with the black screen.

I already had this black screen problem when restarting or shutting down by this procedure: apple logo (upper left corner of the screen) -> Restart or Shut Down.

Now I only do these procedures to restart or shut down the Macbook Pro.

1 - Restart Macbook Pro

Applications -> Utilities -> Terminal

sudo shutdown -r now


2 - Shut down - Halt - Power off Macbook Pro

sudo shutdown -h now
 
  • Like
Reactions: GDBO
Well hopefully this problem goes away with the next update.

I already had this black screen problem when restarting or shutting down by this procedure: apple logo (upper left corner of the screen) -> Restart or Shut Down.

Now I only do these procedures to restart or shut down the Macbook Pro.

1 - Restart Macbook Pro

Applications -> Utilities -> Terminal

sudo shutdown -r now


2 - Shut down - Halt - Power off Macbook Pro

sudo shutdown -h now
 
Hi,
Just signed up to thank everyone in this thread, I did the post in page 5, and today I started reading all the pages after page 9 (that was the last page last time I looked at this thread).
After reading the bug with temperature I noticed I "kind of" had this issue, my idle was in the high 50s and low 60s.
I was about to do the post by GDBO, which summarizes nsgr discovery, and noticed my mac had downloaded 10.12.6 update. Said a couple of hail marys and installed it. Left it reboot a zillion times and now my mac is in the mid 30s idling, gpu diode temperature is now about 20 degrees (before it was a degree or two above or below cpu diode).
I checked for loaded amd kexts (before i had none), and have the following

149 2 0xffffff7f83376000 0x122000 0x122000 com.apple.kext.AMDLegacySupport (1.5.1) 0670744B-B64C-3424-B186-FD972A37E78E <108 12 11 7 5 4 3 1>
153 0 0xffffff7f83498000 0x12e000 0x12e000 com.apple.kext.AMD6000Controller (1.5.1) 2015FD1C-294C-3C71-AEB5-C1EE0E65BD46 <149 108 12 11 5 4 3 1>
156 0 0xffffff7f837aa000 0x571000 0x571000 com.apple.AMDRadeonX3000 (1.5.1) F6F37414-893B-3F66-8AB7-F3327DE6AC55 <155 136 108 12 7 5 4 3 1>
157 0 0xffffff7f83d1b000 0x22000 0x22000 com.apple.kext.AMDLegacyFramebuffer (1.5.1) 930A7077-5EBD-3FA5-A023-415A1438E132 <149 108 12 11 7 5 4 3 1>

My Macbook is a 2.0 i7 with the 6490 AMD (Early 2011).

Thanks again to all of you!


EDIT: As usual I spoke too soon, rebooted and now I WILL have to do the procedure again je...
I edited gpu-power-blabla again to be able to boot into mac for the time being. I checked and have the same kexts loaded now, apart from a new one AMDSupport (?)
 
Last edited:
It seems like you added quite a few steps. Steps 4 & 6 shouldn't be required and step 5 can be done directly in recovery mode.


Complete Guide to Permanently Disable AMD 6XXXm series dGPU and Prevent Thermal Throttling

Acknowledgements: This guide is entirely based on nsgr's work.

1. This is an optional step. If you have previously attempted to remove AMD kexts, revert your system to the original state by installing the latest Mac OS combo update. At the time of writing of this guide, the latest combo update can be found here. Installing the update will update your kext files to the latest version. After the update is finished, your macbook will restart and freeze as soon as the dGPU is activated. Shutdown or force a restart.

2. Clear the NVRAM by holding Option + Command + P + R on startup until the macbook reboots.

3. Boot into the single user mode by pressing Command + S on startup. Execute the following commands to enable the iGPU during the boot phase:



4. Disable System Integrity Protection to allow editing system files. Boot into the verbose recovery mode by pressing Command + R + S on startup. Execute



5. Go again into the the single user mode by pressing Command + S on startup. Mount root with write permissions via

(Note the space in front of the last forward slash). Next, create a backup folder by executing

Move the AMDRadeonX3000.kext file to the backup folder you created by executing

Moving this kext file is sufficient to prevent graphics switching.


6. Re-enable System Integrity Protection inside the verbose recovery mode (Command + R + S) by executing



7. Boot into Mac OS normally and start the Terminal. Navigate to your backup folder using

Load the former kext file manually by executing

to prevent the dGPU from idling at maximum TDP. This will not re-enable graphics switching. A restart is not required.

Closing remarks: Step 7 will have to be executed after every system restart to prevent overheating. Steps 4, 5 and 6 will have to be executed after each major system update that breaks graphics switching. Step 3 has to be repeated after a NVRAM reset.
[doublepost=1500806241][/doublepost]Also this black screen lockup when opening the lid is going to get old pretty fast... I wonder if it's caused by leaving in all of those extra Kexts.
 
Last edited:
It seems like you added quite a few steps. Steps 4 & 6 shouldn't be required and step 5 can be done directly in recovery mode.

Wrong.
[doublepost=1500808053][/doublepost]
Also this black screen lockup when opening the lid is going to get old pretty fast... I wonder if it's caused by leaving in all of those extra Kexts.
Not sure, I have not tried deleting all kexts. We could try leaving just the ones inside that are autoloaded.
 
Last edited:
Not wrong... I've done this several dozen times already with nsgr and not once have I had to disable SIP...

Single user mode - edit nvram

Recovery mode - Create directory and move AMDRadeonX3000.kext

Boot normally and load AMDRadeonX3000.kext through terminal.

This is enough already and the procedure I have done time and time again.

Go look at Fguarini's instructions, Section 3.1. There is no need to disable SIP.


When we were testing this before the update (the several dozen times I've already done this as previously mentioned) I never had a black screen while only having AMDSupport.kext AMDFramebuffer.kext and AMD6000Controller.kext. What makes it difficult to test though is that the black screen happens so inconsistently.




Wrong.
[doublepost=1500808053][/doublepost]
Not sure, I have not tried deleting all kexts. We could try leaving just the ones inside that are autoloaded.
 
Last edited:
Not wrong... I've done this several dozen times already with nsgr and not once have I had to disable SIP...

Single user mode - edit nvram

Recovery mode - Create directory and move AMDRadeonX3000.kext

Boot normally and load AMDRadeonX3000.kext through terminal.

This is enough already and the procedure I have done time and time again.

Go look at Fguarini's instructions, Section 3.1. There is no need to disable SIP.


When we were testing this before the update (the several dozen times I've already done this as previously mentioned) I never had a black screen while only having AMDSupport.kext AMDFramebuffer.kext and AMD6000Controller.kext. What makes it difficult to test though is that the black screen happens so inconsistently.

Hmmm. As I recall, moving AMDRadeonX3000 to a backup folder in the root failed without disabling SIP. After what appeared to be a successful move, looking at /System/Library/Extensions, I saw that AMDRadeonX3000 was still there!

Edit: Found this...

For those wondering, System Integrity Protection locks down the following system level directories in Mac OS X:

/System
/sbin
/usr (with the exception of /usr/local subdirectory)

Accordingly, rootless may cause some apps, utilities, and scripts to not function at all, even with sudo privelege, root user enabled, or admin access.
 
Very strange, the only time I had to disable SIP was when I went through the Arch Linux method.

Hmmm. As I recall, moving AMDRadeonX3000 to a backup folder in the root failed without disabling SIP. After what appeared to be a successful move, looking at /System/Library/Extensions, I saw that AMDRadeonX3000 was still there!
 
Very strange, the only time I had to disable SIP was when I went through the Arch Linux method.

Hmmm My screen was black too when Sierra 10.12.6 installed and rebooted... Force restart showed AMDRadeonX3000 showed up in /System/Library/Extensions and had automatically loaded according to Kextstat... After I moved it outta there, (With SIP disabled), all was fine after kextloading from /backup it after login...

Could this be the source of your random black screens?
 
I don't think so because I did it the same way (recovery mode, move kexts (SIP enabled)) when I was on 10.12.5 and I never had a black screen lockup then.

Both times when I updated 10.12.6 I let it boot totally the first time and as expected it locked up after I entered my password and it tried to load. Then I restarted into recovery, moved the kexts (with SIP enabled) and then rebooted without locking up after logging in (verified by toggling to discrete graphics using gfxCardStatus).

I also always verify that the kext(s) have been moved with ls, and I always check kextstat before manually loading AMDRadeonX3000 to verify what's already been loaded (I do this because my laptop will randomly decide whether or not it wants to load AMDSupport and I simply want to check what's going on that boot).


Edit: The only thing that I have done differently (aside from updating to 10.12.6 of course) is that I am now using the 1012.6 v1.5.1 Kexts instead of the 10.12.3 v1.4.8 Kexts in the Extensions folder.



Hmmm My screen was black too when Sierra 10.12.6 installed and rebooted... Force restart showed AMDRadeonX3000 showed up in /System/Library/Extensions and had automatically loaded according to Kextstat... After I moved it outta there, (With SIP disabled), all was fine after kextloading from /backup it after login...

Could this be the source of your random black screens?


Edit2: I have noticed now that after login (before loading AMDRadeonX3000.kext) AMDLegacySupport, AMDSupport, AMD6000Controller, and AMDLegacyFramebuffer get loaded. As soon as I load AMDRadeonX3000.kext, AMDSupport gets unloaded. Must have something to do with the dependencies of the 10.12.6 v1.5.1 AMDRadeonX3000.kext but I wonder if that might be the culprit of the black screens somehow.
 
Last edited:
In Recovery mode you do not need to disable SIP (csrutil disable) to move the AMD kexts.

1 - Single User Mode -> Command + S -> Uses the Mac OS X operating system installed on the hard disk.

The /System directory is locked (csrutil enable).


2 - Recovery Mode -> Command + R -> Uses the operating system OS X Base System installed on the hard disk or Recovery Mode from Internet (Shift-Option-Command-R).

The OS X Base System is on a different partition. It is an independent operating system. So it bypasses SIP and moves the AMD kexts even with SIP enabled (csrutil enable).
 
Last edited:
Well there you go GDBO... And you even got an explanation for why you were wrong. Might be a good idea to edit your instructions... There's no point making people jump through extra hoops if they don't need to. ¯\_(ツ)_/¯

Wrong.
[doublepost=1500808053][/doublepost]
Not sure, I have not tried deleting all kexts. We could try leaving just the ones inside that are autoloaded.

In Recovery mode you do not need to disable SIP (csrutil disable) to move the AMD kexts.

1 - Single User Mode -> Command + S -> Uses the Mac OS X operating system installed on the hard disk.

The /System directory is locked (csrutil enable).


2 - Recovery Mode -> Command + R -> Uses the operating system OS X Base System installed on the hard disk or Recovery Mode from Internet (Shift-Option-Command-R).

The OS X Base System is on a different partition. It is an independent operating system. So it bypasses SIP and moves the AMD kexts even with SIP enabled (csrutil enable).
 
Last edited:
In Recovery mode you do not need to disable SIP (csrutil disable) to move the AMD kexts.

1 - Single User Mode -> Command + S -> Uses the Mac OS X operating system installed on the hard disk.

The /System directory is locked (csrutil enable).


2 - Recovery Mode -> Command + R -> Uses the operating system OS X Base System installed on the hard disk or Recovery Mode from Internet (Shift-Option-Command-R).

The OS X Base System is on a different partition. It is an independent operating system. So it bypasses SIP and moves the AMD kexts even with SIP enabled (csrutil enable).

Thanks for clearing that up nsgr!
 
Hello, thank you for your detailed instructions. I am having trouble with the chattr step.. it says:
sh: chattr: not found

Any ideas? Attaching a few (color corrected :mad:) photos... I can see the "gpu-power-prefs..." that i created. There wasn't a "gpu-power..." in the list before i created it.

sorry if this is a repeat question!

early 2011 MBP 15"







1.JPG
2.JPG
3.JPG
 
That happened to me with a bad formatted archlinux pendrive.
What method did you use?
 
That happened to me with a bad formatted archlinux pendrive.
What method did you use?

the "macOS" option from the ArchLinux link:
$ diskutil list
$ diskutil unmountDisk /dev/diskX
$ sudo dd if=path/to/arch.iso of=/dev/rdiskX bs=1m

did you ever get it to work?
 
Yes, but I used a Ubuntu machine to do so, although they were similar commands to those you tried.
I don't remember right now if i wrote to the partition or the whole disk... you should try the other one (writing to the partition if you wrote to disk or writing to the whole disk if you only wrote to the partition)


EDIT: I remember now that i had that problem when during the startup (archlinux from pendrive) the display showed that it could not mount the archlinux partition

PS: Sorry for my english
 
Yes, but I used a Ubuntu machine to do so, although they were similar commands to those you tried.
I don't remember right now if i wrote to the partition or the whole disk... you should try the other one (writing to the partition if you wrote to disk or writing to the whole disk if you only wrote to the partition)


EDIT: I remember now that i had that problem when during the startup (archlinux from pendrive) the display showed that it could not mount the archlinux partition

PS: Sorry for my english

In post #192 in this thread, nsgr described an alternate method to write the iGPU settings to EFI without having to boot via Archlinux. I invite you you to have a look at that post to avoid booting to the defective AMD chip. All you have to do is boot in single user mode (command-s) and execute a single line of code, and reboot.
 
In post #192 in this thread, nsgr described an alternate method to write the iGPU settings to EFI without having to boot via Archlinux. I invite you you to have a look at that post to avoid booting to the defective AMD chip. All you have to do is boot in single user mode (command-s) and execute a single line of code, and reboot.

thank you for directing me to that post! the screen now looks normal, however it has been stuck on the loading screen for a while... hoping it starts up eventually??

before and after the nsgr method:
bef.JPG
aft.JPG
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.