Jump to content
ErmaC

Clover General discussion

19,137 posts in this topic

Recommended Posts

Advertisement

Clover Configurator currently doesn't support:

- Devices/Arbitrary (it will remove the entire section if present!)

- Disabled flag in ACPI/DSDT/Patches (it will remove the flag)

- Disabled flag in ACPI/KernelAndKextPatches/KextsToPatch (it will remove the flag)

- there may be others...

 

In addition some DSDT/Fixes are misspelled. I don't have a complete list, but as an example... if you edit a file with FIX_TMR_40000, it will remove it because it is misspelled as FiX_TMR_40000 in the CC code (note lower case 'i'). I'm not sure if there are other examples.

 

Also, the tool adds settings that were not previously present, and re-orders everything. It is mess if you use source control (git/svn).

 

Problem is one of design. Removing entries that CC doesn't understand is bad design. The file contents should be kept in original order. Entries that are not present should not be added.

 

Noob trying to learn.

I think I just read the above quote and more puzzle pieces coming together.

So Clover is the bootloader (Only used to get software installed and keep the EFI in order?)

Clover Configurator is NOT made by the same people and removes things that coders of clover would not have done?

I am looking at starting over with a new clover setup because of trying tooo many pathches and bad kext left my current clover set up a little confusing.

If the above is true then I am assuming that I

1.) Need to find out how to create a new clover install without using configuator.

2.) Do all edits through DSDT editor like MaciAsl and Plist editors

3.) All kekts can be moved to the correct S/L/E or Extra folder and injected using terminal or Kext injector software (The version mentioned in the beginning of this forum)

4.) Clover is more manual than clover configurator but when you know what you are doing that is the best way?

Sorry if I am missing things it is just that the more I read the more confused i get especially being new and sometimes I will be reading something only to find out I do not need it for the build I have.

Share this post


Link to post
Share on other sites

So Clover is the bootloader (Only used to get software installed and keep the EFI in order?)

 

Clover is an extended Boot Manager to provide an OS X-compatible environment, it doesn't keep anything EFI "in order".

 

Clover Configurator is NOT made by the same people and removes things that coders of clover would not have done?

 

Aye.

 

3.) All kekts can be moved to the correct S/L/E or Extra folder and injected using terminal or Kext injector software (The version mentioned in the beginning of this forum)

 

There is no 'Extra' folder for Clover, use EFI/Clover. Putting a kext into Clover's folder doesn't require Terminal or extra software.

 

4.) Clover is more manual than clover configurator but when you know what you are doing that is the best way?

 

I have no idea what that means, but if you are asking that using the Clover installer is 'more manual' than using the Configurator, there practically isn't any difference. The only thing the Configurator provides is a fancy GUI rather than the bare plist content.

Share this post


Link to post
Share on other sites

The BooterConfig entry explained here:             #7            

/* Bitfields for boot_args->flags */
#define kBootArgsFlagRebootOnPanic    (1 << 0)
#define kBootArgsFlagHiDPI            (1 << 1)
#define kBootArgsFlagBlack            (1 << 2)
#define kBootArgsFlagCSRActiveConfig	(1 << 3)
#define kBootArgsFlagCSRPendingConfig	(1 << 4)
#define kBootArgsFlagCSRBoot          (1 << 5)
#define kBootArgsFlagBlackBg          (1 << 6)
#define kBootArgsFlagLoginUI          (1 << 7)

..is what you need (bit fields with black options)

Thanks for the reply I'm confused by (1 << 6).  I believe I need something like this below but what flag for black I don't know how to convert to number value. 

 

<key>RtVariables</key>

    <dict>

        <key>BooterConfig</key>

        <string>??</string>

    </dict>

Share this post


Link to post
Share on other sites

Clover is an extended Boot Manager to provide an OS X-compatible environment, it doesn't keep anything EFI "in order".

 

 

Aye.

 

 

There is no 'Extra' folder for Clover, use EFI/Clover. Putting a kext into Clover's folder doesn't require Terminal or extra software.

 

 

I have no idea what that means, but if you are asking that using the Clover installer is 'more manual' than using the Configurator, there practically isn't any difference. The only thing the Configurator provides is a fancy GUI rather than the bare plist content.

Thanks for replying. As far as the difference between them yes your explanation is what I was thinking.

 

The Extra folder is throwing me off a little I will need to check what I have set up.

 

