Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Could not open Info.plist file #77

Closed
SchmollTroll opened this issue Jul 26, 2018 · 12 comments
Closed

Error: Could not open Info.plist file #77

SchmollTroll opened this issue Jul 26, 2018 · 12 comments

Comments

@SchmollTroll
Copy link

Hi there,

MANY THANKS for your work - my Moms 2010 MBP constantly crashing with kernal panic driving her crazy!

When I tried your tool with the admin account on this book I get the following output with an error:

 | Checking compatibility
 MBPModelVersion :  MacBookPro6,2 ➔ Compatibility : OK ✓
  | macOS version : 
 OS X 10.11
  | Checking SIP Status
 SIP Disabled
  | Searching for AppleGraphicsPowerManagement.kext
 AppleGraphicsPowerManagement.kext found
  ********** Starting MBP GPU Fix **********
 Disabling Kext Signing verification :  ✓ 
 Copying Info.plist file
 Previous Info.plist file removed
 Could not open Info.plist file
 ********************* MBP GPU Fix FAILED *********************

Any ideas for me?

@julian-poidevin
Copy link
Owner

Closing issue : This was resolved by changing user account to an admin one (see #78)

@SchmollTroll
Copy link
Author

Thanks for your answer,
unfortunately not.
First I tried as a non-admin user (resulting in issue 78 :-)

Since I got an error there because of missing admin rights I switched to the admin account and here I got the error described above -> Could not open Info.plist file

@julian-poidevin
Copy link
Owner

Please can you try to apply the suggestions I made on issue #65 ?

Tell me if you need more help.

@eberlyjm
Copy link

eberlyjm commented Aug 3, 2018

Hello and thanks for the GPU fix program. I think my problem is similar (or the same) to the one on this thread. When I try to run the program (from admin user), I get the log below with FAILED message. Any help would be greatly appreciated.

| Checking compatibility
MBPModelVersion : MacBookPro6,2 ➔ Compatibility : OK ✓
| macOS version :
OS X 10.11
| Checking SIP Status
SIP Disabled
| Searching for AppleGraphicsPowerManagement.kext
AppleGraphicsPowerManagement.kext found
********** Starting MBP GPU Fix **********
Disabling Kext Signing verification : ✓
Copying Info.plist file
Patching Info.plist

  • FindChild - key|MacBookPro6,2
  • NextSibling - dict
  • FindChild - key|LogControl
  • ModifyIntValue - integer|1
  • FindSibling - key|Vendor10deDevice0a29
  • FindSibling - key|BoostPState
  • FindSibling - key|BoostTime
  • FindSibling - key|Heuristic
  • FindSibling - key|IdleInterval
  • ModifyIntValue - integer|10
  • RemoveSiblingLabel - P3HistoryLength Not found
  • FindSibling - key|SensorSampleRate
  • ModifyIntValue - integer|10
  • FindSibling - key|Threshold_High
  • FindSibling - key|Threshold_High_v
  • FindSibling - key|Threshold_Low
  • FindSibling - key|Threshold_Low_v
    Info.plist successfully patched
    | Loading Kernel Extension
    Removing existing kext in tmp : ✓
    Copying actuel kext into tmp : ✓
    Copying patched Info.plist into kext : ✓
    Changing permission of kext : ✗ : cp: /tmp/AppleGraphicsPowerManagement.kext/Contents/Info.plist: No such file or directory

Removing existing kext : ✓
Copying patched kext into Extension : ✓
Loading modified kext : ✓
********************* MBP GPU Fix FAILED *********************

@SchmollTroll
Copy link
Author

I had the same problem.
Resetting SMC and PRAM helped me in my case.

@eberlyjm
Copy link

eberlyjm commented Aug 5, 2018

Thanks SchmollTroll. I reset SMC and PRAM. That made a noticeable difference, but then was getting an error saying that the file was missing. I assumed it meant AppleGraphicsPowerManagement.kext. It was there, but I tried reinstalling it with KextBeast. The program did not seem to be working either. But after the 4th try, the GPU Fix stopped giving me the error and ran with success. After restarting, my MacBook ran for over an hour without crashing (it had been crashing literally every 1-3 min after startup). I was excited thinking it was fixed. But alas... after some time I got the kernel panic again and from there on out it was just as before (seems to be even worse, actually). I've reran the GPU Fix program several times now, but with the same result (does not fix it). I guess this is a dead end, unless someone has other ideas...

@eberlyjm
Copy link

eberlyjm commented Aug 8, 2018

(in case this is helpful to anyone else…)
I think I may have figured out why the fix hadn't resolved the kernel panic in my case. I had various problems that kept me from successfully running hte GPU Fix and in the course troubleshooting I mistakenly installed AppleGraphicsPowerManagement.kext in the /library/extensions/ folder instead of in /system/library/extension/. I don't know much about ktext and how it works, but when I went back and deleted it and reran the GPU Fix, I stopped crashing. I've now been running the MacBook Pro for 2 days without a crash (previously it was crashing almost as quickly as the laptop could start up).

@julian-poidevin
Copy link
Owner

@SchmollTroll Can you please confirm that your issue is solved ?

@SchmollTroll
Copy link
Author

It's the notebook of my mother so I don't have direct access to it most of the time but since she always called me when it crashed (and she did not call me during the past days) it seems to be solved.

@SchmollTroll
Copy link
Author

Some days ago I worked with this book for about 5 hours (most of the time I used VMware Fusion to run some tools to sort my mothers TV channels :-P ) WITHOUT any crash.

Today my mom tries to edit some photos and had 3 kernel panics...

@julian-poidevin
Copy link
Owner

Maybe she updated MacOS. You have to re-apply the patch after every OS update.

Re-apply the patch and let me know.

@SchmollTroll
Copy link
Author

TNX! Good hint - I think there was a security update!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants