MBP 1,1-10,2 Force 2011 MacBook Pro 8,2 with failed AMD GPU to ALWAYS use Intel integrated GPU (EFI variable fix)

[nsgr]

It seems like a clean install might be one of the last options. I will try it in the morning and report back.

You didn't list AMD(Legacy)Framebuffer.kext, is that one not relevant anymore or should I load that one too?

I put the AMD kexts that had their AMD ID 6740.

Yes, the AMDLegacyFrammebuffer.kext should be loaded. I think it will be charged by dependence. If it is not, load it manually.

Remember, take a test before with kexts that were moved after installation. Forget the old kexts that you already did test.

Example:

Clean install Sierra -> put AMD / ATI kexts 1.5.1 in /System/Library/Extensions

Move this kexts -> /kexts-sierra-1.5.1-install

Then use this kexts to do the tests (load manual).

 

[SirMeowington5]

Okay, sounds good. I will let you know how it goes in the morning.

I put the AMD kexts that had their AMD ID 6740.

Yes, the AMDLegacyFrammebuffer.kext should be loaded. I think it will be charged by dependence. If it is not, load it manually.

Remember, take a test before with kexts that were moved after installation. Forget the old kexts that you already did test.

Example:

Clean install Sierra -> put AMD / ATI kexts 1.5.1 in /System/Library/Extensions

Move this kexts -> /kexts-sierra-1.5.1-install

Then use this kexts to do the tests (load manual).

 

[rlebleu]

Did you first try/ have any success loading the Kexts through Terminal while MacOS was already running?

I'm wondering now if maybe there's a difference between having them auto-load at login and manually loading them through Terminal... Although there shouldn't really be a difference as long as they show up as loaded in kextstat ...

I'm starting to think that fully re-installing OS X and trying FGuarini's method for 17" models might be one of my last options...



[doublepost=1499284965][/doublepost]Hopefully this pings you but have you encountered any thermal issues in your 17" model FGuarini?

Actually no. For me getting the AMD texts out of System/Library/Extensions were the key to making sure the MBP would not try to run the dGPU.

I began this trip with the Archlnux ISO because I was unable to boot whithout triggering the dGPU. Booting from the USB drive allowed me the have a stable working environment to get the AMD kexts safely moved out to AMD_Kexts folder. I learned later that simply booting with CMD-S more or less achieves the same result. The using the printf method of writing the desired boot to integrated GPU did the job of always booting to the iGPU. Again, I learned later that there was an easier way by using the sudo nvram method...to set the boot parameters to select iGPU.

Later I learned from nsgr that the key kext to getting thermal control was the AMDRadeonX3000.kext, but it didn't play well with the 1.51 AMD Kexts, and earlier versions did. That's when I created an install sierra USB to use as a source. Using nsgr's instructions, I copied the 1.44 versions from the USB disk to the hard disk, then tried loading AMDRadeon X3000 (1.51) from my AMD_Kexts folder, it then loaded fine with no errors, and the temps dropped!

It must be frustrating for you following the same instructions unsuccesfully... But I think we have different dGPU's and the combination of kexts may be different.

If you are able to single user boot (Cmd-S) I don't think you need the Archlinux boot to achieve to kexts change.

 

[nsgr]

Okay, sounds good. I will let you know how it goes in the morning.

Do not forget:

Gfxcardstatus Steve Schow v. 2.4.31 for Sierra.

Before load kexts AMD, make sure the Intel video card stays active even with gfxcardstatus -> Discrete Only.

Then gfxcardstatus -> Integrated Only.


My tests:

Gfxcardstatus -> Integrated Only

System Preferences -> Energy Saver -> Automatic graphics switching: checked

 

[SirMeowington5]

Ah, sorry for the confusion. The three critical kexts were the ones I was referring to (AMDSupport.kext, AMDFramebuffer.kext and AMD6000Controller.kext). You moved those back in to the Extensions folder to have them auto-load whereas I'm loading them manually through Terminal.

I was wondering if you had the same success autoloading those three followed by manually loading the AMDRadeonX300 kext compared to manually loading all four of them through Terminal.

Actually no. For me getting the AMD texts out of System/Library/Extensions were the key to making sure the MBP would not try to run the dGPU.

I began this trip with the Archlnux ISO because I was unable to boot whithout triggering the dGPU. Booting from the USB drive allowed me the have a stable working environment to get the AMD kexts safely moved out to AMD_Kexts folder. I learned later that simply booting with CMD-S more or less achieves the same result. The using the printf method of writing the desired boot to integrated GPU did the job of always booting to the iGPU. Again, I learned later that there was an easier way by using the sudo nvram method...to set the boot parameters to select iGPU.