2 more questions.

 

1.) Does clover configurator use the clover folder? So if I manually access the EFI/Clover folder on my hack then I am in the folder that clover installer made?

 

2.) If I just add .kext files to the kext folder inside the EFI/Clover folders that have the operating numbers on them then they are injected?

  2a Is there a way to see what kexts are loaded? The reason I ask is I think I have some that I need to remove because of the configurator and some old youtube videos.

Share this post


Link to post
Share on other sites

Thanks for the reply I'm confused by (1 << 6).  I believe I need something like this below but what flag for black I don't know how to convert to number value. 

 

<key>RtVariables</key>

    <dict>

        <key>BooterConfig</key>

        <string>??</string>

    </dict>

The example show 0x28 for Yosemite and El Capitan... why not use that?

Share this post


Link to post
Share on other sites

Guys, any idea how to fix a non-bootable system due to dual-monitors? It boots fine with a single monitor, but it goes into some sort of boot loop (monitor goes to sleep) when loading second stage boot.

 

Is there a way to fix this via device-properties? Or something from Clover?

Share this post


Link to post
Share on other sites

Thanks for the reply I'm confused by (1 << 6).  I believe I need something like this below but what flag for black I don't know how to convert to number value. 

1<<6 is "1 shift left 6". This is C code.

 

Given binary representation, "1 shift left 6" is the same as 0x40 (64 decimal).

Share this post


Link to post
Share on other sites

Hi Guys,

 

and again I need some help. As I had written some topics in the past few weeks about my x58 update from 10.9.5 chameleon to 10.10.5 clover I was stucked at many different steps. But in the end, I'am up and running with my clover 3220 EFI only installation on my Samsung SSD connected to my ICH10 SATA2 port, dsdt fixes for Audio, Trim (which does not work), USB3.0 from my pci-e Asus U3S6 extention card, some HW Monitoring working, GTX970 fixes etc.

 

But now, I'm stucked again regarding booting my Yosemite Installation using clover but not connecting the SSD to the ICH10 SATA2 port instead using the SATA3 Port on the U3S6 pci-e card. In my newest Asus P6T-SE Bios, every SSD attached to the pcie extention card is shown up (IDE Card which is AHCI redirected due to some bios post messages of the Asus pcie card and the customer support). When I use a second SSD with a mirrored Yosemite installation, clover in efi only installation, boot0af information, my config, kext, dsdt etc. this puppy boots from the ICH10 (sure it should), but not from the pcie extention card. first boot stage does work, but then it fails to boot into second stage where I can choose my different ssd os x yosemite and windows installations. instead, it boots into my main Yosemite Samsung SSD clover installation where I can boot into Yosemite Main installation, but the mirrored Yosemite SSD attached to the pcie extention card is not recognized.

A member, Chris, posted to my questions in another topic, that he uses another expansion card on another motherboard without any problems (for booting up using clover): http://www.insanelymac.com/forum/topic/307003-clover-os-x-el-capitan-usb/?p=2206454

 

Can Anyone give me any advice? Due to some other topics in the internet, the Asus U3S6 should be accepting every possible boot. I haven't tried any Windows installation at the moment as a reference point. 

Share this post


Link to post
Share on other sites

Guys, any idea how to fix a non-bootable system due to dual-monitors? It boots fine with a single monitor, but it goes into some sort of boot loop (monitor goes to sleep) when loading second stage boot.

 

Is there a way to fix this via device-properties? Or something from Clover?

This seems to be a common thing with the newer nvidia cards.  I have the same problem with my 960.  Changing your system definition to imac14,2 is supposed to fix it.  For me that's not an option because my system is too old.

Share this post


Link to post
Share on other sites

This seems to be a common thing with the newer nvidia cards.  I have the same problem with my 960.  Changing your system definition to imac14,2 is supposed to fix it.  For me that's not an option because my system is too old.

