Jump to content

Clover and multiple disks/OS versions


manta
 Share

4 posts in this topic

Recommended Posts

Hi,

 

Hope this is the correct place to post this - seems that I can't start topics in the Clover forum.

 

Anyway - been using Clover for a few months, it works great and it boots a lot faster than Chameleon.

 

I have a question - I have 3 separate disks with 10.8, 10.9 and 10.10 on them.

 

Should I be installing Clover to all the drives?

 

Whichever UEFI disk I try to tell the Bios to boot from, it seems to always boot to the Clover menu on the 10.8 disk.

 

Is it only necessary to install Clover on 1 of the disks?

 

Thanks for any advice.

Link to comment
Share on other sites

  • 1 year later...

Please excuse me for reopening this old topic...

 

Can clover use config.plist per OsX version ?

Real example/problem:

 

I have installed Sierra (disk0p2) and Yosemite (disk0p3) on HDD and the machine boots UEFI to one clover partition (disk0p1)

Now, Sierra to boot needs the flag nv_disable=1 because the GPU (Geforce 520) doesn't let Sierra boot...

The Yosemite boot without problem...

 

What if i need to set that flag only to Sierra (10.12) in config.plist... ?

The project could have some "overide" in some manner... is it?

 

Best regards.

Link to comment
Share on other sites

  • 3 weeks later...

Please excuse me for reopening this old topic...

 

Can clover use config.plist per OsX version ?

Real example/problem:

 

I have installed Sierra (disk0p2) and Yosemite (disk0p3) on HDD and the machine boots UEFI to one clover partition (disk0p1)

Now, Sierra to boot needs the flag nv_disable=1 because the GPU (Geforce 520) doesn't let Sierra boot...

The Yosemite boot without problem...

 

What if i need to set that flag only to Sierra (10.12) in config.plist... ?

The project could have some "overide" in some manner... is it?

 

Best regards.

 

You can surely do this, by adding Custom Entries. in the GUI Section -> Custom of config.plist

The Example below shows two Entries, and you can edit the boot flags in the AddArguments Section.

<key>Entries</key>
<array>
    <dict>
        <key>Volume</key>
        <string>El Capitan</string>
        <key>VolumeType</key>
        <string>Internal</string>
        <key>FullTitle</key>
        <string>Apple Mac OS X El Capitan 10.11.6</string>
        <key>Hidden</key>
        <false/>
        <key>Disabled</key>
        <false/>
        <key>Type</key>
        <string>OSX</string>
        <key>AddArguments</key>
        <string>kext-dev-mode=1 rootless=0 -v</string>
        <key>InjectKexts</key>
        <true/>
        <key>NoCaches</key>
        <false/>
    </dict>
    <dict>
        <key>Volume</key>
        <string>Eraser</string>
        <key>VolumeType</key>
        <string>Internal</string>
        <key>FullTitle</key>
        <string>Apple Mac OS X Temporary</string>
        <key>Hidden</key>
        <false/>
        <key>Disabled</key>
        <false/>
        <key>Type</key>
        <string>OSX</string>
        <key>AddArguments</key>
        <string>kext-dev-mode=1 rootless=0 -v -f</string>
        <key>InjectKexts</key>
        <true/>
        <key>NoCaches</key>
        <false/>
    </dict>
</array>
  • Like 1
Link to comment
Share on other sites

 Share

×
×
  • Create New...