Later I learned from nsgr that the key kext to getting thermal control was the AMDRadeonX3000.kext, but it didn't play well with the 1.51 AMD Kexts, and earlier versions did. That's when I created an install sierra USB to use as a source. Using nsgr's instructions, I copied the 1.44 versions from the USB disk to the hard disk, then tried loading AMDRadeon X3000 (1.51) from my AMD_Kexts folder, it then loaded fine with no errors, and the temps dropped!

It must be frustrating for you following the same instructions unsuccesfully... But I think we have different dGPU's and the combination of kexts may be different.

If you are able to single user boot (Cmd-S) I don't think you need the Archlinux boot to achieve to kexts change.

[doublepost=1499294334][/doublepost]Okay, I'll make sure to check this before loading any of the kexts.

Do not forget:

Gfxcardstatus Steve Schow v. 2.4.31 for Sierra.

Before load kexts AMD, make sure the Intel video card stays active even with gfxcardstatus -> Discrete Only.

Then gfxcardstatus -> Integrated Only.


My tests:

Gfxcardstatus -> Integrated Only

System Preferences -> Energy Saver -> Automatic graphics switching: checked

 

[rlebleu]

Ah, sorry for the confusion. The three critical kexts were the ones I was referring to (AMDSupport.kext, AMDFramebuffer.kext and AMD6000Controller.kext). You moved those back in to the Extensions folder to have them auto-load whereas I'm loading them manually through Terminal.

I was wondering if you had the same success autoloading those three followed by manually loading the AMDRadeonX300 kext compared to manually loading all four of them through Terminal.




[doublepost=1499294334][/doublepost]Okay, I'll make sure to check this before loading any of the kexts.

I would put all four to autoload, but when I tried it, the MBP tried to wake up the dGPU. So the Radeon is only loaded after login... Never had to manually load the other three...

 

[nsgr]

Ah, sorry for the confusion. The three critical kexts were the ones I was referring to (AMDSupport.kext, AMDFramebuffer.kext and AMD6000Controller.kext). You moved those back in to the Extensions folder to have them auto-load whereas I'm loading them manually through Terminal.

I was wondering if you had the same success autoloading those three followed by manually loading the AMDRadeonX300 kext compared to manually loading all four of them through Terminal.




[doublepost=1499294334][/doublepost]Okay, I'll make sure to check this before loading any of the kexts.

My AMDSupport.kext, AMDFramebuffer.kext and AMD6000Controller.kext are 1.4.8 from Sierra 10.12.14 installer pendrive.

If I only had these kexts (AMDSupport.kext, AMDFramebuffer.kext and AMD6000Controller.kext) in version 1.5.1, then I would have to load them manually with each boot. IOConsoleUsers IOScreenLockState error.

The AMDRadeonX3000.kext 1.5.1 I have to manually load every boot.

I tried loading AMDRadeonX3000.kext 1.4.8 - from the mac OS Sierra Combo Update 10.12.2 but it gives error (unresolved symbols).

I only had the option to load AMDRadeonX3000.kext 1.5.1. (manual) .

I will have to do a new installation of the Sierra 10.12.3 system because my Recovery Mode is corrupted. I can not get into Recovery Mode (Command + R) or Recovery Mode only text (Command + R + S).

So I'm going to move the AMD / ATI 1.5.1 kexts that have been installed (/System/Library/Extensions) to a new folder.

Then I'll try to manually load all the AMD kexts 1.5.1 and see what happens.

AMDRadeonX3000.kext - 1.5.1
AMD6000Controller.kext - 1.5.1
AMDLegacyFramebuffer.kext - 1.5.1
AMDLegacySupport.kext - 1.5.1

 

[rlebleu]

My AMDSupport.kext, AMDFramebuffer.kext and AMD6000Controller.kext are 1.4.8 from Sierra 10.12.14 installer pendrive.

If I only had these kexts (AMDSupport.kext, AMDFramebuffer.kext and AMD6000Controller.kext) in version 1.5.1, then I would have to load them manually with each boot. IOConsoleUsers IOScreenLockState error.

The AMDRadeonX3000.kext 1.5.1 I have to manually load every boot.

I tried loading AMDRadeonX3000.kext 1.4.8 - from the mac OS Sierra Combo Update 10.12.2 but it gives error (unresolved symbols).

I only had the option to load AMDRadeonX3000.kext 1.5.1. (manual) .

I will have to do a new installation of the Sierra 10.12.3 system because my Recovery Mode is corrupted. I can not get into Recovery Mode (Command + R) or Recovery Mode only text (Command + R + S).

