What am i doing wrong? https://imgur.com/a/oF0GB
Looks like i did everything correctly this second time, but now im stuck on 60% ish loading screen.....
Maybe my harddrive has gone to **** too?..
Last edited:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MBP 1,1-10,2 Force 2011 MacBook Pro 8,2 with failed AMD GPU to ALWAYS use Intel integrated GPU (EFI variable fix)
- Thread starter AppleMacFinder
- WikiPost WikiPost
- Start date
-
- Tags
- a1286 amd black screen blue and black screen discrete graphics dmg dmg files gfxcardstatus glitching gpu failure gpu panic gpu switch graphic card hardware fault hardware issue logic board failure macbook pro "15 2011 macbook pro (15-inch early 2011) macbook pro 2011 radeongate restart loop white screen
- Sort by reaction score
- Status
Looks like i did everything correctly this second time, but now im stuck on 60% ish loading screen.....
Maybe my harddrive has gone to **** too?..
First step solved by adding an extra commando in front.
Same step as Ruben.
I get the following message typing the printf:
invalid argument.
What should I do? Not clear. The commando with chattr gives the same message invalid argument.
Thanks for help.
Same step as Ruben.
I get the following message typing the printf:
invalid argument.
What should I do? Not clear. The commando with chattr gives the same message invalid argument.
Thanks for help.
Another thing, by using the single user mode I can boot but I still have the green stripes. The finder doesn't work at all and I can't browse anything.
Any idea also or will the linux trick make everything fine?
Thanks in advance for the help as it's far away from my knowledge.
Any idea also or will the linux trick make everything fine?
Thanks in advance for the help as it's far away from my knowledge.
Hi!
First of all thanks a lot for the continuous work all of you are developing about this issue in this forum!!! The amount of info is here is just overwhelming
I fixed my computer following the directions I found in this forum a couple of months ago, specifically the ones can be found in this post.
The computer, a MBP late 2011, works really great in general and even I would say that better than before since now it only uses the iGPU.
However, it still has sleep issues. I mean, I have set hibernatemode 3, and it's able to sleep and wake up fine if it's just for a couple of hours or something like that. But, if I put it to sleep for the whole night, sometimes it isn't able to wake up properly, i.e. the screen doesn't turn on, and I need to restart the machine.
Does anyone the slight idea of what is going on here and why sometimes this happens? I've tried several configs for gpuswitch and it's seems that the one works it gpuswitch 1. I also don't think that switching to hibernatemode 25 is going to do any good. I have that way in the past and sometimes happened the same thing.
Any help it's more than welcomed.
First of all thanks a lot for the continuous work all of you are developing about this issue in this forum!!! The amount of info is here is just overwhelming
I fixed my computer following the directions I found in this forum a couple of months ago, specifically the ones can be found in this post.
The computer, a MBP late 2011, works really great in general and even I would say that better than before since now it only uses the iGPU.
However, it still has sleep issues. I mean, I have set hibernatemode 3, and it's able to sleep and wake up fine if it's just for a couple of hours or something like that. But, if I put it to sleep for the whole night, sometimes it isn't able to wake up properly, i.e. the screen doesn't turn on, and I need to restart the machine.
Does anyone the slight idea of what is going on here and why sometimes this happens? I've tried several configs for gpuswitch and it's seems that the one works it gpuswitch 1. I also don't think that switching to hibernatemode 25 is going to do any good. I have that way in the past and sometimes happened the same thing.
Any help it's more than welcomed.
Hi everyone,
Sorry to say that, but it didn't worked for me, it's even worse than before, after this trick, I can more easily opening a session but I get a blue screen after one or two minutes, I took photos during the linux step, can you tell me where i'm wrong please ? (cf, si un expert francophone est de passage sur ce forum, merci par avance - anglais deuxième langue...)
https://imgur.com/a/M1J9C
Sorry to say that, but it didn't worked for me, it's even worse than before, after this trick, I can more easily opening a session but I get a blue screen after one or two minutes, I took photos during the linux step, can you tell me where i'm wrong please ? (cf, si un expert francophone est de passage sur ce forum, merci par avance - anglais deuxième langue...)
https://imgur.com/a/M1J9C
not yet, finally my mbpro works fine for the moment, no blue screen and quick start...it's a bit confusing.
I will try your solution if I see new bugs
I will try your solution if I see new bugs
[doublepost=1520701377][/doublepost]ApplemacFinder,If you don't have time to read my story (which also describes some interesting technical approaches) just scroll down this thread until a "100% WORKING SOLUTION" text
Discrete AMD GPU of my 2011 MacBook Pro 8,2 has finally failed because of the reasons mentioned here ( http://logicboardmac.blogspot.ru/ ) and there ( https://www.macrumors.com/2015/02/19/2011-macbook-pro-repair-program-apple/ ) . It has been working perfectly for 6 years under quite a high load, even tried SETI@HOME mining at background! So I was confident that my MBP is not affected by bad solder / bad soldering quality and didn't want to bring it to Apple for a free repair program - partially because couldn't find the time to pause my important software projects, partially because I was afraid that Apple might give me a less reliable logic board or refuse a free repair because of the several unrelated repairs that I did manually by myself earlier to save money: changed thermal paste a few times, replaced the internal battery 2 times, replaced a keyboard with broken buttons, etc. But it finally broke down last week: laptop's screen image became distorted, it refused to boot OS X (always freezing half-way), and - Apple free repair program has already ended! I know there are affordable solutions like $50 BGA resoldering at unofficial local repair shop and that its possible to get a new replacement HD 6750M chip from AliExpress for $35 or cheaper ( http://www.aliexpress.com/item/DC-2...0028-216-0810028-BGA-Chipset/32764872143.html or https://www.aliexpress.com/item/DC-2015-New-216-0810001-216-0810001-Graphic-Chipset/32718112928.html , because don't know if this is true - https://www.rossmanngroup.com/board...0604-replace-216-0810005-gpu-with-216-0810028 ) to guarantee a successful repair, so the total price of repair would be either $50 or $50+$35=$85 - less than $100 in any case. But I don't like investing money to the old computers, so I have thought - what if there is some hack to force MBP to use integrated graphics ALL THE TIME, even while booting ? And then started to explore the possible solutions...
===
First of all, it is possible to successfully boot a MBP to OS X while still using the failed GPU, after you remove the AMD drivers by booting in command line mode (CMD+S) and entering these commands:
1) fsck -fy (to check a disk)
2) mount -uw / (mount a root filesystem with read/write permissions)
3) sudo mkdir /AMD_Kexts/ (make a directory to store the AMD drivers in case you'll need them in future)
4) sudo mv /System/Library/Extensions/AMD*.* /AMD_Kexts/ (move the AMD drivers)
5) sudo rm -rf /System/Library/Caches/com.apple.kext.caches/ (remove the AMD drivers cache)
6) sudo mkdir /System/Library/Caches/com.apple.kext.caches/ (just in case OS X will be dumb and will not recreate this directory, I am creating it for OS X)
7) sudo touch /System/Library/Extensions/ (to update the timestamps so that new driver caches - without AMD drivers - will be definitely rebuilt)
8) sudo umount / (umount a partition to guarantee that your changes are flushed to it)
9) sudo reboot
The degree of your inconvenience while doing these steps - strongly depends on how heavily a screen's image is distorted in your case. In my case it was even more difficult because the OS X partition became a "read-only" partition (because of too many emergency shutdowns I did while desperately trying to boot OS X with a failed GPU) so I had to remove a hard drive from MacBook Pro and (using a USB to SATA 2.5" adapter taken from my portable HDD) attached it to a computer with Linux, then followed these instructions:
https://superuser.com/questions/961401/mounting-hfs-partition-on-arch-linux (1st answer) - carefully executed a number of commands, calculated a sizelimit for my parition layout, and finally ran sudo mount -t hfsplus -o force,rw,sizelimit=YOURNUMBER /dev/sdb2 /mnt to mount this HFS+ partition to /mnt directory in read-write mode. Then I performed these "1)-7)" steps you see above, and also repaired a filesystem by running sudo fsck.hfsplus -f /dev/sdb2 before unmounting a partition with sudo umount /mnt and putting a hard drive back to MBP...
===
This gave me a MBP which could boot to OS X although STILL using a broken AMD GPU: so it screen's image is very distorted (could browse the Internet but quite inconvenient to read a text), Launchpad is super laggy, and you can't switch to Integrated GPU using gfxCardStatus because: without AMD drivers (which we had to remove to successfully boot to OS X) Macbook Pro thinks its' internal screen is External Display and gfxCardStatus tells it is impossible to switch because External Display is using AMD GPU. Somewhere I found a suggestion that it is possible to rebuild a gfxCardStatus from the source code - https://github.com/codykrieger/gfxCardStatus - with removed or commented out 156-166 lines in the ./gfxCardStatus/Classes/GSProcess.m to make it to ignore the external display:
// find out if an external monitor is forcing the discrete gpu on
CGDirectDisplayID displays[8];
CGDisplayCount displayCount = 0;
if (CGGetOnlineDisplayList(8, displays, &displayCount) == noErr) {
for (int i = 0; i < displayCount; i++) {
if ( ! CGDisplayIsBuiltin(displays))
[list addObject:[NSDictionary dictionaryWithObjectsAndKeys:
Str(@"External Display"), kTaskItemName,
@"", kTaskItemPID, nil]];
}
}
So I rebuilt a gfxCardStatus using the instructions from the last reply of this issue -
https://github.com/codykrieger/gfxCardStatus/issues/229
(also had to download a MacOSX10.11.sdk from here - https://github.com/phracker/MacOSX-SDKs/releases - unpack and copy it to XCode's /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk - because of the Apple's stupidity the latest XCode for El Capitan does not include SDK for El Capitan!) However, it still didn't work - gfxCardStatus only pretended that it has switched to Integrated GPU, while in reality OS X did not let it switch! Even after I edited ./gfxCardStatus/Classes/GSGPU.m file to enable the mysterious "Nuke it from orbit switching" option, it still couldn't switch...
===
Then I discovered this interesting repository - https://github.com/0xbb/gpu-switch - which is partially similar by its' source code to gfxCardStatus but also has the "Login Hooks" (install_hooks.sh) to "automate the switching process for login/logout". Sadly it didn't work for me... However, there is a very interesting gpu-switch text file right at the root of this repository, which describes the EFI variables!
https://github.com/0xbb/gpu-switch/blob/master/gpu-switch
After studying it and also reading this issue's comments - https://github.com/0xbb/gpu-switch/issues/11 - I became confident to try this solution, but found out that my MacBook Pro 2011 8,2 with OS X El Capitan 10.11.6 is in a VERY problematic situation:
1) rEFInd is not installed, and to install it - must disable SIP protection. But I cannot boot to Recovery mode (Command+Option+R) or to OS X Installation DVD/USB (hold Option), (to disable SIP), because they freeze while booting! - although I removed AMD kexts from my system, of course these recovery tools are using AMD kexts integrated to their design. Also cannot use Rootfool hack ( https://github.com/gdbinit/rootfool ) to disable SIP during runtime, because it works only at OS X version older than 10.11.4
2) Tried overheating my Macbook Pro on purpose (forcing CPU usage to 100% and putting it to a tightly closed bag) to force it to shutdown from overheating and then quickly reboot so that Integrated graphics will be enabled during the boot time - making it possible to boot to Recovery. But because of the wonderful high end thermal paste I have applied not so long ago - cannot overheat it even after waiting for a long time! At this point I thought that could either: a) remove AMD kexts from Installation media, or b) to connect MBP's hard drive to a Linux machine again and run a bunch of chmods to remove the SIP flags from the directories mentioned here ( http://apple.stackexchange.com/questions/193368/what-is-the-rootless-feature-in-el-capitan-really ) which could potentially make a system unbootable, or c) to try installing rEFInd to HFS+ partition directly from a Linux machine with root rights because it will bypass SIP --- but have not explored these options, although some of them might have worked...
3) Wanted to boot a Linux LiveCD to edit the EFI variables from there, but no matter what I did: tried booting straight without GRUB option modifications, tried editing GRUB boot options (with "e" key) to add nomodeset / remove quiet splash / or both in every combination , or like suggested in this article ( https://wiki.archlinux.org/index.php/MacBookPro8,1/8,2/8,3_(2011) ) also add i915.modeset=0 radeon.modeset=0 or radeon.modeset=0 i915.modeset=1 i915.lvds_channel_mode=2 ; and then pressed Fn+F10 or Shift+Ctrl+Fn+F10 to boot with these options: but the Linux boot process always failed at different boot stages, no matter what popular user-friendly Linux distribution or what version of it I am trying: tried many releases of Ubuntu / Lubuntu / Fedora , even the old "AMD64 Mac" and "Alternate AMD64 Mac" images, but they always failed - either at the very beginning of boot process (black screen, or a black screen with a blinking or stuck _ character at the left upper corner) or failed at the very end of it - right before it is supposed to show a graphical desktop environment...
Later, totoe_84 wrote that he was able to boot Ubuntu in graphical mode using the following setup for GRUB:
- To disable the AMD graphics card I added the following lines after set gfxpayload=keep
outb 0x728 1
outb 0x710 2
outb 0x740 2
outb 0x750 0(based on https://ubuntuforums.org/showthread.php?t=2157775 )
- Next I added the following after quiet splash
i915.lvds_channel_mode=2 i915.modeset=1 i915.lvds_use_ssc=0
===
Then I remembered that there are not-mainstream Linux distributions for advanced users, which have a LiveCD without any graphical interface: you are dropped to a pure console and you are supposed to install the system along with only those graphical interfaces and software packages / groups of packages which you explicitly select. For example: Arch Linux (https://www.archlinux.org/) and Gentoo Linux (https://gentoo.org/) . Because their LiveCD does not have a graphical interface, they could be booted without a problem to a pure Linux console and there you could edit the EFI variables ! So here is a...
===
=== 100% WORKING SOLUTION
===
=== Force your MBP to ALWAYS use Intel integrated GPU (EFI variable fix)
===
=== to make it great again !
===
1) Create the Arch Linux LiveCD/LiveUSB :
You need a working computer for that and a spare CD/DVD/USB drive. Download the latest Arch Linux ISO image from this page - https://www.archlinux.org/download/ , at the time of writing it is archlinux-2017.03.01-dual.iso . Then you could either simply burn this ISO to CD/DVD (which later could be either inserted to MBP's SuperDrive or External DVD Drive connected to MBP by two USB cables) or create a bootable USB: use the great detailed instructions from this page, https://wiki.archlinux.org/index.php/USB_flash_installation_media
2) Boot to it: insert this CD/DVD/USB to Macbook Pro, hold Option key while booting, choose "EFI boot" (that is your bootable installation media), press "e" key to edit the GRUB options of the Arch Linux archiso x86_64 UEFI CD menu entry while it is selected at the main screen, add nomodeset to the end of this line and press Enter. If everything is done correctly, you will find yourself at the Linux console!
3) Edit EFI vars: looks like efivarfs filesystem is mounted by default! So you can already cd /sys/firmware/efi/efivars and ls to explore this directory and see if there is a "gpu-power-prefs-..." variable (where ... is UUID of this variable). If there is such a variable, its better to remove it with rm. In my case the efivarfs has been mounted by default with read/write permissions, but if you are getting the "operation not permitted" message while attempting to rm, it means that in your case efivarfs has been mounted as read-only and you need to remount it with read-write permissions and try again (credits to totoe_84 for this valuable addition) :
*) cd /
*) umount /sys/firmware/efi/efivars/
*) mount -t efivarfs rw /sys/firmware/efi/efivars/
*) cd /sys/firmware/efi/efivars/
If your screen is so distorted that it is difficult to see the letters, just start typing the rm gpu-power-pre and then press TAB key for autocompletion. In my case there were not such a EFI variable, only "gpu-active-..." and maybe somehow related "gfx-saved-config-restore-status-..." . Then I looked again at that gpu-switch text file (mentioned above, https://github.com/0xbb/gpu-switch/blob/master/gpu-switch),
and entered THESE COMMANDS:
*) chattr -i "/sys/firmware/efi/efivars/" <----- skip this command
Actually a gpu-switch script had "${sysfs_efi_vars}/${efi_gpu}" but I didnt have a "gpu-power-prefs-..." variable - so, partially by mistake, I didn't add that efi_gpu suffix and entered this incomplete path accidentally
*) printf "\x07\x00\x00\x00\x01\x00\x00\x00" > /sys/firmware/efi/efivars/gpu-power-prefs-fa4ce28d-b62f-4c99-9cc3-6815686e30f9
Did not have a EFI "gpu-power-prefs-" variable so I thought that it will be OK to create a new one with a random UUID - in this case, taken directly from a gpu-switch script
*) chattr +i "/sys/firmware/efi/efivars/gpu-power-prefs-fa4ce28d-b62f-4c99-9cc3-6815686e30f9"
http://www.tecmint.com/chattr-command-examples/ - chattr (Change Attribute) is a command line Linux utility that is used to set/unset certain attributes to a file in Linux system to secure accidental deletion or modification of important files and folders, even though you are logged in as a root user.
...
Syntax of chattr ---> chattr [operator] [flags] [filename]
...
A file is set with ‘i‘ attribute (+i as you see in this command) ---> cannot be modified (immutable). Means no renaming, no symbolic link creation, no execution, no writable, only superuser can unset the attribute.
...
Operator
This chattr command is supposed to lock a file to make it accessible only by "superuser" - and so that, while booting, your EFI will have no chance to screw up your gpu-power-prefs-... variable under any circumstances
- + : Adds the attribute to the existing attribute of the files.
- – : Removes the attribute to the existing attribute of the files.
- = : Keep the existing attributes that the files have.
*) cd /
Could not unmount efivars if you are inside this directory, so change to the root directory
*) umount /sys/firmware/efi/efivars/
Guarantees that your EFI variables are flushed to efivarfs filesystem, please unmount it safely before rebooting)
*) reboot
===> IF YOU DID EVERYTHING CORRECTLY, MOST LIKELY THAT YOUR MACBOOK PRO IS NOW USING INTEGRATED GRAPHICS WHILE BOOTING, AFTER BOOTING, AND IS WORKING GREAT AGAIN !
In the future maybe you could need to re-apply this solution if you would have to reset your PRAM / NVRAM / SMC because of some other problems, so remember this solution somewhere... Funny thing: now you can't switch to Discrete GPU even using gfxCardStatus, it is forever stuck at Integrated
I spent two working days to discover this solution, and really hope that it will work flawlessly for every MBP owner with a broken discrete GPU. Good luck!
Thank you for the awesome fix. I went to the apple store and they said that my broken GPU was unrepairable. HAH. Fix is working great however if I restart my computer I have to redo the whole linux process. Does anyone have any idea how to make this fix permanent?
Since I did this trick, the startup sound has gone 
, I can still see artifacts of screen, sometimes, rarely, but the computer is less usable
, I can still see artifacts of screen, sometimes, rarely, but the computer is less usableHi Guys,
at first i have to say thank you for this great thread. It really helps
My short story, my mac shows this crazy pattern on the screen (screenhot) and does not boot.
After moving my NVDIA Kext files i can boot, but the system ewas extremly slow.
After i've read this thread and have done all the steps (archlinux, gpu-power-prefs, efi ...) my system runs much faster!!!
The only problem left ... the screen pattern ... do i have a chance to fight this? Is this really a gpu problem?
Or is it a problem off the internal HDGraphics? The pattern is also visible when i start the machine with the archlinux stick.
Hope to find help
Thank you in advance
at first i have to say thank you for this great thread. It really helps
My short story, my mac shows this crazy pattern on the screen (screenhot) and does not boot.
After moving my NVDIA Kext files i can boot, but the system ewas extremly slow.
After i've read this thread and have done all the steps (archlinux, gpu-power-prefs, efi ...) my system runs much faster!!!
The only problem left ... the screen pattern ... do i have a chance to fight this? Is this really a gpu problem?
Or is it a problem off the internal HDGraphics? The pattern is also visible when i start the machine with the archlinux stick.
Hope to find help
Thank you in advance
Attachments
Hmm strange, when you press enter after the printf line, does the machine respond with "\´dquote>" ? Or is this something you have written?
[doublepost=1520789454][/doublepost]
Yes you need to apply the EFI variable fix by using ArchLinux. Just removing the AMD Drivers will give you a sluggish machine.
You said that the printf gives you invalid argument. Please attach a screenshot of this message. The possibilities I can think of is the following:
1) The file already exists. You have to remove the gpu-power-prefs... file with rm command before you can re-create it. If the file is protected with immunity you will have to chattr -i <filedirectory> before you can delete it.
2) The directory is in read-only. You have to make the directory in read-write by using the commands stated in the original post.
[doublepost=1520789614][/doublepost]
Hey, what OS version are you on? There are some sleep problems with some versions of macOS/OS X
For reference, 10.11.6, 10.12 and 10.12.6 should work perfectly (at least on early 2011MBP).
Is there a way where I can have these settings and LoginHooks survive a software update or if I need to reinstall MacOS? I would rather just have to put these LoginHooks into place once and then never have to think about them ever again.
As far I know it's not possible and you have to apply those fixes every time you update your system or reinstall.
Awe. Alright. Well, at least is there a way where I can turn all of these steps into an application that I can just click on and have it do it for me? I need to sell my computer asap, as I am short on cash and I don't want the person who is going to use it to be confused as hell.
There are no automated apps that completes the process that I know of. I believe it would be possible, but someone has to code the app first. If you have some coding skills you could try yourself. You could also try to create an Automator workflow though I am not sure it would work.
I doubt it could be done, but I'm not an expert. As far as I know you have to boot the recovery single user mode to run csrutil disable to disable the system integrity protection and change the parameters in the nvram. And as far as I know this is reset to defaults every time you update the system. I don't know any app able to do that from the OS.
If you want to sell your computer I recommend you to be honest and reduce the price since it is severely broken in one of its fundamental parts, the dGPU. This solutions are just a rig to make the computer work "normally", but it's still broken, severely.
Hi, does this solution is compatible with a mbpro 2011 (early) or strictly LATE ? thx
[doublepost=1521035110][/doublepost]
I tried it, everything was fine until the step 5 : Failed to load - (libkern/kext) not found; check the system/kernel logs for errors or try kextutil(8)
[doublepost=1521035277][/doublepost]
I guess that step 5 is done on the terminal ?
since I tried this solution (stucked at the step 5), I no more can use the first linux trick...is there a way to reset something ?
Big thanks man! Works perfectly!
Exept the LoadX3000.sh, the AMDRadeonX3000.kext is after moving from extensions in the backup folder, not in AMD_Kexts
My MacBook Pro early 2011 now works again like charm
Hello Mikey and thank you to everyone else who work on this fix.
I have late 2011 macbook pro,
2years ago my GPU was "replaced" or don't know what from Apple for the failing chip.. but now I failed again.
I started with fresh installed Sierra 10.12.6
This guide works best for me. And strangely made my MBP faster.
Tonight I decided to do security update 2018-001, and I noticed I have the AMDRadeonX3000.kext in both folders,
/System/Library/Extensions & /System/Library/Extensions-off
I made mistake - in single user mode I did move AMDRadeonX3000.kext but when I was asked to replace with the file in /System/Library/Extensions-off folder I said yes.
Now works good, no heat etc, but
sudo kextstat |grep AMD give me this:
116 2 0xffffff7f82da0000 0x122000 0x122000 com.apple.kext.AMDLegacySupport (1.5.1) 0670744B-B64C-3424-B186-FD972A37E78E <104 12 11 7 5 4 3 1>
134 0 0xffffff7f82f56000 0x12e000 0x12e000 com.apple.kext.AMD6000Controller (1.5.1) 2015FD1C-294C-3C71-AEB5-C1EE0E65BD46 <116 104 12 11 5 4 3 1>
150 0 0xffffff7f834a7000 0x22000 0x22000 com.apple.kext.AMDLegacyFramebuffer (1.5.1) 930A7077-5EBD-3FA5-A023-415A1438E132 <116 104 12 11 7 5 4 3 1>
Even the AMDRadeonX3000.kext is in /System/Library/Extensions-off folder, and not in /System/Library/Extensions I can't load manually :
AMDRadeonX3000.kext failed to load - (libkern/kext) not found; check the system/kernel logs for errors or try kextutil(8).
I followed your solution about copy or extracting the kext file, but i can't menage to work. not sure what to do now.
I think starting from fresh will be best solution for me, i really want to make this final step, but also want to have the security updates.
all the steps are done in terminal or in the single user mode, which is terminal. I recommend you to read thoroughly either @MikeyN post in this thread or my posts, mainly the last one. If you don't do step by step, thoroughly reading, the guides don't work....
PS/ if you are stuck in step 5, means you haven't done correctly step 4. In other words you haven't move the problematic kext out to the folder extensions-off. Or you have moved it somewhere else. Go figure.
[doublepost=1521183914][/doublepost]
all the steps are done in terminal or in the single user mode, which is terminal. I recommend you to read thoroughly either @MikeyN post in this thread or my posts, mainly the last one.
I think it's also mentioned in both guides, every time you update your system the kext it's going to be installed again the original folder... so before you update you move the kext back to /extensions/ and after you update you apply the solution again.
Again, a better explanation is in both guides.
My macbook pro 2011 is ok now, but there is another problem created which is my pc is getting hot without any reason.Can u suggest me a good solution ?
If your MBP is getting hot that means that you haven't applied the solution correctly... probably the kext aren't loading, specifically the AMDRadeonX3000.kext needs to be load at login using the /Library/LoginHook/LoadX3000.sh.
Check $ kextstat | grep AMD if there are all the kexts there. If the AMDRadeonX3000.kext isn't there... it's a ownership-permissions problem.
Code:
$ sudo chown -R root:wheel /System/Library/Extensions/AMD*.*
$ sudo chown -R root:wheel /System/Library/Extensions-off/AMD*.*again... check the guides, everything is there.