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.

nsgr

macrumors 6502
May 22, 2017
317
117
Okay, i redid Mikey N's guide and now my computer won't even boot up. instead it's always freezes at this point.

SICPROTODETACH_IM6: Fw8 error-6

I included a screen shot. Anyone know what to do?

MacOS system (El Capitan, Sierra, HighSierra)?

In your photo there is the message "GPU Hardware VM ... VRAM: disable".

VRAM = Video RAM, really important. This message is usually when the gpu-power-prefs is configured for the AMD GPU.

I'm not sure if you were able to change the gpu-power-prefs to the Intel GPU.

Test again with the gpu-power-prefs procedure for the Intel GPU. Then boot into Recovery Mode Graphical (Command + R at boot).

The Recovery Mode Graphical is to be fail-safe when the gpu-power-prefs is set to the Intel GPU.

If you can not get into Recovery Mode Graphical, then you have to check if you actually entered the correct commands for gpu-power-prefs with the exact letters, numbers, = and : of the GUID.

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

wilsondr

macrumors newbie
Jan 11, 2018
3
0
You are entirely correct and identified a shortcoming in my original guide:

Before an update you should move X3000 kext back to the default /System/Library/Extensions/ folder.
After an update X3000 has to be moved back to Extensions-off.

If a functional X3000 kext is present in its default location it will hang the system upon reboot in a system with the hack applied.

I only kept SIP disabled because it presents a huge hassle when moving kexts around. As long as there are no updates coming along from Apple SIP might also be (re-)enabled.
[doublepost=1512753058][/doublepost]