So I'm going to move the AMD / ATI 1.5.1 kexts that have been installed (/System/Library/Extensions) to a new folder.

Then I'll try to manually load all the AMD kexts 1.5.1 and see what happens.

AMDRadeonX3000.kext - 1.5.1
AMD6000Controller.kext - 1.5.1
AMDLegacyFramebuffer.kext - 1.5.1
AMDLegacySupport.kext - 1.5.1

In my case, as soon as I loaded AMDRadeonX3000.kext V1.51 my temperatures began to drop. No further action required... I don't think I have a 1.48 version of that kext...

 

[nilrem77]

Can someone help me set up a "batch" file so I can run a script when creating the EFIVAR variable.

Thanks

 

[SirMeowington5]

Okay, I have completely reinstalled MacOS. I didn't restore a Time Machine backup or anything like that so it's completely vanilla.

Memory usage still shows as high, but this is normal from what I read on the internet. This is simply the way OS X handles memory allocation.

The pressure graph is green, so there isn't actually anything using a lot of memory, it's just the way OSX reserves memory. Actual memory usage according to iSat is 22%.


I managed to load sudo kextload AMDLegacySupport.kext without any issues but I get the dependency error with AMDLegacyFramebuffer.kext and AMD6000Controller.kext.

I ran sudo kextutil -n to find the dependency and I get the error message "Dependency Resolution Failures: No kexts found for these libraries: com.apple.kext.AMDLegacySupport". But if I run kextstat I can see that AMDLegacySupport.kext is loaded, so I don't understand why it is complaining...

So instead I loaded them using sudo kextutil -r /AMD_Kexts AMDLegacyFramebuffer.kext & AMD6000Controller.kext. Kextstat shows them as loaded.

I then sudo kextload AMDRadeonX3000.kext, kextstat also confirms loaded.

Still no changes to thermals at this point. Idle @ around 53C.


I tried moving AMDLegacySupport.kext, AMDLegacyFramebuffer.kext & AMD6000Controller.kext back into the Extensions folder so that they auto-load and then manually loading the AMDRadeonX3000.kext. Kextstat shows them all as loaded but also, still no change to thermals using this method.

Do not forget:

Gfxcardstatus Steve Schow v. 2.4.31 for Sierra.

Before load kexts AMD, make sure the Intel video card stays active even with gfxcardstatus -> Discrete Only.

Then gfxcardstatus -> Integrated Only.


My tests:

Gfxcardstatus -> Integrated Only

System Preferences -> Energy Saver -> Automatic graphics switching: checked

 

[Matejh]

Anyone tried this solution with High Sierra Beta?

 

[tommyball]

I've read through the thread and am wondering (considering the discussion between SirMeowington5, rlebleu & nsgr regarding temps) if following AppleMacFinder/FGuarini's method is sufficient to get a working solution.

My 15" 2011 (Sierra 10.12.5, AMD 6750) has the GPU issue again (already repaired once by Apple in Nov. 2015) and I can no longer use it for work (heavy Photoshop design), so long story short, I'm trading it to a friend to use for email, browsing, and backing up an iPhone to Photos. He is not going to want to have to manually load any extensions on startups or do any sort of programming, so I'm hoping that if I go through AppleMacFinder/FGuarini's approach, that will be enough to get him going.

Thanks to everyone here for all the work/info.suggestions!

 

[nsgr]

Okay, I have completely reinstalled MacOS. I didn't restore a Time Machine backup or anything like that so it's completely vanilla.

Memory usage still shows as high, but this is normal from what I read on the internet. This is simply the way OS X handles memory allocation.

The pressure graph is green, so there isn't actually anything using a lot of memory, it's just the way OSX reserves memory. Actual memory usage according to iSat is 22%.


I managed to load sudo kextload AMDLegacySupport.kext without any issues but I get the dependency error with AMDLegacyFramebuffer.kext and AMD6000Controller.kext.

I ran sudo kextutil -n to find the dependency and I get the error message "Dependency Resolution Failures: No kexts found for these libraries: com.apple.kext.AMDLegacySupport". But if I run kextstat I can see that AMDLegacySupport.kext is loaded, so I don't understand why it is complaining...

So instead I loaded them using sudo kextutil -r /AMD_Kexts AMDLegacyFramebuffer.kext & AMD6000Controller.kext. Kextstat shows them as loaded.

I then sudo kextload AMDRadeonX3000.kext, kextstat also confirms loaded.

Still no changes to thermals at this point. Idle @ around 53C.


