Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 08/09/2021 in all areas

  1. No way @Ploddles I reverted to an old bios and it is a bit better but always fails... then...I have used my wife PC to first installation step 🙂 I think it is a combination of new gpu and bios to this very weird behaviour I have less problem to install any OSX in this pc rig...
    1 point
  2. After several more crashes (everything locks up, freezing mouse–––the computer if left alone will re-boot; if impatient, a forced shutdown is required), I think I've isolated the problem... Each new kext seems okay. I can have a stable computer if one or both are running. I can even run the AMD Power Gadget app and the computer is stable. The problem is if the app has the feature to "Launch in menu bar at login" enabled (StartAtLogin in the plist file discussed below) through it's menu, shown below. Once this is enabled and the computer re-booted, the menu is no longer accessible to disable and now the computer locks up in less than 60 seconds after each re-boot due to the auto-login feature of the AMD Power Gadget app. I had to boot into Big Sur (or use another EFI where the AMD Spinach kexts were not enabled) to remove the AMD Spinach plist file. This file is located in the User/Library/Preferences folder as shown below. You can either delete it or better is to edit and set "startAtLogin" to "NO" (and while you're at it, also set "startAtLoginAsked' to "YES" to avoid a pop-up window shown in Spoiler below). In looking more deeply in the CrashReport log, one can find the following (an excerpt from that log file). I'll provide this info to the developer and maybe they can provide a fix. The bottom line, in its present state, the AMD Power Gadget system is usable (at least for me), if the Auto-Login feature of the AMD Gadget app is not activated. ADDENDUM: I found out through playing with the wtf.spinach.AMD-Power-Gadget.plist file that the menu is inactivated if "StartAtLoginAsked" is enabled and "statusbarenabled" is set to "YES". I'm leaving "statusbarenabled" set to "NO" in order to have access to the AMD Power Gadget app's menu bar. After writing the above, the system began locking up even if only the AMDRyzenCPUPowerManagement.kext was enabled (and no AMD Power Gadget app was running). This is after a morning of the computer running fine with both kexts enabled but no app running. It was only after enabling auto log-in did all the troubles start once more. Odd. I've presently disabled both kext files and have contacted the developer.
    1 point
  3. In download un altro aggiornamento....
    1 point
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.