Jump to content
ErmaC

Clover General discussion

20,246 posts in this topic

Recommended Posts

3 minutes ago, Matgen84 said:

Sorry for my stupid question of Desktop user: Have got you one partionned disk or two HDD? 


I have multiple SSDs. Currently one for macOS, one for Windows and 2 others for data.
macOS is installed on disk 0 and Clover is on its EFI, windows is on disk 1

Share this post


Link to post
Share on other sites
Advertisement
24 minutes ago, ricoc90 said:


I have multiple SSDs. Currently one for macOS, one for Windows and 2 others for data.
macOS is installed on disk 0 and Clover is on its EFI, windows is on disk 1

 

On each Hack, I have multiple HDDs: macOS is also installed on disk 0 and Clover is on its EFI, windows is on disk 1. There is no issues with Clover r5056 while rebooting from macOS.

 

Share this post


Link to post
Share on other sites
Posted (edited)

I know, my other hacks do work fine. It's just my Precision suffering from that issue. The issue is not revision-specific though, I've always had that issue but never cared about it because I barely reboot :rofl:

However, I have to reboot back and forth between macOS and Windows a couple of times a day now, so it starts to get annoying

Edited by ricoc90

Share this post


Link to post
Share on other sites
20 hours ago, Badruzeus said:

1. For Windows (UEFI) your Custom Entry is missing this:


Path: \EFI\Microsoft\Boot\bootmgfw.efi

2. For Mojave with APFS, take a look sample Volume below (from Clover's preboot.log):


[18]: Volume: PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x0,0x0,0x0)\HD(12,GPT,48508A5E-2847-497C-8EE3-8A4830800A71,0xDC800,0xC000)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,55CCB8D0CAC956428EB419C0AE75EFC6)

As you could see, one Volume contains 3 UUID(s). Referring to @fusion71au guides here, use the last UUID (Little Endian, w/o Dash for APFS "Volume" inside the Container.) On this case is this:


Volume:	55CCB8D0CAC956428EB419C0AE75EFC6

Good luck.

 

So this will fix my customized title and order issue? Booting is not problem at all.

Share this post


Link to post
Share on other sites
Posted (edited)
11 hours ago, pkdesign said:

 

So this will fix my customized title and order issue? Booting is not problem at all.

 