I tried moving AMDLegacySupport.kext, AMDLegacyFramebuffer.kext & AMD6000Controller.kext back into the Extensions folder so that they auto-load and then manually loading the AMDRadeonX3000.kext. Kextstat shows them all as loaded but also, still no change to thermals using this method.

1- I did a new installation of Sierra 10.12.3.

2 - Then I removed the AMD 1.4.8 kexts to not freeze the screen in IOConsoleUsers IOScreenLockState.
That was weird. Although the Sierra installer kexts AMD are 1.4.8 and the installation kexts on the hard disk are 1.4.8.
But the AMD 1.4.8 kexts installed on the hard disk freeze the screen in IOConsoleUsers IOScreenLockState.

Then I put the kexts AMD 1.4.8 from the Sierra installer (pendrive) and those kexts do not freeze the screen.


3 - I tried to manually load all kexts 1.4.8 but the temperature did not drop.

4 - Then I installed the Sierra Combo Update 10.12.5 macOS to update the kexts for version 1.5.1.

5 - Removed the kexts AMD 1.5.1 to not freezing the screen in IOConsoleUsers IOScreenLockState

6 - I tried to manually load all the AMD 1.5.1 kexts but the temperature did not drop.

7 - I placed the Sierra installer kexts AMD 1.4.8 (pendrive) in /System/Library/Extensions.

8 - After the AMD 1.4.8 kexts loaded by the system, I manually loaded the AMDRadeonX3000.kext 1.5.1 and then the temperature dropped.

/System/Library/Extensions

AMDLegacySupport.kext - 1.4.8 - pendrive installer Sierra 10.12.3

AMD6000Controller.kext - 1.4.8 - pendrive installer Sierra 10.12.3

AMDFramebuffer.kext - 1.4.8 - pendrive installer Sierra 10.12.3


Load manual
AMDRadeonX3000.kext - 1.5.1
[doublepost=1499366328][/doublepost]

I've read through the thread and am wondering (considering the discussion between SirMeowington5, rlebleu & nsgr regarding temps) if following AppleMacFinder/FGuarini's method is sufficient to get a working solution.

My 15" 2011 (Sierra 10.12.5, AMD 6750) has the GPU issue again (already repaired once by Apple in Nov. 2015) and I can no longer use it for work (heavy Photoshop design), so long story short, I'm trading it to a friend to use for email, browsing, and backing up an iPhone to Photos. He is not going to want to have to manually load any extensions on startups or do any sort of programming, so I'm hoping that if I go through AppleMacFinder/FGuarini's approach, that will be enough to get him going.

Thanks to everyone here for all the work/info.suggestions!

Some people have temperature problems and others do not have this problem. Even with the exact same model Macbook Pro.

My Macbook Pro Early 2011 - Intel HD 3000 - AMD 6750 -> problem temperature -> load kexts AMD.
Other people with this same model of Macbook Pro did not have temperature problem -> No need to load the AMD kexts.

 

[rlebleu]

Graphics/Displays:

Intel HD Graphics 3000:

Chipset Model: Intel HD Graphics 3000
Type: GPU
Bus: Built-In
VRAM (Dynamic, Max): 512 MB
Vendor: Intel (0x8086)
Device ID: 0x0126
Revision ID: 0x0009
Automatic Graphics Switching: Supported
gMux Version: 1.9.24

Displays:

Color LCD:
Display Type: LCD
Resolution: 1920 x 1200
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Automatically Adjust Brightness: Yes


AMD Radeon HD 6770M:

Chipset Model: AMD Radeon HD 6770M
Type: GPU
Bus: PCIe
PCIe Lane Width: x8
VRAM (Total): 1024 MB
Vendor: ATI (0x1002)
Device ID: 0x6740
Revision ID: 0x0000
ROM Revision: 113-C0170L-573
Automatic Graphics Switching: Supported
gMux Version: 1.9.24
EFI Driver Version: 01.00.573

system_profiler -detailLevel full SPDisplaysDataType

Graphics/Displays:

Intel HD Graphics 3000:

Chipset Model: Intel HD Graphics 3000
Type: GPU
Bus: Built-In
VRAM (Dynamic, Max): 512 MB
Vendor: Intel (0x8086)
Device ID: 0x0126
Revision ID: 0x0009
Automatic Graphics Switching: Supported
gMux Version: 1.9.24

Displays:

Color LCD:
Display Type: LCD
Resolution: 1920 x 1200
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Automatically Adjust Brightness: Yes


AMD Radeon HD 6770M:

