Posted 12 May 2014 - 11:02 AM

Slice

InsanelyMacaholic

Local Moderators

3,741 posts

Gender:Male

Location:Moscow

Blocking Bad Kext

I encounter a bad situation when I installed a kext (it is GeforceSensor) that caused KP. I install it into SLE without checking if it works.Then I can't boot even with -x, -v, -s. It always loaded and panics.So I created a revision of Clover that is able to block one kext in /S/L/E.Test with NVClockX.kext. It is not vital for system so I can experiment with it.

It is loaded! Why? I think it is loaded by kernel that is not affected by FSInject.efiBut it is loaded much later and give me an ability to boot with -s before the KP will occur.Yes, this is workaround in the case above.

Posted 09 October 2014 - 12:24 PM

Rev 2948+Briefly, Clover writes Boot#### options for each entry in MainMenu and set BootCurrent to last booted entry if all correct.

Requirements: UEFI boot with real NVRAM present.

Usage:Enter CloverGUI, navigate to "Clover Boot Options" in the tools row of main menu and press "Add Clover boot options for all entries".screenshot5.png194.35KB64 downloadsIf you once do this no need to repeat. It will be saved in NVRAM forever.When you change the main menu by adding new volume, new partition, new OS then you should first remove old options: "Remove all Clover boot options"second add all options again.Print them into boot.log to see what you have.

When you started an OS by some entry in the Menu then this entry will be saved as "BootCurrent" and next boot will happen with Clover knowing DefaultVolume and DefaultLoader as in last boot.

Advantages1. It will remember last boot to Windows or even to legacy boot (not checked but I hope it is).2. Bios menu will contain these entries.141008204117.png164.45KB55 downloads

Posted 19 December 2014 - 11:14 AM

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.

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.