Customized title works if you follow my tutorial linked by @Badruzeus.  The order shown by the Clover GUI in part depends on the order that Clover auto scans the physical media volumes, but the custom entries should appear first if you have done them correctly (confirm by looking at Clover's boot log/bdmesg and seeing a successful "match!").  Note the UEFI Windows loader bootmgfw.efi is usually located in the EFI System Partition (@ \EFI\Microsoft\Boot\bootmgfw.efi), not the main NTFS Windows partition.

 

Eg my clean boot log with just Clover auto volume scan, no custom entries...

2:478  0:000  Found 13 volumes with blockIO
2:478  0:000  - [00]: Volume: PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x0,0x0,0x0)
2:478  0:000  - [01]: Volume: PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x0,0x0,0x0)\HD(1,GPT,C23671C0-6A01-4BC5-9FD0-0766D800CD22,0x28,0x64000)
2:482  0:003          Result of bootcode detection: bootable unknown (legacy)
2:482  0:000          This is SelfVolume !!
2:482  0:000  - [02]: Volume: PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x0,0x0,0x0)\HD(2,GPT,8912DB49-EF98-4DF0-ABB3-C5A58A95D2FA,0x64028,0x639BFB0)
2:486  0:003          Result of bootcode detection: bootable unknown (legacy)
2:486  0:000  - [03]: Volume: PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x2,0x0,0x0)
2:490  0:003  - [04]: Volume: PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x1,0x0,0x0)
2:490  0:000          Found optical drive
2:490  0:000  - [05]: Volume: PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x0,0x0,0x0)\HD(2,GPT,8912DB49-EF98-4DF0-ABB3-C5A58A95D2FA,0x64028,0x639BFB0)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,CA5C06978F8F0D41BBBD4D499B33EDBC)
2:490  0:000  - [06]: Volume: PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x0,0x0,0x0)\HD(2,GPT,8912DB49-EF98-4DF0-ABB3-C5A58A95D2FA,0x64028,0x639BFB0)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,34AD9A994BF6064BB007F726C1B61458)
2:491  0:000  - [07]: Volume: PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x0,0x0,0x0)\HD(2,GPT,8912DB49-EF98-4DF0-ABB3-C5A58A95D2FA,0x64028,0x639BFB0)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,20BFD95D1CE80347A7DD120EAAAAF40A)
2:491  0:000  - [08]: Volume: PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x0,0x0,0x0)\HD(2,GPT,8912DB49-EF98-4DF0-ABB3-C5A58A95D2FA,0x64028,0x639BFB0)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,9C2060E8F6233D40AB4A929F92FE767A)
2:491  0:000  - [09]: Volume: PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x0,0x0,0x0)\HD(2,GPT,8912DB49-EF98-4DF0-ABB3-C5A58A95D2FA,0x64028,0x639BFB0)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,DAA77666C829074EAB26FB9374C23424)
2:491  0:000  - [10]: Volume: PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x2,0x0,0x0)\HD(1,GPT,9CBCF5A7-27F5-4EB2-B696-66F80130A12F,0x28,0x64000)
2:494  0:002          Result of bootcode detection: bootable unknown (legacy)
2:541  0:046  - [11]: Volume: PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x2,0x0,0x0)\HD(2,GPT,394DFB82-0792-4253-BE45-2F2F8656091A,0x64028,0x50BB9B8)
2:544  0:003  - [12]: Volume: PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x2,0x0,0x0)\HD(3,GPT,0CF7B7D3-A54C-4D5D-98AF-6F4B9996EF58,0x515F9E0,0x12605F8)
2:548  0:003  No AudioIoProtocols, status=Not Found
2:548  0:000  === [ InitTheme ] =========================================
2:548  0:000  use daylight theme
2:548  0:000   using embedded theme
2:548  0:000  got embedded sound
2:548  0:000    Channels: 2  Sample rate: 8000 Hz  Bits: 16
2:548  0:000  output to channel 0 with volume 70, len=25600
2:548  0:000   sound channels=2 bits=16 freq=8000
2:550  0:001  sound converted to 48kHz
2:550  0:000  not found AudioIo to play
2:550  0:000  sound play end with status=Not Found
2:553  0:002  Using embedded font: Success
2:553  0:000  theme inited
2:553  0:000  Chosen embedded theme
2:553  0:000  after NVRAM boot-args=-v keepsyms=1 usb=0x800 -serial=0x1 size=36
2:553  0:000  === [ Dump SMC keys from NVRAM ] ==========================
2:553  0:000  found AppleSMC protocol
2:595  0:041  Registered 21 SMC keys
2:600  0:004  === [ ScanLoader ] ========================================
2:600  0:000  - [01]: 'EFI'
2:647  0:046          AddLoaderEntry for Volume Name=EFI
2:647  0:000          skipped because entry is hidden
2:647  0:000  - [05]: 'Preboot'
2:662  0:015          AddLoaderEntry for Volume Name=Preboot
2:707  0:044      Check if volume Is Hibernated:
2:707  0:000      Check sleep image 'by signature':
2:707  0:000      using default sleep image name = \private\var\vm\sleepimage
2:707  0:000      sleepimage not found -> Not Found
2:707  0:000      hibernated: no - sign
2:709  0:001  - [06]: 'macOS'
3:164  0:454          AddLoaderEntry for Volume Name=macOS
3:253  0:089      Check if volume Is Hibernated:
3:253  0:000      Check sleep image 'by signature':
3:272  0:019      using default sleep image name = \private\var\vm\sleepimage
3:276  0:003      sleepimage not found -> Not Found
3:276  0:000      hibernated: no - sign
3:277  0:000  - [07]: 'macOS  Data'
3:335  0:057  - [08]: 'Recovery'
3:366  0:030          AddLoaderEntry for Volume Name=Recovery
3:379  0:013  - [09]: 'VM'
3:380  0:000  - [10]: 'EFI'
3:397  0:017          AddLoaderEntry for Volume Name=EFI
3:397  0:000          skipped because entry is hidden
3:397  0:000  - [11]: 'Mojave'
3:420  0:023  - [12]: 'Install macOS Mojave'
3:478  0:058          AddLoaderEntry for Volume Name=Install macOS Mojave