Chipset Model: AMD Radeon HD 6770M
Type: GPU
Bus: PCIe
PCIe Lane Width: x8
VRAM (Total): 1024 MB
Vendor: ATI (0x1002)
Device ID: 0x6740
Revision ID: 0x0000
ROM Revision: 113-C0170L-573
Automatic Graphics Switching: Supported
gMux Version: 1.9.24
EFI Driver Version: 01.00.573

Just for fun, I ran this command on my Late 2011 MBP, and was surprised at the differences...

My Intel i7 CPU ID was 0x0116 vs 0x0126
My gMux version was 1.9.23 vs 1.9.24
My Display resolution was 1440x900 vs 1920x1200
My AMD Radeon was HD6750M vs HD1670M
My VRAM was 512mb vs 1024mb
My device number was 0x6741 vs 0x1640

I have no idea what this means, but it seemed to me there would be different commands needed to manage these chips...

 

[nsgr]

system_profiler -detailLevel full SPDisplaysDataType



Just for fun, I ran this command on my Late 2011 MBP, and was surprised at the differences...

My Intel i7 CPU ID was 0x0116 vs 0x0126
My gMux version was 1.9.23 vs 1.9.24
My Display resolution was 1440x900 vs 1920x1200
My AMD Radeon was HD6750M vs HD1670M
My VRAM was 512mb vs 1024mb
My device number was 0x6741 vs 0x1640

I have no idea what this means, but it seemed to me there would be different commands needed to manage these chips...

Would not be:

My AMD Radeon was HD6750M vs HD6770M

My device number was 0x6741 vs 0x6140

 

[SirMeowington5]

In step 2 do you mean that the Sierra installer kexts were 1.4.8 but the ones on the hard disk were 1.5.1?

I will try the 10.12.3 v1.4.8 kexts now to see if there is any difference.

1- I did a new installation of Sierra 10.12.3.

2 - Then I removed the AMD 1.4.8 kexts to not freeze the screen in IOConsoleUsers IOScreenLockState.
That was weird. Although the Sierra installer kexts AMD are 1.4.8 and the installation kexts on the hard disk are 1.4.8.
But the AMD 1.4.8 kexts installed on the hard disk freeze the screen in IOConsoleUsers IOScreenLockState.

Then I put the kexts AMD 1.4.8 from the Sierra installer (pendrive) and those kexts do not freeze the screen.


3 - I tried to manually load all kexts 1.4.8 but the temperature did not drop.

4 - Then I installed the Sierra Combo Update 10.12.5 macOS to update the kexts for version 1.5.1.

5 - Removed the kexts AMD 1.5.1 to not freezing the screen in IOConsoleUsers IOScreenLockState

6 - I tried to manually load all the AMD 1.5.1 kexts but the temperature did not drop.

7 - I placed the Sierra installer kexts AMD 1.4.8 (pendrive) in /System/Library/Extensions.

8 - After the AMD 1.4.8 kexts loaded by the system, I manually loaded the AMDRadeonX3000.kext 1.5.1 and then the temperature dropped.

/System/Library/Extensions

AMDLegacySupport.kext - 1.4.8 - pendrive installer Sierra 10.12.3

AMD6000Controller.kext - 1.4.8 - pendrive installer Sierra 10.12.3

AMDFramebuffer.kext - 1.4.8 - pendrive installer Sierra 10.12.3


Load manual
AMDRadeonX3000.kext - 1.5.1
[doublepost=1499366328][/doublepost]

Some people have temperature problems and others do not have this problem. Even with the exact same model Macbook Pro.

My Macbook Pro Early 2011 - Intel HD 3000 - AMD 6750 -> problem temperature -> load kexts AMD.
Other people with this same model of Macbook Pro did not have temperature problem -> No need to load the AMD kexts.

 

[nsgr]

It seems like a clean install might be one of the last options. I will try it in the morning and report back.

You didn't list AMD(Legacy)Framebuffer.kext, is that one not relevant anymore or should I load that one too?

I did not oad AMDLegacyFramebufer.kext. It also was not loaded by the system.

The AMDRadeonX3000.kext was loaded manually with the kextload without the -r.


cd /kexts-AMD-1.5.1

sudo kextload AMDRadeonX3000.kext


My current kextstat - temperature 38 degrees Celsius.


kextstat | grep AMD

com.apple.kext.AMDSupport (1.4.8) - installer pendrive Sierra 10.12.3

com.apple.kext.AMD6000Controller (1.4.8) - installer pendrive Sierra 10.12.3

com.apple.kext.AMDFramebuffer (1.4.8) - installer pendrive Sierra 10.12.3

com.apple.AMDRadeonX3000 (1.5.1) - mac OS Sierra Combo Update 10.12.5
[doublepost=1499368408][/doublepost]