Actually this is not for the system in my signature. It's for a GT 630 combined with a i3 3220 @ 3.3 GHz CPU and Gigabyte Z77-DS3H motherboard. But I guess that doesn't help much, does it? :(

 

I feel like this could be pretty easily solved with a device-properties edit. But I just don't know what to edit.

Share this post


Link to post
Share on other sites

I'm not able to boot Recovery HD (the PC reboot itself) with my custom config.plist on a Z77E-ITX. I've made some trial with a pendrive and figure out that I can do it avoiding "Custom Entries" (used to hide three recovery partition) and all the kext to patch booting from USB. Not a big deal, but now I want to do same from the HDD and I don't understand how to boot with this alternative config (named config1.plist) from Clover GUI. I've tried to change in option config with config1, but it does'n work. What I'm doing wrong?
 

Share this post


Link to post
Share on other sites

Thanks for the reply I'm confused by (1 << 6).  I believe I need something like this below but what flag for black I don't know how to convert to number value. 

 

<key>RtVariables</key>

    <dict>

        <key>BooterConfig</key>

        <string>??</string>

    </dict>

You can try to enable bit 2 = 4 or bit 6 = 0x40 (64) BlackBG background ??, please correct me if i am wrong

I have tried to enable the HiDPI bit but no changes 

Share this post


Link to post
Share on other sites

kBootArgsFlagBlack is the bitfield to set to have the black background + white progress bar (kBootArgsFlagHiDPI to have a bigger one, as well for the logo)

 

 

that is what you can find in the xnu kernel in El Capitan:

 

#define kBootArgsFlagRebootOnPanic (1 << 0)

#define kBootArgsFlagHiDPI (1 << 1)

#define kBootArgsFlagBlack (1 << 2)

#define kBootArgsFlagCSRActiveConfig (1 << 3)

#define kBootArgsFlagCSRConfigMode (1 << 4)

#define kBootArgsFlagCSRBoot (1 << 5)

#define kBootArgsFlagBlackBg (1 << 6)

#define kBootArgsFlagLoginUI (1 << 7)

#define kBootArgsFlagInstallUI (1 << 8)

 

...here in Yosemite:

 

#define kBootArgsFlagRebootOnPanic (1 << 0)

#define kBootArgsFlagHiDPI (1 << 1)

#define kBootArgsFlagBlack (1 << 2)

#define kBootArgsFlagCSRActiveConfig (1 << 3)

#define kBootArgsFlagCSRPendingConfig (1 << 4)

#define kBootArgsFlagCSRBoot (1 << 5)

#define kBootArgsFlagBlackBg (1 << 6)

#define kBootArgsFlagLoginUI (1 << 7)

 

 

Share this post


Link to post
Share on other sites

Hi Guys,

 

and again I need some help. As I had written some topics in the past few weeks about my x58 update from 10.9.5 chameleon to 10.10.5 clover I was stucked at many different steps. But in the end, I'am up and running with my clover 3220 EFI only installation on my Samsung SSD connected to my ICH10 SATA2 port, dsdt fixes for Audio, Trim (which does not work), USB3.0 from my pci-e Asus U3S6 extention card, some HW Monitoring working, GTX970 fixes etc.

 

But now, I'm stucked again regarding booting my Yosemite Installation using clover but not connecting the SSD to the ICH10 SATA2 port instead using the SATA3 Port on the U3S6 pci-e card. In my newest Asus P6T-SE Bios, every SSD attached to the pcie extention card is shown up (IDE Card which is AHCI redirected due to some bios post messages of the Asus pcie card and the customer support). When I use a second SSD with a mirrored Yosemite installation, clover in efi only installation, boot0af information, my config, kext, dsdt etc. this puppy boots from the ICH10 (sure it should), but not from the pcie extention card. first boot stage does work, but then it fails to boot into second stage where I can choose my different ssd os x yosemite and windows installations. instead, it boots into my main Yosemite Samsung SSD clover installation where I can boot into Yosemite Main installation, but the mirrored Yosemite SSD attached to the pcie extention card is not recognized.

A member, Chris, posted to my questions in another topic, that he uses another expansion card on another motherboard without any problems (for booting up using clover): http://www.insanelymac.com/forum/topic/307003-clover-os-x-el-capitan-usb/?p=2206454

 

Can Anyone give me any advice? Due to some other topics in the internet, the Asus U3S6 should be accepting every possible boot. I haven't tried any Windows installation at the moment as a reference point. 

    That card does not have an EFI bios on it so will not be bootable or seen until the system boots unless you use legacy boot.  So this is not a Clover problem.

Share this post


Link to post
Share on other sites

@arsradu For trial & error purposes, injecting our additional gpu properties via efistrings/dsdt is such of bad choices. Do that after successfully reach the desktop, and lock your fixed settings with efistrings/dsdt later. No need to delete previously efistrings since Clover now able to en/disable that setting from boot gui. You may try to reverse "AAPL,boot-display" value to other working port.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   1 member

  • Similar Content

    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By AppleBytes
      OK, I've searching for days trying to gather up the tools to make my current install work correctly. I'm well on my way. But all the links to the things I currently must have were apparently nuked "during a forum upgrade". :(
      As far as EFI Studio goes; I can find many links to it. But for Insanelymac, they're broken (due to the upgrade), or for the Netkas site, they're links to either Rapidshare, or Mediafire that also no linger exist. I see many users here indicating that they used it to tweak their DSDT. But the web (google/duckduckgo), Instanelymac, and Netkas seem to have no idea where it's gone.
      Could some kind soul please share a copy, or a link? I'm a loooong time hacker, and would love to bring it back to life. In fact, I'd love to improve it -- or at least bring it up to current times. If only I knew where it was.
      Thank you for all your time, and consideration.
       
      --Chris
       
    • By SoThOr
      This was spurred on from a discussion in the Clover General thread. Where there was a debate on bcdedit being able create/read/edit (U)EFI Boot entries. I didn't think it appropriate to post all this information there and somebody may want to make use of this and its likely to get lost in that massive thread.
       
      Out of curiosity I decided to see if I could create an EFI entry using bcdedit. What can I say I like a challenge.  Whilst is not a documented method by Microsoft, as it turns out in a round about way it IS possible to create an EFI entry using bcdedit and these are the steps I went through to add UEFI Shell located on a USB stick to the EFI entries. 
       
      Third party software is available that can create and edit UEFI entries from Windows with better support and more features. I'm just making this information available in case those options are unavailable. 
       
      DISCLAIMER - This is not a supported method. Use at your own risk. I recommend backing up your BCD/Firmware variables/settings beforehand.
       
      1) Copy {bootmgr} entry.
      C:\Windows\System32>bcdedit /copy {bootmgr} /d "UEFI Shell" The entry was successfully copied to {34e8383c-73a7-11e9-9cb0-94de8078a7b5}. 2) Edit the new entry using the new GUID bcdedit generated in the copy step.
        a) Set the device and path for UEFI shell on my USB stick.
      bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} device partition=G: bcdedit /set {34e8383d-73a7-11e9-9cb0-94de8078a7b5} path \EFI\SHELL\SHELLX64.efi   b) Clean up some of the stuff that was copied from {bootmgr} (optional as far as I can tell, just makes things tidier in bcdedit)
      3) Put the new EFI entry first in boot order. (optional)
       
      After completing the steps above, here is what "bcdedit /enum firmware" shows:
       
      I shutdown my computer and when I turned my computer back on it booted up into UEFI Shell. After exiting the shell my PC went on to boot Windows.
      Here is the resulting dump using "bcfg boot dump -v" from that shell:
       
      You may notice that the shell shows as "Windows Boot Manager" in the bcdedit output. This I believe is because of the "WINDOWS" at the beginning of the option data that bcdedit added to the EFI Boot entry. I also believe this why bcdedit shows my Windows 8 installation as "Firmware Application" because it has no option data. I don't know how to remove this data using bcdedit nor do I know how the option data, that bcdedit adds, will affect other EFI applications.

      There might be a way to create the EFI entry without copying the Windows entry but if there is I'm unable to find any documentation on how one would do so. If you use the create command then it just puts it in the BCD and I'm unaware of a way to tell it to create it in EFI instead, other than by doing the above.
    • By cvad
      Small tool to download, compile and build the latest Clover X64 package.
       
       
       

      The script inside is editable.

       
      Enjoy...
       
      Many thanks to the comrade SunKi for help with creating the script.
       
       
       
       
       
      Best thanks - click "Rate File".
       
    • By blxkspell
      Hey!
      As I have 3 Monitors connected, my RX 570 gets arround 50°C while ideling/ web browsing etc. The problem is, that this temp is apparently just the threshold, when the fans start to spin. So the fans start spinning for a minute then they stop for a while again... This is very annoying for me as the rest of my hackintosh is nearly quiet (SSD, 120mm low RPM cpu fan, nearly silent PSU,...), especially when Im using the pc to revise for school. Does somebody know wether its possible to "change" the threshold till the fans start spinning? Like it would probably not be a problem for the gpu at all, if the temp rises to 55°C but therefore be soundless....
       
       
×