Note macOS Catalina is volume 6 with unique UUID 34AD9A994BF6064BB007F726C1B61458

 

Custom Entry for Catalina looks like below...

				<dict>
					<key>Disabled</key>
					<false/>
					<key>FullTitle</key>
					<string>macOS Catalina</string>
					<key>Hidden</key>
					<false/>
					<key>Ignore</key>
					<false/>
					<key>InjectKexts</key>
					<false/>
					<key>NoCaches</key>
					<false/>
					<key>Path</key>
					<string>\System\Library\CoreServices\boot.efi</string>
					<key>Type</key>
					<string>OSX</string>
					<key>Volume</key>
					<string>34AD9A994BF6064BB007F726C1B61458</string>
				</dict>

Clover boot log after config.plist is updated shows successful match for the custom entry...

1:861  0:000  Custom entry 1 FullTitle:"macOS Catalina" Path:"\System\Library\CoreServices\boot.efi" Type:1 Flags:0x0 matching Volume:"34AD9A994BF6064BB007F726C1B61458"
1:861  0:000      Checking volume "EFI" (PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x0,0x0,0x0)\HD(1,GPT,C23671C0-6A01-4BC5-9FD0-0766D800CD22,0x28,0x64000)) ... skipped
1:861  0:000      Checking volume "EFI" (PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x2,0x0,0x0)\HD(1,GPT,9CBCF5A7-27F5-4EB2-B696-66F80130A12F,0x28,0x64000)) ... skipped
1:861  0:000      Checking volume "Mojave" (PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x2,0x0,0x0)\HD(2,GPT,394DFB82-0792-4253-BE45-2F2F8656091A,0x64028,0x50BB9B8)) ... skipped
1:861  0:000      Checking volume "Install macOS Mojave" (PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x2,0x0,0x0)\HD(3,GPT,0CF7B7D3-A54C-4D5D-98AF-6F4B9996EF58,0x515F9E0,0x12605F8)) ... skipped
1:861  0:000      Checking volume "Preboot" (PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x0,0x0,0x0)\HD(2,GPT,8912DB49-EF98-4DF0-ABB3-C5A58A95D2FA,0x64028,0x639BFB0)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,CA5C06978F8F0D41BBBD4D499B33EDBC)) ... skipped
1:861  0:000      Checking volume "macOS" (PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x0,0x0,0x0)\HD(2,GPT,8912DB49-EF98-4DF0-ABB3-C5A58A95D2FA,0x64028,0x639BFB0)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,34AD9A994BF6064BB007F726C1B61458)) ... match!

 

 

and Clover GUI shows correct title "macOS Catalina"...1373277518_CustomEntries2.thumb.png.da16a1f1b9b64a27c89c04697b12a23c.png

Edited by fusion71au

Share this post


Link to post
Share on other sites
Quote

For High Sierra and newer installers, the boot path \System\Library\CoreServices\boot.efi causes this error to show in Clover's boot log "skipped standard macOS path because volume is 2nd stage Install Media" ...

Why this? What was the logic for this restriction?

I can just erase it and it will work as expected. Any thought?

Share this post


Link to post
Share on other sites
On 8/31/2019 at 2:08 PM, Slice said:

Why this? What was the logic for this restriction?

I can just erase it and it will work as expected. Any thought?

 

LOL, I'm not a developer so I was hoping you might know :rofl:....or maybe @apianti or @SoThOr?

 