In step 2 do you mean that the Sierra installer kexts were 1.4.8 but the ones on the hard disk were 1.5.1?

I will try the 10.12.3 v1.4.8 kexts now to see if there is any difference.

My installation of Sierra 10.12.3 was very strange. Installation done without being connected to the Internet.

Sierra 10.12.3 installer (pendrive) - kexts AMD 1.4.8 - kexts AMD works with /System/Library/Extensions

kexts AMD 1.4.8 installed hard disk by installer - kexts AMD not work with /System/Library/Extensions

Yes, the kexts AMD 1.4.8 pendrive and kext AMD 1.4.8 installed on the hard disk have different behaviors with /System/Library/Extensions

 

[Bonaire]

Correct me if I'm wrong after reading so many possible commands and methods. The conclusion is that if I want the temperature to drop I do this (the short version of the procedure):

I downloaded the 1.4.8 versions of the AMD kexts nsgr made available earlier in a zip from the 10.12.3 pendrive and copied them on a USB stick (MacOS Extended). Now I boot in Recovery mode and go to Terminal to install the three AMD kexts with the cp -v -r /Volumes (etc) command in System/Library/Extensions.

After the reboot I load the AMDRadeonX3000.kext manually in Terminal into the disabled extensions directory.

FYI: I run 10.12.5 and the temperature of my MBP while working is 60-65 degrees with an occasional peek tot 70+. When just reading a text it is around 50-55 degrees and waking the MBP from sleep it starts at approximately 40 degrees, slowly increasing to 50.
Still not sure if these temperatures are harmful to the MBP, except for only being able to work 1,5 - 2 hours on a full battery.

 

[SirMeowington5]

Oh okay, I understand now.

So I tried the 1.4.8 kexts now from the 10.12.3 installer with no difference in temperature.

Udate: okay, with the 1.4.8 kexts maybe there is a 3C decrease in idle temperature. If I leave it long enough it dropped to 50C which is the lowest it's been during all this testing. I'm going to reboot and load the kexts again to see if it will drop bellow 53 again

Update 2: Eh, so the 1.4.8 kexts make a very very small difference, 51C idle vs 53C.

But side question. Didn't you establish earlier that for my hardware I needed the Legacy kexts? Those don't exist in the 10.12.1 and 10.12.3 installer...

I did not oad AMDLegacyFramebufer.kext. It also was not loaded by the system.

The AMDRadeonX3000.kext was loaded manually with the kextload without the -r.


cd /kexts-AMD-1.5.1

sudo kextload AMDRadeonX3000.kext


My current kextstat - temperature 38 degrees Celsius.


kextstat | grep AMD

com.apple.kext.AMDSupport (1.4.8) - installer pendrive Sierra 10.12.3

com.apple.kext.AMD6000Controller (1.4.8) - installer pendrive Sierra 10.12.3

com.apple.kext.AMDFramebuffer (1.4.8) - installer pendrive Sierra 10.12.3

com.apple.AMDRadeonX3000 (1.5.1) - mac OS Sierra Combo Update 10.12.5
[doublepost=1499368408][/doublepost]


My installation of Sierra 10.12.3 was very strange. Installation done without being connected to the Internet.

Sierra 10.12.3 installer (pendrive) - kexts AMD 1.4.8 - kexts AMD works with /System/Library/Extensions

kexts AMD 1.4.8 installed hard disk by installer - kexts AMD not work with /System/Library/Extensions

Yes, the kexts AMD 1.4.8 pendrive and kext AMD 1.4.8 installed on the hard disk have different behaviors with /System/Library/Extensions

[doublepost=1499373074][/doublepost]Your temperatures are already better than mine. Mine are also within operating temperatures (i.e. not harmful to the hardware), but the issue is that it's unusable as an actual laptop with these temperatures.

Correct me if I'm wrong after reading so many possible commands and methods. The conclusion is that if I want the temperature to drop I do this (the short version of the procedure):

I downloaded the 1.4.8 versions of the AMD kexts nsgr made available earlier in a zip from the 10.12.3 pendrive and copied them on a USB stick (MacOS Extended). Now I boot in Recovery mode and go to Terminal to install the three AMD kexts with the cp -v -r /Volumes (etc) command in System/Library/Extensions.

After the reboot I load the AMDRadeonX3000.kext manually in Terminal into the disabled extensions directory.

FYI: I run 10.12.5 and the temperature of my MBP while working is 60-65 degrees with an occasional peek tot 70+. When just reading a text it is around 50-55 degrees and waking the MBP from sleep it starts at approximately 40 degrees, slowly increasing to 50.
Still not sure if these temperatures are harmful to the MBP, except for only being able to work 1,5 - 2 hours on a full battery.

 

