![]() This seems to be an Apple bug triggered by some update in the past couple of months, at least on my MBP. You can't get back the highest resolution and have black bars at the top and bottom of the screen (the higher resolution setting is not available on the integrated card, and for some reason the system won't permit the change). No problem.ħ - Open Console.app, type into search: gfx0 and check if g-state changes if working!ĪppleGraphicsPowerManagement.kext 10.11.On some Macs with dual cards, such as my 2011 MBP, use of the Energy Saver automatic graphics switching will trigger a display problem when logging out and logging back in: the display will be stuck on a lower-resolution option until restart. Maybe smc is responsible.Īfter osx loading i can change to discrete cpu only or in automatic graphics switching. Discrete gpu only (automatic graphics switching unselected) not working properly, and, i don't know why. Here, in my tests is important every boot must be in automatic mode. Remember, the option automatic graphics switching selected always. You can check this on: About System Information -> Extensions) (make sure the AppleGraphicsPowerManagement.kext is loaded. SIP is important to safety, but, we are good guys, we'll know to keep the system safe!ģ - Open Extensions folder (System/Library/Extensions), copy AppleGraphicsPowerManagement.kext to desktop (or other folder), open the ist into editor (I used the PlistEdit Pro.app), and change the values like writing up.Īttention: verify if your model is 0x0a29 really.ĥ - Use Kext Drop.app or Kext Utility.app (this is not marketing, okay?) Only to facilitate the process to instal this kext, but before, delete the AppleGraphicsPowerManagement.kext into extensions folder.Ħ - (This is important step) Leave the automatic graphics switching select (System Preferences - Energy Saver), if you are using gfxCardStatus.app, same thing!. ![]() You can check this on: About System Information -> ExtensionsĢ - Disable SIP (boot into recovery mode, terminal: csrutil disable) ACPI_SMC_PlatformPlugin.kext (IOPlatformPluginFamily.kext).Only so.ġ - Verify that the file is the original and this loaded (there are mods that remove these files) and if they are the original (Apple signed): Perfect values? I do not know, but it is working for me. (attention: only try this if you really have the problem gpu panic). If you want to try, these are the values changed in the ist: ![]() Not bad.īattery consumption does not change much. ![]() I solved the problem by keeping it always at G-State 2 (medium speed), that the problem of stabilizing the voltage not compromise the gpu work.Īnd the performance? Exemple: Cinebench, default (G-state 0) i've about 15fps, with g-state 2 (medium speed): 10fps.). G-state 0 (maximum speed) and G-state 3 (lowest speed). Are related to the thresholds inside AppleGraphicsPowerManagement.kext, like this: This is to maximize performance and battery consumption. G-States go from 0 to 3, are related to the gpu use (idle/load). The problem in the use of nvidia is not the gpu, but the stabilization of the voltage when the gpu changes from g-state 2 to 0 (or 2 to 1), causing the known issues. I discovered that this problem happens every time that g-state change between 2 to 0 (or 2 to 1). I have the famous MacBook Pro 6,2 with GT330m (0x0a29 model). Well, after years i found a solution (so mine?).
0 Comments
Leave a Reply. |