According to source for loader.c, it seems it is checking for the presence of "\.IAPhysicalMedia" file to determine volume is 2nd stage Install Media...

      // NOTE: Sothor - We dont care about legacy OS type // Check if the volume should be of certain os type
      //if ((Custom->Type != 0) && (Volume->OSType != 0) && !OSTYPE_COMPARE(OSType, Volume->OSType)) {
      //  DBG("skipped because wrong type (%d != %d)\n", OSType, Volume->OSType);
      //  continue;
      //}
      //} else if ((Custom->Type != 0) && (Volume->OSType != 0) && !OSTYPE_COMPARE(OSType, Volume->OSType)) {
      //DBG("skipped because wrong type (%d != %d)\n", OSType, Volume->OSType);
      //continue;
    }
    // Check the volume is readable and the entry exists on the volume
    if (Volume->RootDir == NULL) {
      DBG("skipped because filesystem is not readable\n");
      continue;
    }
    if (StriCmp(CustomPath, MACOSX_LOADER_PATH) == 0 && FileExists(Volume->RootDir, L"\\.IAPhysicalMedia")) {
      DBG("skipped standard OSX path because volume is 2nd stage Install Media\n");
      continue;

The logic is incorrect (and the check unnecessary) for High Sierra and newer installers since these don't have boot path \.IABootFiles\boot.efi, despite having the \.IAPhysicalMedia file on the root.

 

I vote to erase the check altogether.  Even when both boot paths are present (eg \.IABootFiles\boot.efi and \System\Library\CoreServices\boot.efi for Sierra Installer), selecting either path works to boot the installer.

 

23 hours ago, Slice said:

I also think the check is redundant. Committed.

 

@D-an-W, @Slice,

 

Custom entry for macOS createinstallmedia installer now working for Clover r5059+.  Tested Mojave, Mavericks and Snow Leopard installers ---> all OK & without duplicate entries :)

0:100  0:000  Starting Clover revision: 5059 on VMware, Inc. EFI
0:100  0:000  Build with: [Args: -D NO_GRUB_DRIVERS_EMBEDDED -D USE_APPLE_HFSPLUS_DRIVER -t GCC53 | -D NO_GRUB_DRIVERS_EMBEDDED -D USE_APPLE_HFSPLUS_DRIVER -D USE_LOW_EBDA -D HAVE_LEGACY_EMURUNTIMEDXE -a X64 -b RELEASE -t GCC53 -n 5 | OS: 10.14.6]
1:670  0:004  === [ AddCustomEntries ] ==================================
1:670  0:000  Custom entry 0 Title:"Install macOS" FullTitle:"Mojave Installer" Path:"\System\Library\CoreServices\boot.efi" Type:11 Flags:0x6 matching Volume:"0CF7B7D3-A54C-4D5D-98AF-6F4B9996EF58"
1:670  0:000      Checking volume "EFI" (PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x0,0x0,0x0)\HD(1,GPT,C23671C0-6A01-4BC5-9FD0-0766D800CD22,0x28,0x64000)) ... skipped
1:670  0:000      Checking volume "EFI" (PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x2,0x0,0x0)\HD(1,GPT,9CBCF5A7-27F5-4EB2-B696-66F80130A12F,0x28,0x64000)) ... skipped
1:670  0:000      Checking volume "Mojave" (PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x2,0x0,0x0)\HD(2,GPT,394DFB82-0792-4253-BE45-2F2F8656091A,0x64028,0x50BB9B8)) ... skipped
1:670  0:000      Checking volume "Install macOS Mojave" (PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x2,0x0,0x0)\HD(3,GPT,0CF7B7D3-A54C-4D5D-98AF-6F4B9996EF58,0x515F9E0,0x12605F8)) ... match!
1:703  0:032  Custom settings: <null string>.plist will  be applied
Spoiler

479897088_CustomentryforInstallerCloverr5059.thumb.png.33664217c522f58c6e24209cc5c4b784.pngscreenshot0.thumb.png.b70cfb9341d00dbd3c8e8807ca59079f.pngscreenshot1.thumb.png.741a45634986c71ffb954d28ba2e3a96.png

CLOVERX64_r5059.zip