[tommyball]

....

Some people have temperature problems and others do not have this problem. Even with the exact same model Macbook Pro.

My Macbook Pro Early 2011 - Intel HD 3000 - AMD 6750 -> problem temperature -> load kexts AMD.
Other people with this same model of Macbook Pro did not have temperature problem -> No need to load the AMD kexts.

Thanks nsgr!

I'll try the fix and see where my temps are.

 

[nsgr]

Oh okay, I understand now.

So I tried the 1.4.8 kexts now from the 10.12.3 installer with no difference in temperature.

Udate: okay, with the 1.4.8 kexts maybe there is a 3C decrease in idle temperature. If I leave it long enough it dropped to 50C which is the lowest it's been during all this testing. I'm going to reboot and load the kexts again to see if it will drop bellow 53 again

Update 2: Eh, so the 1.4.8 kexts make a very very small difference, 51C idle vs 53C.

But side question. Didn't you establish earlier that for my hardware I needed the Legacy kexts? Those don't exist in the 10.12.1 and 10.12.3 installer...




[doublepost=1499373074][/doublepost]Your temperatures are already better than mine. Mine are also within operating temperatures (i.e. not harmful to the hardware), but the issue is that it's unusable as an actual laptop with these temperatures.

The key for me was to put the penrive installer kexts 1.4.8 (AMDLegacySupport.kext, AMD6000Controller.kext, AMDFramebuffer.kext) on /System/Library/Extensions.

If I do not put these kexts in /System/Library/Extensions, then the temperature does not drop much when manually loading AMDRadeonX3000.kext.

I installed Sierra 10.12.3 and then did the update for 10.12.5.

I think when kexts 1.4.8 (AMDLegacySupport.kext, AMD6000Controller.kext, AMDFramebuffer.kext) are placed in /System/Library/Extensions, then certain keys are enabled at boot time in files related to temperature.

1 - Load Automatic

/System/Library/Extensions

AMDLegacySupport.kext - 1.4.8 - pendrive installer Sierra 10.12.3

AMD6000Controller.kext - 1.4.8 - pendrive installer Sierra 10.12.3

AMDFramebuffer.kext - 1.4.8 - pendrive installer Sierra 10.12.3


2 - Load Manual

/kexts-1.5.1-sierra-update-10.12.5 - from Sierra 10.12.5 Combo Update

cd /kexts-1.5.1-sierra-update-10.12.5

sudo kextload AMDRadeonX3000.kext

[doublepost=1499453238][/doublepost]

Correct me if I'm wrong after reading so many possible commands and methods. The conclusion is that if I want the temperature to drop I do this (the short version of the procedure):

I downloaded the 1.4.8 versions of the AMD kexts nsgr made available earlier in a zip from the 10.12.3 pendrive and copied them on a USB stick (MacOS Extended). Now I boot in Recovery mode and go to Terminal to install the three AMD kexts with the cp -v -r /Volumes (etc) command in System/Library/Extensions.

After the reboot I load the AMDRadeonX3000.kext manually in Terminal into the disabled extensions directory.

FYI: I run 10.12.5 and the temperature of my MBP while working is 60-65 degrees with an occasional peek tot 70+. When just reading a text it is around 50-55 degrees and waking the MBP from sleep it starts at approximately 40 degrees, slowly increasing to 50.
Still not sure if these temperatures are harmful to the MBP, except for only being able to work 1,5 - 2 hours on a full battery.

Yes that's right.

I only used the pen drive installer kexts AMD 1.4.8 (AMDLegacySupport.kext, AMD6000Controller.kext, AMDFramebuffer.kext)because they did not lock before the login screen at normal boot (IOConsoleUsers IOScreenLockState).

AMDRadeonX3000.kext - 1.5.1


The problem with battery life (2 hours) is that the AMD video card has not been turned off or using minimum force values.

 

[tschuuuls]

The problem with battery life (2 hours) is that the AMD video card has not been turned off or using minimum force values.

I just don't get, why the values in EFI don't fully turn of the device.

How low does your Power Consumption go in Coconut Battery (shows actual power consumption in Watts, updates every 20-30secs or so).
I can get to 13-14W with only the X3000 kext loaded.
Power draw is probably a better indication than temperatures.

Can you upload the older kexts somewhere? And by the way, you can extract files from installers (such as the combo update) with "Suspicious Package", thats how I got the kext from the combo updater.

EDIT: I asked a buddy with a 13 inch 2011 mbp, that one idles at 9W. We should get close to that to archieve good battery life.

 

