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
What is the total size RAM?
What is the RAM consumption?
Applications -> Utilities -> Active Monitor -> Tab Memory:
Physical Memory:
Memory Used:
App Memory:
Wired Memory:
Directly after a fresh restart -
Physical Memory: 8GB
Memory Used: 5.86
App Memory: 4.72
Wired Memory: 1.13
Physical Memory: 8GB
Memory Used: 5.86
App Memory: 4.72
Wired Memory: 1.13
using OSX 10.11
I believe the GUID is the same, it shows the same when I run nvram-dump
Code:
2017-07-04 14:38:56.745 nvram-dump[1391:45878] FA4CE28D-B62F-4C99-9CC3-6815686E30F9:gpu-active
2017-07-04 14:38:56.748 nvram-dump[1391:45878] FA4CE28D-B62F-4C99-9CC3-6815686E30F9:gpu-power-prefs
2017-07-04 14:38:56.748 nvram-dump[1391:45878] gpu-policy
2017-07-04 14:38:56.748 nvram-dump[1391:45878] 7C436110-AB2A-4BBB-A880-FE41995C9F8:gpu-policy
2017-07-04 14:38:56.749 nvram-dump[1391:45878] FA4CE28D-B62F-4C99-9CC3-6815686E30F9:DisplayBackgroundColor
2017-07-04 14:38:56.749 nvram-dump[1391:45878] backlight-level
2017-07-04 14:38:56.749 nvram-dump[1391:45878] <ff02>
2017-07-04 14:38:56.749 nvram-dump[1391:45878] 7C436110-AB2A-4BBB-A880-FE41995C9F8:backlight-level
2017-07-04 14:38:56.749 nvram-dump[1391:45878] 7C436110-AB2A-4BBB-A880-FE41995C9F8:GfxMode
2017-07-04 14:38:56.749 nvram-dump[1391:45878] FA4CE28D-B62F-4C99-9CC3-6815686E30F9:backlight-regsnot sure what you mean by this. anyway like I said, when I try to set it on my mac I get wonky behavior where the display goes black.
I am unable to run gfxcardstatus when I have gpu-power-prefs set to x0100000 because it makes the screen go black.
Are these values in idle? No web browser, no applications, only Mac OS Sierra with default programs?
If yes, then you have a problem with kernel rebuild cache.
Mac OS Sierra 10.12.5 - idle - only with running Terminal, Active Monitor, gfxcardstatus and Istat Menu
Memory Used: 2 GB or 2.5 GB
App Memory: 1 GB or 1.5 GB
Wired Memory: 1 GB
I've been through this problem.
I solved only by re-installing the Mac OS Sierra 10.12.5 Update. Then Mac OS Sierra reinstalls the AMD kexts and rebuilds the kernel kext cache.
Download macOS Sierra 10.12.5 Combo Update
https://support.apple.com/kb/DL1918?locale=en_US
My steps:
1 - Download macOS Sierra 10.12.5 Combo Update
2 - Install macOS Sierra 10.12.5 Combo Update
3 - When Sierra ask to restart, then restart. Remember, kext AMD put back /System/Library/Extensions
4 - First restart after macOS Sierra 10.12.5 Combo Update
Enter Safe Mode (Shift key at boot) -> rebuild kernel cache extensions
5 - Second restart - Enter Safe Mode (Shift key at boot) - see if mac os sierra update install other things.
6 - Enter Recovery Mode (Command + R)
Use FGuarani method - move AMD kexts /System/Library/Extensions to example /DisableExtensions-3
3.1) So what you have to do is:
https://forums.macrumors.com/thread...efi-variable-fix.2037591/page-5#post-24511780
7 - Reboot
8 - Enter normal mode
9 - Verify Memory Used, App Memory and Wired Memory.
-----------
When I tried to remove the AMD kexts with the Single User mode (Command + S - with SIP disable, then Sierra would rebuild the kernel cache but doubled the memory consumption.
sudo rm -rf /System/Library/Caches/com.apple.kext.caches/
sudo mkdir /System/Library/Caches/com.apple.kext.caches
touch /System/Library/Extensions
[doublepost=1499202017][/doublepost]
Does the screen go black even with the Nvidia kexts removed from the /System/Library/Extensions ?
Did you remove Nvidia kexts from /System/Library/Extensions ?
Does step 4 happen automatically simply by loading into Safe Mode?
I'm just going to back up some files to be safe and then I'll try this. Will this fix the thermal issues though?
I'm just going to back up some files to be safe and then I'll try this. Will this fix the thermal issues though?
Last edited:
I enter Safe Mode after restart, so the Sierra rebuild the kernel and not go into normal mode and freeze the screen in IOConsoleUsers IOScreenLockState.
[doublepost=1499203952][/doublepost]Remember, the Sierra installed in the user FGuarani is in the partition /Volumes/Macintosh\ HD
You have to change to the name of your partition.
Mine is in /Volumes/MacSierra (Sierra 10.12.5 installed hard disk)
Use ls command to list partitions in /Volumes
Recovery Mode
ls /Volumes
I held down shift for five minutes and it wouldn't load Safe Mode. I let it install, it restarted itself but now when I hold down shift I get stuck on the Apple logo with a full black loading bar under it.
I can only load back into normal mode. I still have the same Apple logo and black bar but it will load relatively quickly.
I get the same Apple logo and black bar when I try to load Recovery Mode and it also gets stuck.
+++++++
Okay, I restarted and I'm back to having the problems with my AMD chip.
I did the sudo nvram thing in Single User Mode and I managed to get into Recovery mode now but I can't cd / my drive to move the kexts.
I did ls /Volumes and it shows Image Volume OS X Base System macOS but when I do cd /Volumes/macOS it gives me the message "No such file or directory".
I can only load back into normal mode. I still have the same Apple logo and black bar but it will load relatively quickly.
I get the same Apple logo and black bar when I try to load Recovery Mode and it also gets stuck.
+++++++
Okay, I restarted and I'm back to having the problems with my AMD chip.
I did the sudo nvram thing in Single User Mode and I managed to get into Recovery mode now but I can't cd / my drive to move the kexts.
I did ls /Volumes and it shows Image Volume OS X Base System macOS but when I do cd /Volumes/macOS it gives me the message "No such file or directory".
Last edited:
1 - First, enable boot verbose
Enter Single User mode (Command + S)
sudo nvram boot-args="-v"
reboot
2 - Boot Macbook Pro -> Press Shift Key -> Appears Message Enter Safe Mode
I use the Shift key on the left of the Macbook Pro's built-in keyboard. Hold for 10 seconds with the Shift key.
Do not press the Shift key for a long time so that it does not cause a slowdown at boot (Apple Logo at boot freeze).
Isn't it too late for Safe Mode? I have to start the whole thing over again.
But I can't get back in to normal mode now, it locks up as soon as I log in. I'm assuming I have to remove the kexts again before I can get back in to normal mode again.
It's not letting me cd /Volumes/macOS even though in Recovery Mode Disk Utility it says that that is the Mount Point.
But I can't get back in to normal mode now, it locks up as soon as I log in. I'm assuming I have to remove the kexts again before I can get back in to normal mode again.
It's not letting me cd /Volumes/macOS even though in Recovery Mode Disk Utility it says that that is the Mount Point.
What message error boot verbose (macbook freeze)? The last two lines of boot verbose.
Sorry, after some Googling I managed to cd /Volumes/macOS and move all of the kexts again and I am back in normal mode like I was before, and it appears to be stable again (with high memory usage still though).
But it's almost 1 a.m and I'm assuming that it's too late to do the safe mode trick so I will have to restart the whole procedure. In the morning I will try all of the steps again, installing the 10.12.5 update and trying to get in to safe mode.
But it's almost 1 a.m and I'm assuming that it's too late to do the safe mode trick so I will have to restart the whole procedure. In the morning I will try all of the steps again, installing the 10.12.5 update and trying to get in to safe mode.
You have to discard if it is not the high memory consumption that is causing the above-average thermal heating.
Yes, I understand. It's all about trial and error to find out what is causing which issues.
Right now the memory usage is still high ( slightly higher even) and the thermals are about the same
Right now the memory usage is still high ( slightly higher even) and the thermals are about the same
I was simply impatient the first time, or maybe the process was simply more successful this time around, but I am now in Safe Mode directly after installing the update.
I successfully followed all of these steps with no changes to temperatures or memory usage.
But I've googled high memory usage in MacOS and high memory usage appears to be normal in MacOS. I remember always having high memory usage on my iMac without performance decrease, it's just the way OS X is made apparently. The "Pressure Graph" I think it is called is constantly green, if there was something truly using excessive memory it would be red is what I'm reading.
Memory Used: 6.29
App Memory: 4.79
Wired Memory: 1.32
Cached Files: 1.68
I successfully followed all of these steps with no changes to temperatures or memory usage.
But I've googled high memory usage in MacOS and high memory usage appears to be normal in MacOS. I remember always having high memory usage on my iMac without performance decrease, it's just the way OS X is made apparently. The "Pressure Graph" I think it is called is constantly green, if there was something truly using excessive memory it would be red is what I'm reading.
Memory Used: 6.29
App Memory: 4.79
Wired Memory: 1.32
Cached Files: 1.68
Since I was running relatively high memory too, I decided to take a stab at reinstalling 10.12.5 as suggested by nsgr.
Mistake.
Fortunately I had a recent Time Machine back up to undo the installation.
After first copying the 1.44 AMD Kexts to make sure I could but them back, I did the Sierra Combo 10.12.5 update. All went well, and at the first restart command I made sure I could interrupt the process to remove the AMD 1.51 Kexts that the install did. After moving them to a second copy of AMD_Kexts, I copied the 1.44 kexts to /System/Library/Extensions, and confirmed that they had loaded correctly in the next boot.
But when I tried to manual load AMDRadeonX3000, I got some messages about libkern not compatible or something... Should have copied the error message more closely...
This morning, the Time Machine restore went well overnight, and I found the 1.44 AMD kexts loaded automatically fine. But I got the same libkern error message in the restored system when I tried to load AMDRadeonX300, and my temps started to climb again...
Reviewed all my notes on this process, and decided to do a little digging. NVRAM was a mess, with all kinds of garbage in nvram -p. So I rebooted with Option Command P and R, and cleaned out the nvram. Reboot did not quite restore me to integrated display thought so quickly I did the
sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00
Which brought me back to integrated right away. Reviewing other steps that had been done when I got the system working last time, and also issued this command in Recovery Mode...
nvram boot-args="-v agc=0"
This time, sudo kextload AMDRadeonX3000.kext in /AMD_Kexts was accepted without complaint, and my system is back!
After this scare, I think I will stop playing with this, and enjoy the system as it sits. Memory with browser and Mail running is using about 4gb, GPU Temp is back down to 40, current draw is 1260 ma...
A good spot to stop...
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...
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?
Fix for 17 inch dGPU switch issue
(Tested successfully in both “early” and “late” 2011 17 inch MacBook Pro)
This guide is based on the experience of many users (including me) while trying to fix the very well known issue with AMD dGPU on 17’’ MacBook Pro from 2011 (both early and late):
Step 0) As a starting point I made a clean installation of Sierra (Version 10.12.4) — This is just a step for establishing a common middle ground and is not really needed….
0.1) To do this just download the installer from the App Store and then use “DiskMaker X” to create a bootable installation.
0.2) After the bootable image is created, proceed to turn off your computer and hold the “Alt” or “Options” Key. Select the Sierra installer and proceed with the installation (I format the HDD partition to make a clean install on it)
Note: You might need to do this on another computer. Just buy one of those cheap usb to sata connectors and use it to connect it to another Mac so you don’t risk having your installation failed because of your machine.
Step 1) Prepare a Bootable USB pendrive with a non GUI Linux (Credits to AppleMacFinder)
1.1) Download ArchLinux ISO
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
1.2) Creating the bootable USB with the .iso:
In macOS
First, you need to identify the USB device. Open /Applications/Utilities/Terminal and list all storage devices with the command:
*) diskutil list
Your USB device will appear as something like /dev/disk2 (external, physical). Verify that this is the device you want to erase by checking its name and size and then use its identifier for the commands below instead of /dev/diskX.
A USB device is normally auto-mounted in macOS, and you have to unmount (not eject) it before block-writing to it with dd. In Terminal, do:
*) diskutil unmountDisk /dev/diskX
Now copy the ISO image file to the device. The dd command is similar to its Linux counterpart, but notice the 'r' before 'disk' for raw mode which makes the transfer much faster:
*) sudo dd if=path/to/arch.iso of=/dev/rdiskX bs=1m
After completion, macOS may complain that "The disk you inserted was not readable by this computer". Select 'Ignore'. The USB device will be bootable.
Step 2) Boot to Linux (Credits to AppleMacFinder):
2.1) 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! (It takes some time so be patient and wait for the prompt)
2.2) 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).
2.2-Case 1:
If there is such a variable, its better to remove it with rm.
*) rm gpu-power-prefs-…
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) (Try this and then try to remove it):
*) cd /
*) umount /sys/firmware/efi/efivars/
*) mount -t efivarfs rw /sys/firmware/efi/efivars/
*) cd /sys/firmware/efi/efivars/
*) rm gpu-power-prefs-…
If this also fails (If you still can’t erase the file) use chattr command to disable file immutability and then erase the file:
*) chattr -i "/sys/firmware/efi/efivars/gpu-power-prefs-…”
*) cd /sys/firmware/efi/efivars/
*) rm gpu-power-prefs-…
2.2-Case 2:
The file gpu-power-prefs-… doesn’t exist well then you don’t have to delete it hahaha. (I repaired 2 17 inch models and 1 didn’t have it, so it’s fine)
2.3) Create a new gpu-power-prefs-… file (Original credit mentioned above, https://github.com/0xbb/gpu-switch/blob/master/gpu-switch, Credits to AppleMacFinder):
*) printf "\x07\x00\x00\x00\x01\x00\x00\x00" > /sys/firmware/efi/efivars/gpu-power-prefs-fa4ce28d-b62f-4c99-9cc3-6815686e30f9
2.4) Add immutability to the gpu-power-prefs-… file (Credits to AppleMacFinder):
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
*) chattr +i "/sys/firmware/efi/efivars/gpu-power-prefs-fa4ce28d-b62f-4c99-9cc3-6815686e30f9"
2.5) Unmount efivars and reboot (Credits to AppleMacFinder):
Could not unmount efivars if you are inside this directory, so change to the root directory
*) cd /
*) umount /sys/firmware/efi/efivars/
Guarantees that your EFI variables are flushed to efivarfs filesystem, please unmount it safely before rebooting)
*) reboot
3) Eliminate AMD Kexts (Credits to newfield),
Note: You might need to do this every time you do an OS updates, since each update normally writes the AMD Kexts again.
(His words and this also happened to me!: After disabling the dGPU using Arch, normal boot would hang halfway. Although safe boot would work. I wound up having to remove all the AMD kext files in the Terminal in Recovery Console)
Trying to remove them in Single User just gave me sandbox errors. (Summary -> Don’t do it in Single User Mode the one that you boot with Cmd + S)
3.1) So what you have to do is:
If you have FileVault Unlock it first:
Unlock first.
Then Boot into Recovery (“cmd + r”, it will boot without failing, if it fails then repeat step 2 and then after that boot directly into recovery with command + R, I had to do this once because the dGPU got active again after booting into the os with AMD kexts)
*) Boot into recovery mode (Command + r)
*) Start Terminal
*) diskutil cs list (find UUID for drive)
*) diskutil coreStorage unlockVolume UUID
*) cd /Volumes/Macintosh\ HD
*) mkdir AMD_Kexts
*) mv System/Library/Extensions/AMD*.* AMD_Kexts/
*) reboot
(If you only have one storage with 1 partition just use "cd /Volumes/Macintosh\ HD" and the remaining commands after starting the terminal)
Extra STEP), if your PC is now working! Download “steveschow” branch of gfxCardStatus (gfxCardStatus v2.4.3i) or just download the app directly from:
URLS:
https://github.com/steveschow/gfxCardStatus/releases
https://github.com/steveschow/gfxCardStatus
With this application you can even prove that the dedicated GPU can't get activated. Even if you try to change the selected GPU to the dedicated one, it just won't change.
—————
The End!
AND VOILA!!! You have a working 17 inch MacBook Pro. As I said I tested this with an early 2011 and late 2011 17 inch MacBook Pro’s and both are now running (Before they were both dead)
Big thanks to AppleMacFinder, to the makers and contributors of this thread, to gfxCardStatus maker and forkers(steveschow) and to switch-gpu makers I can’t thank you guys enough as I am so happy to bring both of this incredible machines back to life. With this post I am not trying to take any credit, but as I had 2 machines I run into different issues with both, which could be helpful to others, thats why I was inclined to make “my own” guide and share it with you.
I just created an account here to share this, Hope it helps more people!
Last edited:
Unfortunately the Macbook Pro 2011 with OS X turned into a Pandora's box.
It worked for me the sudo boot-args="- v agc=0" with Sierra 10.12.5. Now it does not work for me anymore in the Sierra. I'm really surprised by this lack of Apple standardization.
I thought the temperature problem was only with the Sierra, but I realized that it also happened to Montain Lion, Yosemite, El Capitan and Sierra.
Unfortunately I did not have the El Capitan available from the App Store tab Purchase. So I had to study how the App Store worked so I could "cheat" the App Store and download El Capitan with the Sierra installed on the hard disk.
El Capitan did not solve the temperature problem.
I realized that in my tests, the gpu-power-prefs ArchLinux or sudo nvram GUID:variable=value did not work with Sierra and kexts AMD 1.5.1 just before the login screen.
IOConsoleUser IOScreenLockState.
Removed all the kexts AMD I could get to the login screen. This works correctly.
But the temperature problem remained.
So I realized that when entering with the installer of the Sierra 10.12.3 (pendrive), and using the command ioreg | grep AMD, there were some AMD kexts (1.4.8) loaded onto my AMD video card. No problem with gpu-power-prefs ArchLinux or sudo nvram GUID:variable=value.
AMD6000Controller.kext
AMDFramebuffer.kext
AMDSupport.kext
Unfortunately the kextstat command is not available in the Sierra (pendrive) installer. Negative point for Apple.
I had the idea to put these AMD kexts 1.4.8 in Sierra 10.12.5 and see what would happen. And I realized that I could get to the log-in screen.
The temperature had dropped a bit but remained high. So I remembered that I had sometimes seen the AMDRadeonX3000.kext loaded before I had the AMD chip failure problem.
I tested load the AMDRadeonX3000.kext (1.5.1) and fortunately the temperature dropped 15 degrees Celcius.
When you load AMDRadeonX3.kext, then keys are activated within the AppleGraphicsControl.kext and AppleGraphicsPowerManagement.kext.
[doublepost=1499286631][/doublepost]
No temperature difference in loading AMDRadeonX3000.kext automatically (before login) or manually (after login).
Before having the AMD chip problem, the temperatures were the same as now (AMDRadeonX3000.kext).
Post the information of this command. Open Terminal:
system_profiler -detailLevel full SPDisplaysDataType
Last edited:
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
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
I'm not sure what you mean. It's still the same AMD chip that the laptop came with when I first purchased it. There have been no modifications to the hardware in my machine.
I asked because there are people who did the AMD chip replacement and after a while they had problems again.
If I look for your AMD 6740 ID in the AMD kexts, they appear in only 3 files.
My AMD 6741 ID appears in these same 3 files.
Kexts AMD moved to /DisableExtensions
grep -Ril "6740" /DisableExtensions
/DisableExtensions/AMD6000Controller.kext/Contents/Info.plist
/DisableExtensions/AMDLegacySupport.kext/Contents/Info.plist
/DisableExtensions/AMDRadeonX3000.kext/Contents/Info.plist
To remove any doubt, could you load these kexts one by one and see if the temperature drops?
AMDLegacySupport.kext
ATIRadeonX2000.kext
AMDRadeonX4000.kext
AMDRadeonX4100.kext
No difference with the 1.5.1 version of those kexts I pulled from the 10.12.5 update I did earlier using sudo kextutil -r /AMD_10.12.5_Kexts/ ...
Is there any difference between this command and kextload or do they both accomplish the same thing? They show up as loaded in kextstat.
Should I try other versions? I'm assuming that since I didn't crash when I loaded them I'll probably get the same result as with the other ones.
Is there any difference between this command and kextload or do they both accomplish the same thing? They show up as loaded in kextstat.
Should I try other versions? I'm assuming that since I didn't crash when I loaded them I'll probably get the same result as with the other ones.
The first command would be kextload. So if you had problems, you would execute kextutil to see more information.
Both the kextload and kextutil commands load the kext.
kextutil and kextlibs are commands to do a more thorough check if an error occurs while loading a kext.
Update:
I do not know if you would try a reinstallation of the system. I do not know if any configuration file is in trouble.
Then remove all kexts AMD.
Then load the kexts removed one by one in Terminal after login.
Use the same kexts that were installed on the hard disk (1.5.1). You will install them manually.
AMDLegacySupport.kext
AMDRadeonX3000.kext
AMD6000Controller.kext
Last edited:
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?
You didn't list AMD(Legacy)Framebuffer.kext, is that one not relevant anymore or should I load that one too?