Edited by fusion71au
Custom entry for macOS createinstallmedia installer now working for Clover r5059+

Share this post


Link to post
Share on other sites
15 hours ago, fusion71au said:

LOL, I'm not a developer so I was hoping you might know :rofl:....or maybe @apianti or @SoThOr?

Haha yeah, well I don't know either. It looks like it was me who added that code but being that was 6 years ago I don't remember why exactly that check needed. I haven't really been involved with Clover for a long time now. Likely the reasoning existed on the ProjectOSX forums. 

 

From my commit message r2228 "Avoid custom entry duplication for 10.9 install media" my guess is there was some duplication of entries during installation of Mavericks (and above?) where multiple boot.efi exist. 

 

I may have followed the logic from loader.c#983 from r2226 and mimicked that logic for the custom entry also. 

    // Use standard location for boot.efi, unless the file /.IAPhysicalMedia is present
    // That file indentifies a 2nd-stage Install Media, so when present, skip standard path to avoid entry duplication
    if (!FileExists(Volume->RootDir, L"\\.IAPhysicalMedia")) {
      if(EFI_ERROR(GetRootUUID(Volume)) || isFirstRootUUID(Volume)) {
        AddLoaderEntry(MACOSX_LOADER_PATH, NULL, L"Mac OS X", Volume, NULL, OSTYPE_OSX, 0);
      }
    }

Maybe there is a better way to determine if \System\Library\CoreServices\boot.efi is from second stage install? I'm quite out of touch with Hackintosh that I wouldn't really know where to start. Maybe check for \.IABootFiles\boot.efi rather than \.IAPhysicalMedia? That would probably make more sense. Does that code above also need to be updated?

Share this post


Link to post
Share on other sites

Hi @Slice

 

I've this issue when I try to compile r5061:

 

[CC] Lib
[CC] HdaCodec
[CC] BootFixes3
[CC] BootArgs
[CC] AutoGen
/Users/mathieu/src/UDK2018/Clover/rEFIt_UEFI/refit/main.c:2651:26: error: initializing 'EFI_KEY_DATA' with an expression of incompatible type 'int'
            EFI_KEY_DATA KeyData = 0;
                         ^         ~
[CC] AutoGen
1 error generated.
make: *** [/Users/mathieu/src/UDK2018/Build/Clover/RELEASE_XCODE8/X64/Clover/rEFIt_UEFI/refit/OUTPUT/refit/main.obj] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/mathieu/src/UDK2018/Build/Clover/RELEASE_XCODE8/X64/Clover/rEFIt_UEFI/refit]


build.py...
 : error F002: Failed to build module
	/Users/mathieu/src/UDK2018/Clover/rEFIt_UEFI/refit.inf [X64, XCODE8, RELEASE]

- Failed -
Build end time: 11:42:57, Sep.03 2019
Build total time: 00:00:49

 

Share this post


Link to post
Share on other sites
44 minutes ago, Slice said:

See screenshot here

 

 

Great job :) button Reset = restart, Space + button Reset = Clear CMOS, right?

Edited by Matgen84

Share this post


Link to post
Share on other sites
6 hours ago, Matgen84 said:

 

Great job :) button Reset = restart, Space + button Reset = Clear CMOS, right?

On my case with AMI Aptio UEFI 2.0 (Asus), I set BIOS / firmware Password (Admin + User). Then booting Clover r5064, press SpaceBar with Clicking Left Mouse on "Restart" function (CMIIW). Once mach reboot, my Startup key gives prev. boot entries, but BIOS still asks for Password. Weird is on BIOS - Boot: I lost all my boot entries hah haa..

Edited by Badruzeus

Share this post


Link to post
Share on other sites

When Start-Up my rig it is waiting 17 sec on the splash screen is that normal? I reset my BIOS with 2 pin header and also removed CMOS battery but nothing change. Does anyone know why this happening? 

Share this post


Link to post
Share on other sites
1 hour ago, Badruzeus said:

