Clover v.2 Instructions - Page 3 - Clover Development
How to speedup Clover boot
There is usual claim from novices that Clover is too slow (or hang). Let us consider this question carefully.
If you try Clover first time then it is logically that you install it onto USB stick and set debug-log to be created. This is the reason of slowness #1.
<key>Boot</key> <dict> <key>Log</key> <false/>
This is wrong key name, I will change the key to "Debug" (since rev3064) that will reflect its appointment. Boot.log will be created even with "False", it just be in memory and accessible in system if booted.
When "true" the "debug.log" will be Open-Write-Close on every line guarantying you will found the file even after hard-reset.
The file will be saved in /clover-partition/EFI/CLOVER/misc/ folder is the partition is FAT32 to help you understand what is the reason of hang is any. The process ve-e-ery slo-o-ow. With my USB stick I have to wait about 10 minutes to enter GUI.
Set "false" here!
I also will kindly recommend to install Clover on HDD that times faster then USB. Why not? You want to keep Chameleon here? Yes, it is possible. Clover and Chameleon can live on the same partition with the same boot sectors. Boot sectors from Clover distribution are able to boot Chameleon as they are comes from them. But not vice versa. Chameleon's boot1h is not able to boot Clover because of its restriction.
OK. The partition will looked like this
total 22487 drwxrwxrwx 1 slice staff 2560 18 дек 17:17 . drwxrwxrwt@ 8 root admin 272 19 дек 10:54 .. drwxrwxrwx 1 slice staff 1024 29 окт 11:17 EFI drwxrwxrwx 1 slice staff 2048 4 апр 2014 Extra -rwxrwxrwx 1 slice staff 482816 3 дек 15:54 boot -rwxrwxrwx 1 slice staff 268256 6 авг 2011 boot2 -rwxrwxrwx 1 slice staff 367589 4 апр 2014 boot3 -rwxrwxrwx 1 slice staff 383562 14 июл 2009 boot4 -rwxrwxrwx 1 slice staff 450048 17 дек 17:37 boot5 -rwxrwxrwx 1 slice staff 482816 28 окт 13:34 boot6
EFI/ - a folder for Clover's files
Extra/ - a folder for Chameleon files
boot is current bootloader. For my case it is Clover BiosBlockIO, renamed from boot7.
boot2 is Chameleon
boot3 is Clover-32bits
boot5 is Clover with low-ebda (rev3061+)
At the computer start when I see "Booting from hard drive..." I can press a digit 2,3,5 to choose a bootloader.
I just want to say you can install Clover on HDD even if there is Chameleon presents here.
Less feature - faster boot, more features - slower boot. What do you want, powerful bootloader or fast bootloader?
The compromise should be found when you study all Clover's features.
For the first time I may propose minimal setting to boot into system.
Do you want to see all possible systems and entries in main menu? And you have four drives with tens partitions each.
Scanning all partitions will take a time. I even saw 80 seconds in real life.
<key>GUI</key> <dict> <key>Scan</key> <dict> <key>Entries</key> <false/> <key>Legacy</key> <false/> <key>Tool</key> <false/> </dict>
Use custom entry to set only that entry that you want to see
<key>GUI</key> <dict> <key>Custom</key> <dict> <key>Entries</key> <array> <dict>
See more instructions elsewhere.
If you have Windows with a couple of files then scanning it will be very slow. DIsable NTFS.efi driver to prevent it!
Too many drivers in /EFI/CLOVER/drivers64*/ folder. Some third party driver may hang or slow respond. Test it separately when needed.
Big theme chosen. More graphics, more animations - slow boot. But very nice looking!
For first start you may choose Theme=embedded. This is fastest theme.
Mouse slow response. Clover GUI can be controlled by a mouse. But the driver can understand only part of market. Good mice: Logitech, KYE systems, Microsoft. Bad mice: noname.
Disable mouse in config.plist
<key>Mouse</key> <dict> <key>Enabled</key> <false/> <key>Speed</key> <integer>0</integer> </dict>
Reason #6. Slow HFS+ driver.
Official release of Clover contains VBoxHFS.efi driver. It is very good, it understand links sft and hard, it understand aliases, but slow.
Apple's driver HFSplus.efi is much faster but we have no license to distribute it. Take it somewhere (here #3 ) and place it into /EFI/CLOVER/drivers64*/ folder. And it will works instead embedded driver. (since rev 3043).
Since Clover revision 3063 you may see boot process on the screen to understand why it is soo slow.
boot-process.png 12.75KB 181 downloads