Contribute
Register

Clover config.plist deteriorates across multiple usages.

Status
Not open for further replies.
Joined
Feb 27, 2016
Messages
7
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. 0
8.0.1 El Capitan.

I'm very much a noob when it comes to building hacks—I did my first one this weekend—but my first build was pretty much a resounding success. Having said that, I may not understand the desired behavior of Multibeast in this regard.

What I observed is that running Multibeast multiple times and trying different settings will result in a polluted Clover config.plist. I managed to brick my box to the point where I was stuck forever at the apple progress bar. I thought the issue was a kext I loaded through choices in multibeast, so I went through the steps of single user and/or recovery console kext cache deleting and cache rebuilding, but I never realized success doing this. I booted up into my existing install with my unibeast boot media and figured I must have a screwed up clover config, so I re-ran Multibeast, loading my saved profile that worked, then installing. Still no joy. After a bit of troubleshooting it was obvious that my clover config.plist still contained modifications that had come from previous selections that I was no longer selecting (such as the hdmi audio fix that installs the intel frame buffer mod.) While booted up via the unibeast install media, I moved my existing EFI directory structure out of the way, loaded up Multibeast, loaded my saved good profile, and re-built. Now my EFI clover config.plist was different and looked like my EFI backups.

My impression was that each time I clicked build I was getting a fresh translation of my selections to a fresh clover configuration. I can understand use cases where only "merging" or "updating" the clover config.plist would be desired, but I had no idea this was the case and I certainly wasted a lot of time discovering that this was the case. It sure seems like it is a bug. Having said that, if the merge/update behavior is needed, such as in the case of preserving existing manually created configuration, perhaps a merge vs overwrite option with a tool tip that explains the difference would be good, or perhaps a "custom plist entries" that can be stored in the multibeast saved profile on disk and could be applied at build time combined with the user's selections. Either of these is more ideal than having it appear that your build is fresh when it is not.

Thanks for your consideration. I've been *very* impressed with the whole hackintosh build and install. I followed the guide, picked out hardware and purchased it Saturday. I had a completely working system built from scratch within 24 hours including drive time, assembly time, install time, and troubleshooting of fixing of my USB3 issues.

Wayne
 
Nice job on the build Wayne. Will you put all the main parts of your hardware in your profile so that we can see what you are working with. It sounds like you may need to do a clean install and follow a specific User Build guide for your hardware.









Put Graphics CPU and motherboard
here:

 
I will post up what I have soon, plus a "success" thread with the one real issue I ran into (usb3 oddities). All of it is fixed now though, so no need to do a fresh install. I wiped out my EFI and extensions directory (and cache) and re-ran multibeast with my known good profile and everything is golden. The only remaining issue is sometimes audio goes away after sleep, but I don't use sleep and will probably continue troubleshooting that.
 
Status
Not open for further replies.
Back
Top