On my case with AMI Aptio UEFI 2.0 (Asus), I set BIOS / firmware Password (Admin + User). Then booting Clover r5064, press SpaceBar with Clicking Left Mouse on "Restart" function (CMIIW). Once mach reboot, my Startup key gives prev. boot entries, but BIOS still asks for Password. Weird is on BIOS - Boot: I lost all my boot entries hah haa..

 

Reset CMOS, you means lost boot order entries in BIOS... Logical, ha, ha, ha. I don't understand why this new function exists in Clover and his utility?

Share this post


Link to post
Share on other sites
11 minutes ago, Matgen84 said:

 

Reset CMOS, you means lost boot order entries in BIOS... Logical, ha, ha, ha. I don't understand why this new function exists in Clover and his utility?

No, Boot entries should remain here. But different BIOSes may behave differently.

Share this post


Link to post
Share on other sites
16 minutes ago, Slice said:

No, Boot entries should remain here. But different BIOSes may behave differently.

 

I talk about boot order in BIOS for my two rigs. As you said:  "different BIOSes may behave differently"

 

Can you tell me the utility of this function in Clover, because I don't understand. I've always reset BIOS setting in hardware way or by loading default optimized values, directly.

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

  • Similar Content

    • By ErmaC
      Slice is glad to present a new EFI bootloader.

      CLOVER
      Now version 2 rEFIt based.


      It is open source based on different projects: Chameleon, rEFIt, XNU, VirtualBox. The main is EDK2 latest revision.
      I also want to thank all who help Slice with the development. Credits and copyrights remain in the sources.
      https://sourceforge.net/projects/cloverefiboot/?source=directory
      There is a WIKI 
      http://clover-wiki.zetam.org/
      Main features:


      If you have a question please provide outputs from DarwinDumper (formed from Trauma tool). Thanks Trauma!
      Continued by blackosx and STLVNUB.
      Post#2 CloverGrower - create Clover by yourself Post#3 Downloads Post#4 Installation of the bootloader Post#5 How to do UEFI boot Post#6 How to use - common words Post#7 Calculator for Automatic DSDT fix Post#8 Instructions for GraphicsInjector Post#9 ATIConnector patching Post#10 Any kexts patching with some Samples Post#11 CustomEDID Post#12 Hiding unnecessary menu entries Post#13 Instruction for DSDT corrections to do DeviceInjection works Post#14 Development Post#15 Themes Post#16 About kexts injection Post#17 Instructions for P- and C-states generator Post#18 Patching DSDT to get Sleep working Post#19 CPU settings and geekbench Post#20 ACPI tables loading Post#21 DSDTmini Post#22 Custom SMBios Post#23 F.A.Q. Post#24 iCloudFix Post#25 Using mouse. Post#26 How to make orange icons to be metallic Post#27 How to make software RAID (by Magnifico) Post#28 How to modify InstallESD.dmg (by shiecldk) Post#29 Config.plist settings Post#30 Using extra kexts and skipping kernelcache Post#31 Choosing EFI drivers Post#32 Configuration files Post#33 Automatic config.plist creating Post#34 Custom DSDT patches Post#35 How to do sleep/wake working with UEFI BOOT Post#36 DeviceID substitution (FakeID) Post#37 Using Custom OS Icons Post#38 Hibernation Post#39 Floating regions Post#41 Property List Editor Post#42 Blocking Bad Kext Post#43 AAPL,slot-name Post#44 FakeCPUID for unsupported CPU Post#45 Multiple Boot Options - to write into UEFI BIOS boot menu Post#46 How to install Windows UEFI Post#47 How to speedup Clover boot Post#48 Info.plist patching Post#49 Arbitrary device injection Post#50 Non-Standard Legacy Boot Files Post#51 Reboot to Windows UEFI from Mac OSX Post#52 Deprecated Features Post#53 Using UDK2018 Post#54 Device Properties Post#55 Scalable themes Post#56 How to search Clover mistakes (bisection) -----------------
       
      Slice:
      I edited all posts in the thread to correspond to actual Clover revision.
      Please install Clover at least 2652 and use new instructions.
×