[nsgr]

I just don't get, why the values in EFI don't fully turn of the device.

How low does your Power Consumption go in Coconut Battery (shows actual power consumption in Watts, updates every 20-30secs or so).
I can get to 13-14W with only the X3000 kext loaded.
Power draw is probably a better indication than temperatures.

Can you upload the older kexts somewhere? And by the way, you can extract files from installers (such as the combo update) with "Suspicious Package", thats how I got the kext from the combo updater.

EDIT: I asked a buddy with a 13 inch 2011 mbp, that one idles at 9W. We should get close to that to archieve good battery life.

It would be great for me if when running gpu-power-prefs Arch Linux or sudo nvram GUID:variable=values, then the AMD video card to stay completely off. Unfortunately this does not happen on my Macbook Pro 2011.

When I run the Sierra 10.12.3 installer (pendrive), then the following AMD kexts 1.4.8 are loaded (AMD6000Controller.kext, AMDFramebuffer.kext, AMDSupport.kext). AMDRadeonX3000.kext does not exist in the Sierra 10.12.3 installer (pendrive) - OS X Base System.

Even with these loaded kexts 1.4.8, the AMD video card remains active in the Sierra 10.12.3 installer. Touching next to the MagSafe connector, above the F2 key, this part of the Macbook Pro gets very hot.

I will print the screen with information from the Istat Menu and Coconut Battery.

Update - on Battery:

http://oi66.tinypic.com/14kzkmh.jpg

http://tinypic.com/r/14kzkmh/9

Photo: Kexts-AMD-1.4.8-and-1.5.1-Istat-Menu-Coconut-Battery-2017-07-07-at-17.55.54-2.jpg

Macbook Pro Early 2011 - MacBookPro 8,2 - Intel HD 3000 - AMD 6750M

Mac OS Sierra 10.12.5

Istat Menu -> CPU -Die Analog: 37 degrees Celsius

Coconut Battery

Active Monitor - Memory used: 2.65 GB

kexts AMD 1.4.8 - /System/Library/Extensions - load automatic

AMD6000Controller.kext

AMDSupport.kext

AMDFramebuffer.kext


Kext AMD 1.5.1 - kexts-1.5.1-sierra-update-10.12.5 - load manual

AMDRadeonX3000.kext


Update 2:

For security reasons, you should not use kexts downloaded from other sites. Only from official Apple websites.

kexts-amd-1.4.8-sierra-10.12.3-installer-pendrive.zip

https://uploadfiles.io/818dn


Extract kexts-amd-1.4.8-sierra-10.12.3-installer-pendrive.zip

Put the permissions 755 and owner and group on the kexts.
http://osxdaily.com/2012/01/12/how-to-manually-install-kernel-extensions-in-mac-os-x/


cd /kexts-amd-1.4.8-sierra-10.12.3-installer-pendrive

sudo chmod -R 755 AMD6000Controller.kext

sudo chown -R root:wheel AMD6000Controller.kext


sudo chmod -R 755 AMDFramebuffer.kext

sudo chown -R root:wheel AMDFramebuffer.kext


sudo chmod -R 755 AMDSupport.kext

sudo chown -R root:wheel AMDSupport.kext


Verify permissions Owner / Group


ls -la

drwxr-xr-x@ 3 root wheel 102 Jun 29 00:16 AMD6000Controller.kext

drwxr-xr-x@ 3 root wheel 102 Jun 29 00:17 AMDFramebuffer.kext

drwxr-xr-x@ 3 root wheel 102 Jun 29 00:17 AMDSupport.kext

 

[tschuuuls]

I am running a late 2011 15" 2.4Ghz with 6770m and the fix from page 5 (editied the EFI variable).

Mine draws about 17W with a few things open but basically idle. I just loaded the X3000 kext from 10.12.5, I don't have any AMD kexts in my extentions folder.

Can you upload the kext from the installer on mega, dropbox or some other service?
I don't really want to download the whole os just for those kexts

EDIT: And I don't care about ram usage. This machine (useless brick by Apples definition) has 16GB's anyways.

 

[nsgr]

I am running a late 2011 15" 2.4Ghz with 6770m and the fix from page 5 (editied the EFI variable).

Mine draws about 17W with a few things open but basically idle. I just loaded the X3000 kext from 10.12.5, I don't have any AMD kexts in my extentions folder.

Can you upload the kext from the installer on mega, dropbox or some other service?
I don't really want to download the whole os just for those kexts

EDIT: And I don't care about ram usage. This machine (useless brick by Apples definition) has 16GB's anyways.

Post above.