An upgrade to Sierra is imho quite commendable (but *only* because we have to hack around Apple's quality issues; a certain decline in over-all quality is also already present in Sierra, alas).

The upgrade is quite smooth sailing. It leaves the NVRAM hack in place. But it places a new X3000 kext in its default location -> System freeze on first full reboot -> disable SIP -> move kext in Single User -> presto. That also applies to High Sierra. (But being the train wreck HS is I won't upgrade to that.)


With Sierra I now have *no* issues with shutdown or sleep/waking.

Your minor issue might be mitigated?
Yosemite was problematic for me, Sierra improved on that on its own but below's addition makes it round again [I never tested the 'force' switch on 10.10]:
But that involved adding another command to the LoginHook, which is now:

#!/bin/bash
kextload /System/Library/Extensions-off/AMDRadeonX3000.kext
pmset -a force gpuswitch 0
exit 0



And after letting that load on boot one time; performing once again a complete reset/ re-application of the NVRAM hack: the machine doesn't mind what happens to the lid or how it is told to sleep or shutdown.

[The pmset command was discovered by @nsgr and @pvllo in #1066; 1000x kudos to you two!]

How do you edit the LoginHook to add the pmset -a force gpuswitch 0 text to my existing LoginHook?
 

Tonymakkaroni

macrumors newbie
May 31, 2018
3
0
I fixed it with these instructions, it works much better now: But my Macbook (HighSierra)shutdown randomly sometimes after 5 min of boot sometimes after some days only. It's always freezing for 30 sec and shut off. After pressing power button everything works fine. No correlation to any app sometimes all are closed and it still shutdown. Etrecheck Report says: Shutdown cause -128 and also did a Hardwaretest with no Errors and it works only with the integrated GPU. Before that fix, it had the same problems and symptoms with the AMD GPU like others.

But these random shutdowns now are very frustrating, does anyone has an idea, what this could be even when it works only with Intel GPU now?
 

Nightwing32

macrumors member
May 5, 2018
36
4
Thanks for your help! I'm on El Capitan.

It says GPU Hardware VM is disabled (mulitspace: disabled, paged table updates with DMA:disabled, non-contiguous VRAM:disabled) DSMOS has arrived.


The very last line on it says SIOPROTODETACH_IN6: fw0 error=6

I'm sorry but I'm not sure where to go from here. You think I should find a way to switch it back to Intel GPU?

Should I follow MikeyN's guide again? Which section should I start? Sorry for the questions, I'm a not as technically savvy. I uploaded a better photo of the error screen.




MacOS system (El Capitan, Sierra, HighSierra)?

In your photo there is the message "GPU Hardware VM ... VRAM: disable".

VRAM = Video RAM, really important. This message is usually when the gpu-power-prefs is configured for the AMD GPU.

I'm not sure if you were able to change the gpu-power-prefs to the Intel GPU.

Test again with the gpu-power-prefs procedure for the Intel GPU. Then boot into Recovery Mode Graphical (Command + R at boot).

The Recovery Mode Graphical is to be fail-safe when the gpu-power-prefs is set to the Intel GPU.

If you can not get into Recovery Mode Graphical, then you have to check if you actually entered the correct commands for gpu-power-prefs with the exact letters, numbers, = and : of the GUID.

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

nsgr

macrumors 6502
May 22, 2017
317
117
How do you edit the LoginHook to add the pmset -a force gpuswitch 0 text to my existing LoginHook?

Nano editor with sudo (increase permission level).

Inside Nano editor -> add pmset ... -> CTRL + O to save file -> CRTL + X to exit Nano editor.

Code:
sudo nano /Library/LoginHook/LoadX3000.sh

Follow - #1243

[doublepost=1527817204][/doublepost]
Thanks for your help! I'm on El Capitan.

It says GPU Hardware VM is disabled (mulitspace: disabled, paged table updates with DMA:disabled, non-contiguous VRAM:disabled) DSMOS has arrived.


The very last line on it says SIOPROTODETACH_IN6: fw0 error=6

I'm sorry but I'm not sure where to go from here. You think I should find a way to switch it back to Intel GPU?

Should I follow MikeyN's guide again? Which section should I start? Sorry for the questions, I'm a not as technically savvy. I uploaded a better photo of the error screen.

Quick Test - AMD GPU failure:

1 - Boot Single User Mode (Command + S at boot).

2 - NVRAM gpu-power-prefs to Intel GPU + boot-args verbose
Code:
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00

nvram boot-args="-v"

reboot

3 - Boot Recovery Mode Graphical (Command + R at boot).
Test result OK to Intel GPU-> show screen with Disk Utility, Install MacOS, etc.

Boot Recovery -> use another partition with another MacOS system.

-------

fw0 in my system is FireWire port.

en2 is Thunberbolt port.

List your Hardware Ports (my example Macbook Pro) - with Terminal:
Code:
networksetup -listallhardwareports

Hardware Port: Ethernet
Device: en0
Ethernet Address: xx:xx:xx:xx:xx:xx

Hardware Port: FireWire
Device: fw0
Ethernet Address: xx:xx:xx:xx:xx:xx:xx:xx

Hardware Port: Wi-Fi
Device: en1
Ethernet Address: xx:xx:x:xx:xx:xx

Hardware Port: Bluetooth PAN
Device: en3
Ethernet Address: xx:xx:xx:xx:xx:xx

Hardware Port: Thunderbolt 1
Device: en2
Ethernet Address: xx:xx:xx:xx:xx:xx

Hardware Port: Thunderbolt Bridge
Device: bridge0
Ethernet Address: xx:xx:xx:xx:xx:xx

Links:
SIOCPROTODETACH_IN6:en0 error=43 - Solved with erase partition and reinstall MacOS
https://discussions.apple.com/thread/382184

Problem with VPN DNS - PM kernel: SIOCPROTODETACH_IN6: fw0 error=6
https://x10hosting.com/community/threads/problem-with-vpn-dns.180133/

Maybe, wi-fi card problem.
 
Last edited:
  • Like
Reactions: Nightwing32

Nightwing32

macrumors member
May 5, 2018
36
4
Thank you. You are the man! I was able to get into recovery now. I am now reinstalling El Capitain.

So do I need to redo the Quick test once i reinstall El Capitain?

What would you recommend doing next?

Nano editor with sudo (increase permission level).

Inside Nano editor -> add pmset ... -> CTRL + O to save file -> CRTL + X to exit Nano editor.

Code:
sudo nano /Library/LoginHook/LoadX3000.sh

Follow - #1243

[doublepost=1527817204][/doublepost]

Quick Test - AMD GPU failure:

1 - Boot Single User Mode (Command + S at boot).

2 - NVRAM gpu-power-prefs to Intel GPU + boot-args verbose
Code:
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00

nvram boot-args="-v"

reboot

3 - Boot Recovery Mode Graphical (Command + R at boot).
Test result OK to Intel GPU-> show screen with Disk Utility, Install MacOS, etc.

Boot Recovery -> use another partition with another MacOS system.

-------

fw0 in my system is FireWire port.

en2 is Thunberbolt port.

List your Hardware Ports (my example Macbook Pro) - with Terminal:
Code:
networksetup -listallhardwareports

Hardware Port: Ethernet
Device: en0
Ethernet Address: xx:xx:xx:xx:xx:xx

Hardware Port: FireWire
Device: fw0
Ethernet Address: xx:xx:xx:xx:xx:xx:xx:xx

Hardware Port: Wi-Fi
Device: en1
Ethernet Address: xx:xx:x:xx:xx:xx

Hardware Port: Bluetooth PAN
Device: en3
Ethernet Address: xx:xx:xx:xx:xx:xx

Hardware Port: Thunderbolt 1
Device: en2
Ethernet Address: xx:xx:xx:xx:xx:xx

Hardware Port: Thunderbolt Bridge
Device: bridge0
Ethernet Address: xx:xx:xx:xx:xx:xx

Links:
SIOCPROTODETACH_IN6:en0 error=43 - Solved with erase partition and reinstall MacOS
https://discussions.apple.com/thread/382184

Problem with VPN DNS - PM kernel: SIOCPROTODETACH_IN6: fw0 error=6
https://x10hosting.com/community/threads/problem-with-vpn-dns.180133/

Maybe, wi-fi card problem.
 

nsgr

macrumors 6502
May 22, 2017
317
117
Thank you. You are the man! I was able to get into recovery now. I am now reinstalling El Capitain.

So do I need to redo the Quick test once i reinstall El Capitain?

What would you recommend doing next?

NVRAM gpu-power-prefs to Intel GPU -> stored in EFI chip -> logic board.

If reinstall El Capitan -> after half installation freeze Macbook Pro because AMDRadeonX3000.kext (rebuild kext cache) -> follow MikeN Guide disable SIP and move AMDRadeonX3000.kext to /System/Library/Extensions-off -> reboot -> continue installation El Capitan -> follow again MikeyN Guide and create LoginHook to load AMDRadeonX3000.kext only after login.

Follow - #875
Follow - #1243

----------

Follow this Guides:

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

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


Shutdown or Restart Macbook -> black screen - Page 57 - #1425

Close Lid - Sleep - Wake - Pages 43-50 - #1066 #1243

Update MacOS, then MacOS put back new /System/Library/Extensions/AMDRadeonX3000.kext -> no freeze Macbook Pro? - Page 70 - #1747
 

Nightwing32

macrumors member
May 5, 2018
36
4
UGH. I reinstalled ElCapitan and then I'm back at SIOPROTODETACH_IN6: fw0 error=6

When I type in
networksetup -listallhardwareports

after I type in Command S

it only says 1 thing : Hardware Port : thunderbolt Bridge Device: Bridge0 Etherenet Address: N/A

Thats it

NVRAM gpu-power-prefs to Intel GPU -> stored in EFI chip -> logic board.

If reinstall El Capitan -> after half installation freeze Macbook Pro because AMDRadeonX3000.kext (rebuild kext cache) -> follow MikeN Guide disable SIP and move AMDRadeonX3000.kext to /System/Library/Extensions-off -> reboot -> continue installation El Capitan -> follow again MikeyN Guide and create LoginHook to load AMDRadeonX3000.kext only after login.

Follow - #875
Follow - #1243

----------

Follow this Guides:

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

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


Shutdown or Restart Macbook -> black screen - Page 57 - #1425

Close Lid - Sleep - Wake - Pages 43-50 - #1066 #1243

Update MacOS, then MacOS put back new /System/Library/Extensions/AMDRadeonX3000.kext -> no freeze Macbook Pro? - Page 70 - #1747
U
[doublepost=1527824281][/doublepost]Thanks for your help. I'm thinking I"m coming close to taking out my SSD and trying to sell off this MBP for parts on ebay.. its incredibly frustration
 

nsgr

macrumors 6502
May 22, 2017
317
117
UGH. I reinstalled ElCapitan and then I'm back at SIOPROTODETACH_IN6: fw0 error=6

When I type in
networksetup -listallhardwareports

after I type in Command S

it only says 1 thing : Hardware Port : thunderbolt Bridge Device: Bridge0 Etherenet Address: N/A

Thats it


U
[doublepost=1527824281][/doublepost]Thanks for your help. I'm thinking I"m coming close to taking out my SSD and trying to sell off this MBP for parts on ebay.. its incredibly frustration

Remove any devices attached to your Macbook Pro.

Maybe install Sierra.

You erase (disk utility) MacOS El Capitan partition before re-install?

Use networksetup -listallhardwareports in Recovery Graphical Mode -> Utilities -> Terminal

Try boot in Safe Mode (press SHIFT key at boot) -> if show login screen then the problem maybe in some kext.
 
Last edited:

Nightwing32

macrumors member
May 5, 2018
36
4
Remove any devices attached to your Macbook Pro.

Maybe install Sierra.

You erase (disk utility) MacOS El Capitan partition before re-install?

Use networksetup -listallhardwareports in Recovery Graphical Mode -> Utilities -> Terminal

Try boot in Safe Mode (press SHIFT key at boot) -> if show login screen then the problem maybe in some kext.
Safe mode won't even boot.

How do I erase the El Capitan pratition before I re-install? I'll try it one more time before I sell this.

Thanks again for your help.
 

nsgr

macrumors 6502
May 22, 2017
317
117
Safe mode won't even boot.

How do I erase the El Capitan pratition before I re-install? I'll try it one more time before I sell this.

Thanks again for your help.

Before sell Macbook Pro or only Hard Drive:

1 - Boot with MacOS installer disk CD / Pendrive / USB Stick -> press Option at boot and select MacOS installer disk.

2 - Show graphical screen -> Disk Utility -> Select the disk instead partition - example select Samsung, Seagate, etc -> Erase -> Security Option -> Zero out Data or the second "|" after Fastest option -> OK.

If you select the entire disk (Samsung, Seagate, etc), then the disk utility will erase all partitions on your disk, including the Recovery partition and other partitions you have created for personal data.

Back up your data to another disk (external hard drive) before doing this.

Only HDD -> show Secure Erase Options. There is no such option for SSDs. At least in HighSierra it is not possible.


https://support.apple.com/kb/ph22241?locale=en_US
Note: With a solid-state drive (SSD), secure erase options are not available in Disk Utility. For more security, consider turning on FileVault encryption when you start using your SSD drive.


This video -> select only MacOS partition (Snow Leopard) instead "500 11 GB STS..." -> erase only MacOS partition -> other partitions like Recovery partition are preserved.

ERASE MAC HARD DRIVE AND REINSTALL OS X! EASIEST METHOD!
 
  • Like
Reactions: Nightwing32

LUKas007

macrumors newbie
Jan 30, 2008
18
0
First of all - thank you all for this great forum and helpful tips that I found here when I experienced a GPU breakdown in my late 2011 MacBook Pro 15" recently.

I moved the AMDRadeonX3000.kext file, then I used the
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00 setting to enable the Intel GPU.

While the laptop is thankfully working again, I noticed the temperature increased quite a lot even at idle... I did some research and I came upon the slightly "mysterious" nvram boot-args="agc=0" option... From all the small pieces of information I found, it seems that it disables the GPU dynamic switching - therefore prevents the overheating issue.

From my experience it seem to be exactly the case - with nvram boot-args="agc=0" enabled the laptop boots at about 50C, when I remove it it boots at 65C (it manages to warm up during boot time) and then when I use the sudo kextload AMDRadeonX3000.kext command it drops again...

To sum up: its seems that nvram boot-args="agc=0" disables the failed AMD chip during the boot process, so manually loading the AMDRadeonX3000.kext file is no longer needed... If someone could confirm this and did some testing, that would be great.

Thanks!
 

Nightwing32

macrumors member
May 5, 2018
36
4
Remove any devices attached to your Macbook Pro.

Maybe install Sierra.

You erase (disk utility) MacOS El Capitan partition before re-install?

Use networksetup -listallhardwareports in Recovery Graphical Mode -> Utilities -> Terminal

Try boot in Safe Mode (press SHIFT key at boot) -> if show login screen then the problem maybe in some kext.

Okay I got into safemode and lists
Hardware Port Ethernet Device en0
Hardware Port Wifi en1
Hardware Port Thunderport Bridge Device Bridge0

That's it.

So I am back at it today. It works again for some reason in safe mode. I'm trying to back up before i reinsall as you recommened. I still have no idea why it won't boot normally and what fw0 is?
 

nsgr

macrumors 6502
May 22, 2017
317
117
First of all - thank you all for this great forum and helpful tips that I found here when I experienced a GPU breakdown in my late 2011 MacBook Pro 15" recently.

I moved the AMDRadeonX3000.kext file, then I used the
nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00 setting to enable the Intel GPU.

While the laptop is thankfully working again, I noticed the temperature increased quite a lot even at idle... I did some research and I came upon the slightly "mysterious" nvram boot-args="agc=0" option... From all the small pieces of information I found, it seems that it disables the GPU dynamic switching - therefore prevents the overheating issue.

From my experience it seem to be exactly the case - with nvram boot-args="agc=0" enabled the laptop boots at about 50C, when I remove it it boots at 65C (it manages to warm up during boot time) and then when I use the sudo kextload AMDRadeonX3000.kext command it drops again...

To sum up: its seems that nvram boot-args="agc=0" disables the failed AMD chip during the boot process, so manually loading the AMDRadeonX3000.kext file is no longer needed... If someone could confirm this and did some testing, that would be great.

Thanks!

What is your MacOS with the exact version number?

Works for me on Sierra 10.12 (not 10.12.1, 10.12.2, etc - only 10.12)
When I discovered in my tests that agc=0 did not need to move AMDRadeonX3000.kext, then I thought it would be easier.
AMDRadeonX3000.kext inside /System/Library/Extensions -> no freeze Macbook Pro 2011.


Only in Recovery Mode (with SIP enable) - Command + R at boot / Command + R + S at boot:

nvram boot-args="-v agc=0"

or

nvram boot-args="-v agc=9"


Unfortunately Apple changed something in the Sierra and HighSierra that this was no longer possible.
Now the message in boot verbose is "Boot to IG: policy disable!". It is inside AppleMuxControl.kext -> AppleMuxControl executable file.

Now, you need to move AMDRadeonX3000.kext to /System/Library/Extensions-off/ -> not freeze Macbook Pro on boot.

IG = Integrated GPU / Intel GPU.

agc=0 and agc=9 -> power off AMD GPU after login and load AMDRadeonX3000.kext.

agc=1, agc=2, agc=3, agc=4, agc=5, agc=6, agc=7, agc=8 -> do not power off AMD GPU after login and load AMDRadeonX3000.kext.

Unfortunately this agc option is not documented and we have to walk in the dark to know what it does exactly.

In the discussions.apple.com post, user Linc Davis makes a "guess". But it does not mean that agc is connected with the GPU switch.
https://discussions.apple.com/thread/7295722

If you use HighSierra then you can use the AGDCDiagnose command to see if your AMD GPU has been turned off.

IG = Integrate GPU / Intel GPU
EG = Discrete GPU / AMD ou Nvidia

IG = 0 -> power state on
EG = 0 -> power state on
EG = 6 -> power state off

Code:
/System/Library/Extensions/AppleGraphicsControl.kext/Contents/MacOS/AGDCDiagnose -a | grep -i Power
  IG: FB0:on  FB1:N/A FB2:N/A 3D:idle HDA:N/A  Power:on
  EG: FB0:off FB1:off FB2:off 3D:idle HDA:idle Power:off
Policy:off GPUPowerDown:on Backlight Control:on Recovery:on
Power State Machine IG: 0 EG: 6


El Capitan and Sierra:
One of the best app is the Istat Menu that shows the system temperature and GPU temperature.
If the GPU temperature drops to zero or 5 degrees Celsius after load AMDRadeonX3000.kext, then the AMD GPU has been turned off.
The temperature of the system can vary greatly depending on the weather.


Unfortunately I do not have an external GPU. HighSierra 10.12.4 has External GPU support.
It would be interesting to do a test to see if an external GPU works on the Thunderbolt port (Macbook Pro 2011).

Macbook Pro 2011 - HighSierra 10.12.4 - test with External GPU

1 - gpu-power-prefs to AMD GPU -> Thunderbolt port wired to AMD GPU.

2 - Boot Single User Mode (SIP disable) move AMD kexts to another directory -> not freeze Macbook Pro 2011 at boot -> AMD6000Controller.kext.

3 - Boot normal -> gpu-power-prefs to AMD GPU -> load fallback driver -> no AMD kexts inside /System/Library/Extensions -> Properly install the external GPU kexts -> reboot.

4 - Boot normal -> external GPU connected in Thunderbolt port.-> gpu-power-prefs to AMD GPU -> load fallback driver AMD -> no AMD kexts inside /System/Library/Extensions -> use gfxCardStatus app to change to External GPU -> test HDMI port external GPU to external display and test heavy graphics app.

Macbook Pro 2011 -> thunderbolt port -> external GPU -> HDMI port external GPU -> external display.
[doublepost=1528058890][/doublepost]
Okay I got into safemode and lists
Hardware Port Ethernet Device en0
Hardware Port Wifi en1
Hardware Port Thunderport Bridge Device Bridge0

That's it.

So I am back at it today. It works again for some reason in safe mode. I'm trying to back up before i reinsall as you recommened. I still have no idea why it won't boot normally and what fw0 is?

fw0 -> firewire port/device

Boot Safe Mode -> Terminal -> kextstat | grep -i firewire

Normal boot load firewire kexts - see if in safe mode -> no load firewire kexts.

Normal boot - Macbook Pro 2011 - HighSierra 10.12.4:
Code:
kextstat | grep -i firewire
com.apple.iokit.IOFireWireFamily
com.apple.iokit.IOFireWireIP


Kexts FireWire inside /System/Library/Extensions/

Code:
ls -la /System/Library/Extensions/ | grep -i firewire
drwxr-xr-x@   3 root  wheel     96 Jul 15  2017 IOFireWireAVC.kext
drwxr-xr-x@   3 root  wheel     96 Dec 17 15:30 IOFireWireFamily.kext
drwxr-xr-x@   3 root  wheel     96 Dec 17 15:31 IOFireWireIP.kext
drwxr-xr-x@   3 root  wheel     96 Jul 15  2017 IOFireWireSBP2.kext
drwxr-xr-x@   3 root  wheel     96 Dec 17 15:37 IOFireWireSerialBusProtocolTransport.kext


If the problem is firewire kexts -> then move firewire kexts to another directory -> not load on boot -> example move to /System/Library/Extensions-off/ .

1 - Single User Mode (SIP disable) -> change permissions "/" to Read and Write:
Code:
mv -v /System/Library/Extensions/*FireWire*.* /System/Library/Extensions-off/
reboot

Note: FireWire


2 - Boot normal.


What exactly is the result of your nvram -p command?

Example:
Code:
nvram -p

bluetoothInternalControllerInfo    %xxxx%xxx%xx%fa%xx%xx%x%xx%
fmm-computer-name    xxxx
SystemAudioVolumeDB    %80
bluetoothActiveControllerInfo    x%xx%xx%xx%xx%xx%xx
SystemAudioVolume    %80x
backlight-level    %65%00
boot-args    -v
 
Last edited:

Nightwing32

macrumors member
May 5, 2018
36
4
Thanks man, I came so close to buying a Thinkpad x1 this afternoon.

So I am about to boot into safemode. My only question is I'm on ElCapitan, so are these the same commands I put into the terminal?

What is your MacOS with the exact version number?

Works for me on Sierra 10.12 (not 10.12.1, 10.12.2, etc - only 10.12)
When I discovered in my tests that agc=0 did not need to move AMDRadeonX3000.kext, then I thought it would be easier.
AMDRadeonX3000.kext inside /System/Library/Extensions -> no freeze Macbook Pro 2011.

Unfortunately Apple changed something in the Sierra and HighSierra that this was no longer possible.
Now the message in boot verbose is "Boot to IG: policy disable!". It is inside AppleMuxControl.kext -> AppleMuxControl executable file.

Now, you need to move AMDRadeonX3000.kext to /System/Library/Extensions-off/ -> not freeze Macbook Pro on boot.

IG = Integrated GPU / Intel GPU.

agc=0 and agc=9 -> power off AMD GPU after login and load AMDRadeonX3000.kext.

agc=1, agc=2, agc=3, agc=4, agc=5, agc=6, agc=7, agc=8 -> do not power off AMD GPU after login and load AMDRadeonX3000.kext.

Unfortunately this agc option is not documented and we have to walk in the dark to know what it does exactly.

In the discussions.apple.com post, user Linc Davis makes a "guess". But it does not mean that agc is connected with the GPU switch.
https://discussions.apple.com/thread/7295722

If you use HighSierra then you can use the AGDCDiagnose command to see if your AMD GPU has been turned off.

IG = Integrate GPU / Intel GPU
EG = Discrete GPU / AMD ou Nvidia

IG = 0 -> power state on
EG = 0 -> power state on
EG = 6 -> power state off

Code:
/System/Library/Extensions/AppleGraphicsControl.kext/Contents/MacOS/AGDCDiagnose -a | grep -i Power
  IG: FB0:on  FB1:N/A FB2:N/A 3D:idle HDA:N/A  Power:on
  EG: FB0:off FB1:off FB2:off 3D:idle HDA:idle Power:off
Policy:off GPUPowerDown:on Backlight Control:on Recovery:on
Power State Machine IG: 0 EG: 6


El Capitan and Sierra:
One of the best app is the Istat Menu that shows the system temperature and GPU temperature.
If the GPU temperature drops to zero or 5 degrees Celsius after load AMDRadeonX3000.kext, then the AMD GPU has been turned off.
The temperature of the system can vary greatly depending on the weather.


Unfortunately I do not have an external GPU. HighSierra 10.12.4 has External GPU support.
It would be interesting to do a test to see if an external GPU works on the Thunderbolt port (Macbook Pro 2011).

Macbook Pro 2011 - HighSierra 10.12.4 - test with External GPU

1 - gpu-power-prefs to AMD GPU -> Thunderbolt port wired to AMD GPU.

2 - Boot Single User Mode (SIP disable) move AMD kexts to another directory -> not freeze Macbook Pro 2011 at boot -> AMD6000Controller.kext.

3 - Boot normal -> gpu-power-prefs to AMD GPU -> load fallback driver -> no AMD kexts inside /System/Library/Extensions -> Properly install the external GPU kexts -> reboot.

4 - Boot normal -> external GPU connected in Thunderbolt port.-> gpu-power-prefs to AMD GPU -> load fallback driver AMD -> no AMD kexts inside /System/Library/Extensions -> use gfxCardStatus app to change to External GPU -> test HDMI port external GPU to external display and test heavy graphics app.

Macbook Pro 2011 -> thunderbolt port -> external GPU -> HDMI port external GPU -> external display.
[doublepost=1528058890][/doublepost]

fw0 -> firewire port/device

Boot Safe Mode -> Terminal -> kextstat | grep -i firewire

Normal boot load firewire kexts - see if in safe mode -> no load firewire kexts.

Normal boot - Macbook Pro 2011 - HighSierra 10.12.4:
Code:
kextstat | grep -i firewire
com.apple.iokit.IOFireWireFamily
com.apple.iokit.IOFireWireIP


Kexts FireWire inside /System/Library/Extensions/

Code:
ls -la /System/Library/Extensions/ | grep -i firewire
drwxr-xr-x@   3 root  wheel     96 Jul 15  2017 IOFireWireAVC.kext
drwxr-xr-x@   3 root  wheel     96 Dec 17 15:30 IOFireWireFamily.kext
drwxr-xr-x@   3 root  wheel     96 Dec 17 15:31 IOFireWireIP.kext
drwxr-xr-x@   3 root  wheel     96 Jul 15  2017 IOFireWireSBP2.kext
drwxr-xr-x@   3 root  wheel     96 Dec 17 15:37 IOFireWireSerialBusProtocolTransport.kext


If the problem is firewire kexts -> then move firewire kexts to another directory -> not load on boot -> example move to /System/Library/Extensions-off/ .

1 - Single User Mode (SIP disable) -> change permissions "/" to Read and Write:
Code:
mv -v /System/Library/Extensions/*FireWire*.* /System/Library/Extensions-off/
reboot

Note: FireWire


2 - Boot normal.


What exactly is the result of your nvram -p command?

Example:
Code:
nvram -p

bluetoothInternalControllerInfo    %xxxx%xxx%xx%fa%xx%xx%x%xx%
fmm-computer-name    xxxx
SystemAudioVolumeDB    %80
bluetoothActiveControllerInfo    x%xx%xx%xx%xx%xx%xx
SystemAudioVolume    %80x
backlight-level    %65%00
boot-args    -v
 

nsgr

macrumors 6502
May 22, 2017
317
117
Thanks man, I came so close to buying a Thinkpad x1 this afternoon.

So I am about to boot into safemode. My only question is I'm on ElCapitan, so are these the same commands I put into the terminal?

Yes, same commands for Mountain Lion, Lion, Mavericks, El Capitan, Sierra and HighSierra.

What can change are the names of kexts.
Example: some versions of MacOS -> ATIRadeonX3000.kext or AMDRadeonX3000.kext.

For list FireWire kexts -> list files (kexts) -> ls -la /System/Library/Extensions/ | grep -i firewire

For FireWire kextstat -> loaded kexts on boot -> kextstat | grep -i firewire

If you are going to make a new installation, it would be good to erase your entire disk (before backup your personal data to external drive) and then create a new partition.
You have to select the name of the disk (Samsung, Seagate, STS, etc) and not the name of the partition (MacOS, Macintosh HD, etc) in Disk Utility.
Then MacOS installer would create and build a new partition for Recovery (boot Recovery Mode) and another partition for MacOS (normal boot).

ls and mv commands are UNIX/Linux commands -> MacOS -> UNIX
kextstat is MacOS command.

mv command -> move kexts -> used only with Single User Mode with SIP disable. Single User Mode you are logged in as root user (administrator) level permissions.

Do you have any active settings in System Preferences -> Network -> Firewire? My case is FireWire (not connected) -> Using DHCP.
 
Last edited:

mobimation2

macrumors newbie
Jun 10, 2015
5
1
I was able to use the commands posted by AppleMacFinder in the post dated Dec 7, 2009:
Boot to single user mode, then issue commands:

nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
nvram boot-args="-v"
reboot

This seems to have disabled discrete graphics,
(MacBook Pro (17-inch, Late 2011), 2.4GHz Intel Core i7
Now runs "Intel HD Graphics 3000 512 MB".
Serial C02GH3MFDV11

This means an external monitor will not work as long as this setting is in effect.
 

davidescion

macrumors newbie
Dec 3, 2017
4
0
The 2D World
Hello, I have been using various methods to fix my MacBook first the original and then later the grub method, my problem is that my MacBook started to randomly crash and if I forcefully restarted it with the power button it would only display a black screen and the sleep light stays fully on, no chime and no nothing, my solution has been to let the laptop fully discharge and charge it back up, I would just want to know if it's my gpu that is getting worse or if it is just something wrong on the software side of things, I really hope that someone can point me to the right direction
Thanks,
-Davide
 

davidescion

macrumors newbie
Dec 3, 2017
4
0
The 2D World
I fixed all my problems using the resistor method, highly recommend, if you can't do it 85$ is still worth it tbh. Thankfully I know how to solder, now my Mac is almost as good as 13inch models, only difference is I can't reset the nvram which I don't really care about anyway, no more updating problems and no more grub bs
 

FiliAl

macrumors newbie
Jun 4, 2018
2
0
Thank you very much to the thread starter AppleMacFinder and other supporters (GDBO, nsgr, MikeyN) for sharing experience, spending your time and keeping your patience.

I'm a thread reader about a year. I began to fix dGPU failure with AppleMacFinder method, then reinstalled macOS once or twice and applied the fix using GDBO method. As I remember, it was in July-August 2017 after Sierra 10.12.6 was released.

So I used Sierra (10.12.6) for months and checked new information on the forum from time to time. Everything was fine (dGPU was deactivated and powered off) until I decided to install Security Update 2018-002 for Sierra from App Store.

(BTW, I don't remember if I installed Sierra Security Update 2018-001 or not in January... Probably, yes, I did, but I didn't get any issue that time.)

Before update I copied back AMDRadeonX3000.kext to default location (/System/Library/Extensions), then updated the system via App Store. Final reboot after update was successful and I booted into desktop environment.

I didn’t apply LoginHook tweak previously, so I opened the Terminal to check loaded AMD kexts by "kextstat | grep AMD" as I used to do after each boot before manual "kextload AMDRadeonX3000.kext", but no lines were printed… (instead of usual 4 for Sierra).

I booted into Single User Mode, moved updated AMDRadeonX3000.kext from default location, booted normally: the same result, no AMD kexts are loaded. All Info.plist files were inside /System/Library/Extensions/AMD*.kext/Contents/.

I booted into Single User Mode again and updated kextcache by "touch /System/Library/Extensions" command. It ran less than a second.
Next boot showed hundreds errors on Sierra "kext-dev-mode allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext".
I’m pretty sure there were errors with every kext from /System/Library/Extensions.
I found an equal screenshot on Hackintosh users forum.

High Sierra reported slightly different messages started with "Kext with invalid signature (-2147409622) allowed: ...".

I searched on the forum and googled for such a total kext failure on MBP more, but I didn't get any valuable information.

Then I tried to reinstall Sierra and High Sierra for a dozen of times from USB sticks with small changes in installation sequence. I applied MikeyN’s fix on High Sierra 10.13.4 fresh installations and also on HS 10.13.4 updated immediately after installation procedure via App Store. No changes.

Additional information:
  • All kexts have info.plist, I checked it after each installation and update.
  • I erased the whole disk by Disk Utility before each installation of macOS from scratch.
  • After five-six failed installation attempts I erased all partitions on HDD from Ubuntu (live-booted from USB drive) by GParted tool. No new result. So I think it's enough to erase disk using installer’s Disk Utility.
  • System Integrity Protection was disabled before the initial problem I met. And it was disabled every time I stepped over corresponding MikeyN’s guide after each High Sierra installation.
  • There were no color lines, distorted graphics output on screen after SMC and PRAM/NVRAM reset as it was a year ago: only totally blacked screen. I reset NVRAM before new High Sierra installation booted blindly into Single User mode and ran ./force-iGPU-boot.sh which I copied from backup after each OS installation.
  • Every "touch /System/Library/Extensions/" lasts for less a second and even if I wait for 5-10 minutes after that before reboot it leads to "Kext with invalid signature (-2147409622) allowed: ..." on next boot.
I updated the system to 10.13.5 from 10.13.4 with Security Update 2018-001 yesterday. The same result: no kexts are loaded. I haven't "touch"-ed kexts yet, just moved AMDRadeonX3000.kext from default location.

Despaired, I tried to do something stupid, I added kexts calls to /Library/LoginHook/LoadX3000.sh:
Code:
#!/bin/bash
kextload /System/Library/Extensions/AMDLegacyFramebuffer.kext
kextload /System/Library/Extensions/AMDFramebuffer.kext
kextload /System/Library/Extensions/AMD6000Controller.kext
kextload /System/Library/Extensions-off/AMDRadeonX3000.kext
pmset -a force gpuswitch 0
exit 0

After reboot I've got:
Code:
$ kextstat | grep AMD 
  164    2 0xffffff7f83398000 0x122000   0x122000   com.apple.kext.AMDLegacySupport (1.6.6) B7ED5B85-C76E-33EF-BB44-33CA9D9042BB <106 12 11 7 5 4 3 1>
  165    0 0xffffff7f834ba000 0x22000    0x22000    com.apple.kext.AMDLegacyFramebuffer (1.6.6) C17741E6-97E9-3F0B-8EF8-533036EADFFD <164 106 12 11 7 5 4 3 1>
  166    1 0xffffff7f834dc000 0x1ed000   0x1ed000   com.apple.kext.AMDSupport (1.6.6) FCF5E01E-5551-37FF-9238-A91E9116740A <119 106 12 11 7 5 4 3 1>
  167    0 0xffffff7f836c9000 0x29000    0x29000    com.apple.kext.AMDFramebuffer (1.6.6) 6E1C0E44-3AE8-3DF3-B93B-B7D0794433CA <166 106 12 11 7 5 4 3 1>
  168    0 0xffffff7f836f2000 0x12e000   0x12e000   com.apple.kext.AMD6000Controller (1.6.6) 774DEC5B-95D1-3A18-B4D7-0469DAB59E23 <164 106 12 11 5 4 3 1>
  170    0 0xffffff7f838b7000 0x568000   0x568000   com.apple.kext.AMDRadeonX3000 (1.6.6) 15040C17-BF99-32F1-85C5-7C0D409F1288 <169 151 106 12 7 5 4 3 1>

Kext are loaded, but screen brightness is not adjustable, temperature is high, dGPU is on.

Just for information, I tried also:
Code:
#!/bin/bash
kextload /System/Library/Extensions/AMDLegacySupport.kext
kextload /System/Library/Extensions/AMDSupport.kext
kextload /System/Library/Extensions/AMD6000Controller.kext
kextload /System/Library/Extensions/AMDLegacyFramebuffer.kext
kextload /System/Library/Extensions/AMDFramebuffer.kext
kextload /System/Library/Extensions-off/AMDRadeonX3000.kext
pmset -a force gpuswitch 0
exit 0

Code:
$ kextstat | grep AMD 
  164    2 0xffffff7f83398000 0x122000   0x122000   com.apple.kext.AMDLegacySupport (1.6.6) B7ED5B85-C76E-33EF-BB44-33CA9D9042BB <106 12 11 7 5 4 3 1>
  165    1 0xffffff7f834ba000 0x1ed000   0x1ed000   com.apple.kext.AMDSupport (1.6.6) FCF5E01E-5551-37FF-9238-A91E9116740A <118 106 12 11 7 5 4 3 1>
  166    0 0xffffff7f836a7000 0x12e000   0x12e000   com.apple.kext.AMD6000Controller (1.6.6) 774DEC5B-95D1-3A18-B4D7-0469DAB59E23 <164 106 12 11 5 4 3 1>
  167    0 0xffffff7f837d5000 0x22000    0x22000    com.apple.kext.AMDLegacyFramebuffer (1.6.6) C17741E6-97E9-3F0B-8EF8-533036EADFFD <164 106 12 11 7 5 4 3 1>
  168    0 0xffffff7f837f7000 0x29000    0x29000    com.apple.kext.AMDFramebuffer (1.6.6) 6E1C0E44-3AE8-3DF3-B93B-B7D0794433CA <165 106 12 11 7 5 4 3 1>
  170    0 0xffffff7f838b7000 0x568000   0x568000   com.apple.kext.AMDRadeonX3000 (1.6.6) 15040C17-BF99-32F1-85C5-7C0D409F1288 <169 151 106 12 7 5 4 3 1>

I'm sure that it's not enough or it is not correct way to load kexts, but I'm stuck finding right way to set up dGPU at the moment.

It feels I miss something simple or I've got new / combined SW/HW problem.
Need help from community, thanks!
 

nsgr

macrumors 6502
May 22, 2017
317
117
Thank you very much to the thread starter AppleMacFinder and other supporters (GDBO, nsgr, MikeyN) for sharing experience, spending your time and keeping your patience.

I'm a thread reader about a year. I began to fix dGPU failure with AppleMacFinder method, then reinstalled macOS once or twice and applied the fix using GDBO method. As I remember, it was in July-August 2017 after Sierra 10.12.6 was released.

So I used Sierra (10.12.6) for months and checked new information on the forum from time to time. Everything was fine (dGPU was deactivated and powered off) until I decided to install Security Update 2018-002 for Sierra from App Store.

(BTW, I don't remember if I installed Sierra Security Update 2018-001 or not in January... Probably, yes, I did, but I didn't get any issue that time.)

Before update I copied back AMDRadeonX3000.kext to default location (/System/Library/Extensions), then updated the system via App Store. Final reboot after update was successful and I booted into desktop environment.

I didn’t apply LoginHook tweak previously, so I opened the Terminal to check loaded AMD kexts by "kextstat | grep AMD" as I used to do after each boot before manual "kextload AMDRadeonX3000.kext", but no lines were printed… (instead of usual 4 for Sierra).

I booted into Single User Mode, moved updated AMDRadeonX3000.kext from default location, booted normally: the same result, no AMD kexts are loaded. All Info.plist files were inside /System/Library/Extensions/AMD*.kext/Contents/.

I booted into Single User Mode again and updated kextcache by "touch /System/Library/Extensions" command. It ran less than a second.
Next boot showed hundreds errors on Sierra "kext-dev-mode allowing invalid signature -2147409622 0xFFFFFFFF8001212A for kext".
I’m pretty sure there were errors with every kext from /System/Library/Extensions.
I found an equal screenshot on Hackintosh users forum.

High Sierra reported slightly different messages started with "Kext with invalid signature (-2147409622) allowed: ...".

I searched on the forum and googled for such a total kext failure on MBP more, but I didn't get any valuable information.

Then I tried to reinstall Sierra and High Sierra for a dozen of times from USB sticks with small changes in installation sequence. I applied MikeyN’s fix on High Sierra 10.13.4 fresh installations and also on HS 10.13.4 updated immediately after installation procedure via App Store. No changes.

Additional information:
  • All kexts have info.plist, I checked it after each installation and update.
  • I erased the whole disk by Disk Utility before each installation of macOS from scratch.
  • After five-six failed installation attempts I erased all partitions on HDD from Ubuntu (live-booted from USB drive) by GParted tool. No new result. So I think it's enough to erase disk using installer’s Disk Utility.
  • System Integrity Protection was disabled before the initial problem I met. And it was disabled every time I stepped over corresponding MikeyN’s guide after each High Sierra installation.
  • There were no color lines, distorted graphics output on screen after SMC and PRAM/NVRAM reset as it was a year ago: only totally blacked screen. I reset NVRAM before new High Sierra installation booted blindly into Single User mode and ran ./force-iGPU-boot.sh which I copied from backup after each OS installation.
  • Every "touch /System/Library/Extensions/" lasts for less a second and even if I wait for 5-10 minutes after that before reboot it leads to "Kext with invalid signature (-2147409622) allowed: ..." on next boot.
I updated the system to 10.13.5 from 10.13.4 with Security Update 2018-001 yesterday. The same result: no kexts are loaded. I haven't "touch"-ed kexts yet, just moved AMDRadeonX3000.kext from default location.

Despaired, I tried to do something stupid, I added kexts calls to /Library/LoginHook/LoadX3000.sh:
Code:
#!/bin/bash
kextload /System/Library/Extensions/AMDLegacyFramebuffer.kext
kextload /System/Library/Extensions/AMDFramebuffer.kext
kextload /System/Library/Extensions/AMD6000Controller.kext
kextload /System/Library/Extensions-off/AMDRadeonX3000.kext
pmset -a force gpuswitch 0
exit 0

After reboot I've got:
Code:
$ kextstat | grep AMD
  164    2 0xffffff7f83398000 0x122000   0x122000   com.apple.kext.AMDLegacySupport (1.6.6) B7ED5B85-C76E-33EF-BB44-33CA9D9042BB <106 12 11 7 5 4 3 1>
  165    0 0xffffff7f834ba000 0x22000    0x22000    com.apple.kext.AMDLegacyFramebuffer (1.6.6) C17741E6-97E9-3F0B-8EF8-533036EADFFD <164 106 12 11 7 5 4 3 1>
  166    1 0xffffff7f834dc000 0x1ed000   0x1ed000   com.apple.kext.AMDSupport (1.6.6) FCF5E01E-5551-37FF-9238-A91E9116740A <119 106 12 11 7 5 4 3 1>
  167    0 0xffffff7f836c9000 0x29000    0x29000    com.apple.kext.AMDFramebuffer (1.6.6) 6E1C0E44-3AE8-3DF3-B93B-B7D0794433CA <166 106 12 11 7 5 4 3 1>
  168    0 0xffffff7f836f2000 0x12e000   0x12e000   com.apple.kext.AMD6000Controller (1.6.6) 774DEC5B-95D1-3A18-B4D7-0469DAB59E23 <164 106 12 11 5 4 3 1>
  170    0 0xffffff7f838b7000 0x568000   0x568000   com.apple.kext.AMDRadeonX3000 (1.6.6) 15040C17-BF99-32F1-85C5-7C0D409F1288 <169 151 106 12 7 5 4 3 1>

Kext are loaded, but screen brightness is not adjustable, temperature is high, dGPU is on.

Just for information, I tried also:
Code:
#!/bin/bash
kextload /System/Library/Extensions/AMDLegacySupport.kext
kextload /System/Library/Extensions/AMDSupport.kext
kextload /System/Library/Extensions/AMD6000Controller.kext
kextload /System/Library/Extensions/AMDLegacyFramebuffer.kext
kextload /System/Library/Extensions/AMDFramebuffer.kext
kextload /System/Library/Extensions-off/AMDRadeonX3000.kext
pmset -a force gpuswitch 0
exit 0

Code:
$ kextstat | grep AMD
  164    2 0xffffff7f83398000 0x122000   0x122000   com.apple.kext.AMDLegacySupport (1.6.6) B7ED5B85-C76E-33EF-BB44-33CA9D9042BB <106 12 11 7 5 4 3 1>
  165    1 0xffffff7f834ba000 0x1ed000   0x1ed000   com.apple.kext.AMDSupport (1.6.6) FCF5E01E-5551-37FF-9238-A91E9116740A <118 106 12 11 7 5 4 3 1>
  166    0 0xffffff7f836a7000 0x12e000   0x12e000   com.apple.kext.AMD6000Controller (1.6.6) 774DEC5B-95D1-3A18-B4D7-0469DAB59E23 <164 106 12 11 5 4 3 1>
  167    0 0xffffff7f837d5000 0x22000    0x22000    com.apple.kext.AMDLegacyFramebuffer (1.6.6) C17741E6-97E9-3F0B-8EF8-533036EADFFD <164 106 12 11 7 5 4 3 1>
  168    0 0xffffff7f837f7000 0x29000    0x29000    com.apple.kext.AMDFramebuffer (1.6.6) 6E1C0E44-3AE8-3DF3-B93B-B7D0794433CA <165 106 12 11 7 5 4 3 1>
  170    0 0xffffff7f838b7000 0x568000   0x568000   com.apple.kext.AMDRadeonX3000 (1.6.6) 15040C17-BF99-32F1-85C5-7C0D409F1288 <169 151 106 12 7 5 4 3 1>

I'm sure that it's not enough or it is not correct way to load kexts, but I'm stuck finding right way to set up dGPU at the moment.

It feels I miss something simple or I've got new / combined SW/HW problem.
Need help from community, thanks!

kext-dev-mode allowing invalid signature -> it is normal message.

Try FGuarani method to move only AMDRadeonX3000.kext to /System/Library/Extensions-off/ in Recovery Mode (Command + R at boot) if you can not install again Sierra/HighSierra.

The kexts are loaded by Device ID -> System Information -> AMD Radeon HD 6750M - Device ID: 0x6741

AMD6000Conroller.kext (Info.plist) match with Device ID: 0x6741? Yes, then MacOS load AMD6000Controller.kext on boot.


Install Sierra/HighSierra + FGuarani method:

0 - NVRAM gpu-power-prefs to Intel GPU otherwise -> freeze gray screen Sierra/HighSierra installer.

1 - Load Sierra/HighSierra installer -> Utilities -> Terminal -> Enable SIP -> csrutil enable -> nvram boot-args="-v" -> reboot.

2 - Boot again from Sierra/HighSierra installer -> Disk Utility -> erase all disk -> create 1 or 2 partitions -> my case Partition1-MacOS and Partition2-Backup (personal data) -> close Disk Utility and install Sierra/HighSierra. Remember: backup your personal data before erase all disk.

My example -> partition with Sierra/HighSierra installed on SSD -> name/label partition -> MacOS .

3 - Half installation Sierra/HighSierra -> Macbook Pro 2011 freeze and overheating -> try load AMDRadeonX3000.kext on boot after Rebuild kextcache -> if not auto restart -> force shutdown -> press Power Button.

Freeze Macbook Pro 2011 message: gIOScreenLockState 3

4 - Boot again with Sierra/HighSierra installer -> Disk Utility -> choose your partition name/label MacOS and mount.

5 - Close Disk Utility -> menu Utilities -> Terminal.

6 - Now your MacOS half installed -> on /Volumes/MacOS .

7 - Create directory to move AMDRadeonX3000.kext -> /Volumes/MacOS/System/Library/Extensions-off/
Code:
mkdir -v /Volumes/MacOS/System/Library/Extensions-off

8 - Move AMDRadeonX3000.kext
Code:
mv -v /Volumes/MacOS/System/Library/Extensions/AMDRadeonX3000.kext /Volumes/MacOS/System/Library/Extensions-off/

9 - Verify with ls (list files/directories) if AMDRadeonX3000.kext -> inside /Volumes/MacOS/System/Library/Extensions-off/
Code:
ls -la /Volumes/MacOS/System/Library/Extensions-off/

10 - Close Terminal -> Disk Utility -> unmount MacOS partition -> close Disk Utility -> reboot.
Sometimes -> message Partition Busy -> not unmount -> wait a minute and try again.

No need touch command with FGuarani method.

11 - Boot normal and continue installation Sierra/HighSierra -> after finish install Sierra/HighSierra -> login screen -> verify if AMD kexts are loaded:
Code:
kextstat | grep AMD

sudo kextload /System/Library/Extensions-off/AMDRadeonX3000.kext


Last update HighSierra 10.13.4 from App Store had 5 normal reboots until completing all the update.

Always have an AMDRadeonX3000.kext complete with Info.plist for Plan B.
The latest security update for HighSierra 10.3.4 has AMDRadeonX3000.kext without Info.plist. This kext will not be loaded with kextload.

If you did an update and after the reboot in Macbook Pro 2011 did not freeze, then probably Apple put an AMDRadeonX3000.kext without Info.plist.
 
Last edited:

FiliAl

macrumors newbie
Jun 4, 2018
2
0
Thank you for the response!

I'm a bit calmed down now, because I don't have to worry about invalid kext signatures, OK.
Try FGuarani method to move only AMDRadeonX3000.kext to /System/Library/Extensions-off/ in Recovery Mode (Command + R at boot) if you can not install again Sierra/HighSierra.

The kexts are loaded by Device ID -> System Information -> AMD Radeon HD 6750M - Device ID: 0x6741

AMD6000Conroller.kext (Info.plist) match with Device ID: 0x6741? Yes, then MacOS load AMD6000Controller.kext on boot.

But I'm slightly confused after reading the first part of your message: I've already done the recommendation you proposed. I moved AMDRadeonX3000.kext to /System/Library/Extensions-off/ after every High Sierra installation/update and never moved any other kext from /System/Library/Extensions.

MBP/macOS state after each Sierra/High Sierra installation since I've met the problem is:
  1. HW is MBP 15" Early 2011 with Radeon HD 6750M.
  2. No AMD*.kext is loaded immediately after OS installation.
  3. All AMD*.kext folders are in /System/Library/Extensions/.
  4. I move only AMDRadeonX3000.kext to /System/Library/Extensions-off/ each time.
  5. Every AMD*.kext has Info.plist.
  6. MBP screen is absolutely black after NVRAM reset, no distortion, etc. is displayed (as it was months ago).
  7. dGPU is not presented in System Information, because of point "1" I think.
  8. dGPU is powered on.
Code:
$ /System/Library/Extensions/AppleGraphicsControl.kext/Contents/MacOS/AGDCDiagnose -a | grep -i Power
  IG: FB0:off FB1:N/A FB2:N/A 3D:idle HDA:N/A  Power:on
  EG: FB0:off FB1:off FB2:off 3D:idle HDA:N/A  Power:on
Policy:off GPUPowerDown:on Backlight Control:on Recovery:on
Power State Machine IG: 0 EG: 0

Anyway, I'll try to install High Sierra 10.13.5 from USB drive using your recipe to exclude current possible kexts/configuration/system mess or probable misunderstanding of your first advice.
Thanks a lot!
 

nsgr

macrumors 6502
May 22, 2017
317
117
Thank you for the response!

I'm a bit calmed down now, because I don't have to worry about invalid kext signatures, OK.


But I'm slightly confused after reading the first part of your message: I've already done the recommendation you proposed. I moved AMDRadeonX3000.kext to /System/Library/Extensions-off/ after every High Sierra installation/update and never moved any other kext from /System/Library/Extensions.

MBP/macOS state after each Sierra/High Sierra installation since I've met the problem is:
  1. HW is MBP 15" Early 2011 with Radeon HD 6750M.
  2. No AMD*.kext is loaded immediately after OS installation.
  3. All AMD*.kext folders are in /System/Library/Extensions/.
  4. I move only AMDRadeonX3000.kext to /System/Library/Extensions-off/ each time.
  5. Every AMD*.kext has Info.plist.
  6. MBP screen is absolutely black after NVRAM reset, no distortion, etc. is displayed (as it was months ago).
  7. dGPU is not presented in System Information, because of point "1" I think.
  8. dGPU is powered on.
Code:
$ /System/Library/Extensions/AppleGraphicsControl.kext/Contents/MacOS/AGDCDiagnose -a | grep -i Power
  IG: FB0:off FB1:N/A FB2:N/A 3D:idle HDA:N/A  Power:on
  EG: FB0:off FB1:off FB2:off 3D:idle HDA:N/A  Power:on
Policy:off GPUPowerDown:on Backlight Control:on Recovery:on
Power State Machine IG: 0 EG: 0

Anyway, I'll try to install High Sierra 10.13.5 from USB drive using your recipe to exclude current possible kexts/configuration/system mess or probable misunderstanding of your first advice.
Thanks a lot!


If your AMD GPU does not appear in System Information, then AMD kexts will not be loaded at boot. And if you kextload manually after login, then they will be loaded but will not make any difference.

The AMD GPU should be listed in System Information even if no AMD kext is loaded.

In the case of GRUB Solution the AMD GPU will not be listed in System Information.

During boot MacOS checks the hardware installed through Device ID.
MacOS confronts this Device ID with the kexts inside /System/Library/Extensions/ by reading the Info.plist of each kext or reading kextcache.

The only way I know of not showing the AMD GPU in System Information is through GRUB Solution - #1.
If you did not do the GRUB Solution, then you might have a problem with the Logic Board.

You are using the original Mac EFI or you changed it by rEFInd or other EFI?

Sometimes one of the USB ports stops working and I do an SMC Reset and this USB port is recognized again in MacOS.

I do the SMC Reset but I keep pressing for 30 seconds. I release all the keys and the Power button and then I repeat the procedure.

Make a SMC reset:

After your Mac shuts down, press:

1 - Press Shift-Control-Option on the left side of the built-in keyboard, then press the power button at the same time. Hold these keys and the power button for 10 seconds.

2 - Press the power button again to turn on your Mac.

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


Macbook Pro / AIr - SMC Reset / PRAM Reset
 
Last edited:

Lloyd22

macrumors newbie
Apr 28, 2017
8
3
Hi everyone,

I come to this thread every few months with a new problem. After doing all the fixes, baking the damn thing, glitches are back...

I'm on El Capitan, wasn't having any issues for months, using the iGPU. Yesterday, while the Mac was running, irridescent glitches just suddenly appeared on the screen. The Mac is still operational, I can reboot, gfxcardstatus is still on the iGPU and I deleted the AMD Kexts again just in case.
But nothing changes, glitches are still present, even in Single User mode (see screen attached).

Are the two GPUs dead now? I really don't get it...
If someone has a hint...
Thank you!
 

Attachments

  • IMG_20180606_093405.jpg
    IMG_20180606_093405.jpg
    557.8 KB · Views: 268
  • IMG_20180606_101302.jpg
    IMG_20180606_101302.jpg
    615 KB · Views: 269

Tonymakkaroni

macrumors newbie
May 31, 2018
3
0
after moving only the AMDRadeonX*.kext Files my MacBook Pro Early 2011 won't wake up after sleeping mode, when I manually load the RadeonX3000 kext and discharge my power cable. When I plugged it in it starts normal. And when I don't load the RadeonX3000 it starts normal after sleeping mode even when it is charged or not.

Please help!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.