Clover General discussion

Andres ZeroCross · August 14, 2019

5 minutes ago, vector sigma said:

try, but looks like you have a damaged filesystem

Yes, maybe you're right. No problem, Catalina is beta. I always reinstall Catalina for every update. The problem is, i want to know the source of issue

vector sigma · August 14, 2019

1 minute ago, Andres ZeroCross said:

No problem, Catalina is beta. I always reinstall Catalina for every update. The problem is, i want to know the source of issue

A kernel panic or any other unsafe shut down or a sudden power off can do that easily.

Andres ZeroCross · August 14, 2019

22 minutes ago, vector sigma said:

A kernel panic or any other unsafe shut down or a sudden power off can do that easily.

Owh yes,,, i have several accidentally shutdown. Electrical Company problem in my Country.
Thanks for the input,,, waiting for new Catalina for Fresh Install. Sorry for bad english

MICKHAEL · August 14, 2019

Owh yes,,, i have several accidentally shutdown. Electrical Company problem in my Country.
Thanks for the input,,, waiting for new Catalina for Fresh Install. Sorry for bad english

I will advise you to buy a good UPS for that

Trimis de pe al meu Pixel folosind Tapatalk

Andres ZeroCross · August 14, 2019

47 minutes ago, MICKHAEL said:

I will advise you to buy a good UPS for that

Trimis de pe al meu Pixel folosind Tapatalk

I have an UPS but with Bad Battery. Still waiting for new battery arrive (I am ordering new ones),, Thanks you

Edited August 14, 2019 by Andres ZeroCross

MICKHAEL · August 14, 2019

I have an UPS but with Bad Battery. Still waiting for new battery arrive (I am ordering new ones),, Thanks you

Haha what a coincidence))

Trimis de pe al meu Pixel folosind Tapatalk

Andres ZeroCross · August 15, 2019

my problem is fixed

1. Just download latest Catalina Beta from Appstore
2. Run Install macOS Catalina Beta from macOS Catalina Beta itself
3. Finish Installing
4. No lost data, no lost installed app
5. Instal Clover with 100% success

Matgen84 · August 15, 2019

Hi Guys

Clover Installer (r5050) stocks at first stage on Catalina Beta 5. I don't understand why?

EDIT: Works if I use Chris's Tool to make Volume read-writable

Historique de Programme d’installation 15-Aug-2019.txt.zip

Edited August 15, 2019 by Matgen84

vector sigma · August 15, 2019

3 hours ago, Matgen84 said:

Hi Guys

Clover Installer (r5050) stocks at first stage on Catalina Beta 5. I don't understand why?

EDIT: Works if I use Chris's Tool to make Volume read-writable

Historique de Programme d’installation 15-Aug-2019.txt.zip

PackageKit: Bypassing the enforcement checker since the destination is read/write

The file system was already rw. Problem is elsewere.. also probably a problem of timing.

Edited August 15, 2019 by vector sigma

Matgen84 · August 16, 2019

11 hours ago, vector sigma said:
PackageKit: Bypassing the enforcement checker since the destination is read/write
The file system was already rw. Problem is elsewere.. also probably a problem of timing.

Thanks. Which solution.

Badruzeus · August 16, 2019

1 hour ago, Matgen84 said:

Thanks. Which solution.

I remember we've discussed about this before;

Installer.app is being used by another process: Software Update. It prevents us for proceeding with another installation; not only with Clover but another installers as well.. especially when we have internet connection active. I guess, just Force Quit it via Activity Monitor.app before installing Clover from package. Seems, macOS 10.15 Beta issue (nor Clover or other installers).

Edited August 16, 2019 by Badruzeus

vector sigma · August 16, 2019

4 hours ago, Matgen84 said:

Thanks. Which solution.

3 hours ago, Badruzeus said:

I remember we've discussed about this before;

Installer.app is being used by another process: Software Update. It prevents us for proceeding with another installation; not only with Clover but another installers as well.. especially when we have internet connection active. I guess, just Force Quit it via Activity Monitor.app before installing Clover from package. Seems, macOS 10.15 Beta issue (nor Clover or other installers).

So the solution is to turn off updates, at least temporarily?

telepati · August 21, 2019

What is this new feature, how to use this;

r5051

Add support for key names PrimaryGPU/SecondaryGPU in Devices/Properties - it can be useful for injecting specific properties to GPU where the monitor is or is not connected to, especially in cases where the monitor is not always connected to the same GPU when booting (for example, it can be used for disabling inactive GPU when OSX boots).

Pene · August 21, 2019

2 hours ago, telepati said:

What is this new feature, how to use this;

r5051

Add support for key names PrimaryGPU/SecondaryGPU in Devices/Properties - it can be useful for injecting specific properties to GPU where the monitor is or is not connected to, especially in cases where the monitor is not always connected to the same GPU when booting (for example, it can be used for disabling inactive GPU when OSX boots).

It is for more complex cases, mostly for cases where you have two GPUs in the system (both are enabled from BIOS), but monitor is connected only to one, and you wish to be able to control the settings for OSX according to which GPU the monitor is connected when system boots up.

It is not needed for simpler cases where only one GPU is being used.

It can help in some other cases too, but here is a use case, where it is really needed:

- You have an Intel GPU and also a discrete GPU, but the discrete GPU is not supported by OSX (for example, all latest Nvidia cards).

- You want to use Nvidia GPU when you boot Windows, but usually Intel GPU when you boot OSX. And maybe you want to boot OSX sometimes also with the NVidia card, when monitor is connected to it.

- You have a DP or HDMI switch connected to the monitor, and can switch the monitor between the Intel and the Nvidia card. Or alternatively, you have two inputs on your monitor, and connect each monitor input to a different GPU, and select it from the monitor before powering up the system.

(Note: such configuration is usually supported with the following UEFI BIOS settings: CSM=Disabled, Primary Graphics Adapter=Onboard, IGPU-Multi-Monitor=Enabled, which results, on most UEFI BIOSes, in POST being displayed to where the monitor is connected).

In the above case, it would be useful for Clover to detect which card is active when you boot (meaning, to which card the monitor is connected), so that you can disable the inactive GPU when OSX boots, in order to avoid problems regarding Multi-GPU setup within OSX (and use OSX, instead, as having a single GPU, regardless of which GPU you are booting with).

- To do this, in the above case, you can now set properties for secondary (inactive) gpu in config.plist (at Devices/Properties/SecondaryGPU). An example property for to inject for the secondary device could be a device-id=0xffff, which will result in disabling the inactive GPU (and it will always disable the card that is not used when booting up, whether it is Intel or Discrete).

- Note, that it this case, it can be also useful to set in config.plist GUI/ShowOptimus=true (this will result in showing at the bottom of Clover's GUI whether monitor is currently connected to Intel or to Discrete GPU).

- Properties can be set also for PrimaryGPU, if needed (at Devices/Properties/PrimaryGPU).

With the correct settings, you can achieve OSX booting properly also with Discrete GPU when monitor is connected to it (without acceleration, of course, for the example above of an unsupported card), and also with Intel GPU when monitor is connected to that one.

Edited August 21, 2019 by Pene

Badruzeus · August 23, 2019

Sorry @Slice, referring to this change since r5052.. I got issue with failed `kext_inject`.

FYi, I have only `10.14` and `Other` dirs on \EFI\CLOVER\kexts\ (all are back to fine after rolling back to r5051).

Here's preboot.log. Thanks.

13:073  0:000  Beginning FSInjection
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 2167098
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 2167098
13:074  0:000  Use origin smbios table type 1 guid.
13:075  0:001  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
13:075  0:000  Extra kext: <null string>\WhateverGreen.kext (v.1.3.2)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\WhateverGreen.kext
13:075  0:000  Extra kext: <null string>\SystemProfilerMemoryFixup.kext (v.1.0.0)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\SystemProfilerMemoryFixup.kext
13:075  0:000  Extra kext: <null string>\RTCMemoryFixup.kext (v.1.0.4)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\RTCMemoryFixup.kext
13:075  0:000  Extra kext: <null string>\RealtekRTL8111.kext (v.2.2.2)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\RealtekRTL8111.kext
13:075  0:000  Extra kext: <null string>\NoTouchID.kext (v.1.0.2)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\NoTouchID.kext
13:075  0:000  Extra kext: <null string>\Lilu.kext (v.1.3.8)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\Lilu.kext
13:075  0:000  Extra kext: <null string>\IOath3kfrmwr.kext (v.1.2.1)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\IOath3kfrmwr.kext
13:075  0:000  Extra kext: <null string>\FakeSMC.kext (v.1802)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\FakeSMC.kext
13:075  0:000  Extra kext: <null string>\EFICheckDisabler.kext (v.0.5)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\EFICheckDisabler.kext
13:075  0:000  Extra kext: <null string>\CalDigitUSBxHCI.kext (v.1.3.8a2)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\CalDigitUSBxHCI.kext
13:075  0:000  Extra kext: <null string>\CalDigitFastIO.kext (v.2.6.1)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\CalDigitFastIO.kext
13:075  0:000  Extra kext: <null string>\AsusFnKeys.kext (v.1.0.6)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\AsusFnKeys.kext
13:075  0:000  Extra kext: <null string>\AsusACPIBackLightPanel.kext (v.1.7)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\AsusACPIBackLightPanel.kext
13:075  0:000  Extra kext: <null string>\ApplePS2SmartTouchPad.kext (v.4.6.8)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\ApplePS2SmartTouchPad.kext
13:075  0:000    |-- PlugIn kext: <null string>\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Keyboard.kext (v.4.6.8)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Keyboard.kext
13:075  0:000    |-- PlugIn kext: <null string>\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Controller.kext (v.4.6.8)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Controller.kext
13:075  0:000  Extra kext: <null string>\AppleALC.kext (v.1.4.1)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\AppleALC.kext
13:075  0:000  Extra kext: <null string>\ACPIBatteryManager.kext (v.1.90.1)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\ACPIBatteryManager.kext

preboot_a43sj_r5052.log.zip

Slice · August 23, 2019

1 hour ago, Badruzeus said:

Sorry @Slice, referring to this change since r5052.. I got issue with failed `kext_inject`.

FYi, I have only `10.14` and `Other` dirs on \EFI\CLOVER\kexts\ (all are back to fine after rolling back to r5051).

Here's preboot.log. Thanks.


13:073  0:000  Beginning FSInjection
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 2167098
FSInjectionInstall ...
- Our FSI_SIMPLE_FILE_SYSTEM_PROTOCOL installed on handle: 2167098
13:074  0:000  Use origin smbios table type 1 guid.
13:075  0:001  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
13:075  0:000  Extra kext: <null string>\WhateverGreen.kext (v.1.3.2)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\WhateverGreen.kext
13:075  0:000  Extra kext: <null string>\SystemProfilerMemoryFixup.kext (v.1.0.0)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\SystemProfilerMemoryFixup.kext
13:075  0:000  Extra kext: <null string>\RTCMemoryFixup.kext (v.1.0.4)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\RTCMemoryFixup.kext
13:075  0:000  Extra kext: <null string>\RealtekRTL8111.kext (v.2.2.2)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\RealtekRTL8111.kext
13:075  0:000  Extra kext: <null string>\NoTouchID.kext (v.1.0.2)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\NoTouchID.kext
13:075  0:000  Extra kext: <null string>\Lilu.kext (v.1.3.8)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\Lilu.kext
13:075  0:000  Extra kext: <null string>\IOath3kfrmwr.kext (v.1.2.1)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\IOath3kfrmwr.kext
13:075  0:000  Extra kext: <null string>\FakeSMC.kext (v.1802)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\FakeSMC.kext
13:075  0:000  Extra kext: <null string>\EFICheckDisabler.kext (v.0.5)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\EFICheckDisabler.kext
13:075  0:000  Extra kext: <null string>\CalDigitUSBxHCI.kext (v.1.3.8a2)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\CalDigitUSBxHCI.kext
13:075  0:000  Extra kext: <null string>\CalDigitFastIO.kext (v.2.6.1)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\CalDigitFastIO.kext
13:075  0:000  Extra kext: <null string>\AsusFnKeys.kext (v.1.0.6)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\AsusFnKeys.kext
13:075  0:000  Extra kext: <null string>\AsusACPIBackLightPanel.kext (v.1.7)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\AsusACPIBackLightPanel.kext
13:075  0:000  Extra kext: <null string>\ApplePS2SmartTouchPad.kext (v.4.6.8)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\ApplePS2SmartTouchPad.kext
13:075  0:000    |-- PlugIn kext: <null string>\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Keyboard.kext (v.4.6.8)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Keyboard.kext
13:075  0:000    |-- PlugIn kext: <null string>\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Controller.kext (v.4.6.8)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Controller.kext
13:075  0:000  Extra kext: <null string>\AppleALC.kext (v.1.4.1)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\AppleALC.kext
13:075  0:000  Extra kext: <null string>\ACPIBatteryManager.kext (v.1.90.1)
13:075  0:000  Failed to load extra kext (Info.plist not found): <null string>\ACPIBatteryManager.kext

preboot_a43sj_r5052.log.zip

Thanks for test, see 5053.

Badruzeus · August 23, 2019

2 hours ago, Slice said:

Thanks for test, see 5053.

Many thanks, guessing it worked since r5053.

Though sometimes, which kexts (plus their versions) are not printed on bottom of preboot.log (on this case, I usually need to reboot), but as long as kexts are loaded / injected; it doesn't matter (`kextstat | grep -v com.apple` still helps).

preboot_a43sj_r5055.zip

Edited August 23, 2019 by Badruzeus

Slice · August 23, 2019

6 hours ago, Badruzeus said:

Many thanks, guessing it worked since r5053.

Though sometimes, which kexts (plus their versions) are not printed on bottom of preboot.log (on this case, I usually need to reboot), but as long as kexts are loaded / injected; it doesn't matter (`kextstat | grep -v com.apple` still helps).

preboot_a43sj_r5055.zip

Because kext_inject.c compiled without messages

#define KEXT_INJECT_DEBUG 0

change to 2 to see the list in preboot.log

I will think how many other messages should be excluded.

MorenoAv · August 25, 2019

Hi guys, good morning,

Today was the day after switching from clover v2.4K 4972 to v2.5 5050 that I tried to boot all my OS, all in separate ssd's Mojave booted just fine because don't have clover installed, but windows 10 booted normally but after the boot loader disappears an I have to use my usb installation... how do I solve this?

Thanks in Advance

PS: Solved ...

Edited August 25, 2019 by MorenoAv

pkdesign · August 26, 2019

I'm sure I am doing something wrong but...my custom entries are not showing up how I excepted them to.

With my config (attached) shouldn’t the entries be listed "Mojave" on the left (first) and "Windows Pro 10" on the right?

Also, as you can see from screen shot, the full title I manually entered is not showing up. It still shows "SYSTEM" and "macOS," not "Mojave" and "Windows 10 Pro."

config.plist

Matgen84 · August 26, 2019

59 minutes ago, pkdesign said:

I'm sure I am doing something wrong but...my custom entries are not showing up how I excepted them to.

With my config (attached) shouldn’t the entries be listed "Mojave" on the left (first) and "Windows Pro 10" on the right?

Also, as you can see from screen shot, the full title I manually entered is not showing up. It still shows "SYSTEM" and "macOS," not "Mojave" and "Windows 10 Pro."

config.plist

Can you try this:

Put Mojave in Last Volume

Sorry for my bad english

Edited August 26, 2019 by Matgen84

pkdesign · August 26, 2019

5 hours ago, Matgen84 said:

Can you try this:

Put Mojave in Last Volume

Sorry for my bad english

That did absolutely nothing. Boot screen still looks the same.

The issue is not that it doesn’t pick the correct volume, it is that they do not have the labels set in the config.

tluck · August 26, 2019

6 hours ago, pkdesign said:

I'm sure I am doing something wrong but...my custom entries are not showing up how I excepted them to.

With my config (attached) shouldn’t the entries be listed "Mojave" on the left (first) and "Windows Pro 10" on the right?

Also, as you can see from screen shot, the full title I manually entered is not showing up. It still shows "SYSTEM" and "macOS," not "Mojave" and "Windows 10 Pro."

config.plist

here is what i did for a Custom entry for macOS and Windows on a single disk with this layout:

$ diskutil list

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *512.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         459.7 GB   disk0s2
   3:       Apple_KernelCoreDump                         655.4 MB   disk0s3
   4:       Microsoft Basic Data W10                     50.6 GB    disk0s4
   5:           Windows Recovery                         995.1 MB   disk0s5

my Window bootmgr is the Microsoft folder but in the ESP/EFI (vs SYSTEM) along side CLOVER

$ cat /Library/Logs/CloverEFI/boot.log |grep Custom
0:120  0:000  Custom boot CUSTOM_BOOT_DISABLED (0x0)
6:657  0:001  === [ AddCustomEntries ] ==================================
6:657  0:000  Custom entry 0 FullTitle:"macOS" Path:"\System\Library\CoreServices\boot.efi" Type:1 Flags:0x6 matching Volume:"CE105F19-A28D-4A84-83D5-CDF4D547E35A"
6:709  0:000  Custom entry 1 FullTitle:"Windows 10" Path:"\EFI\Microsoft\Boot\bootmgfw.efi" Options:"-s -h" Type:7 Flags:0x0 matching Volume:"2A125BB9-B377-4701-9244-FBA3EADB8B4D"

Then looking at the clover logs i can see what GUIDs to use:

refer to the GUID for HD(1, and HD(2

HD(1 is the EFI which seems wrong but that where MS bootmgfw thing is

$ cat /Library/Logs/CloverEFI/boot.log |grep Volume
6:370  0:064  === [ ScanVolumes ] =======================================
6:370  0:000  - [00]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)
6:371  0:000  - [01]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)
6:371  0:000  - [02]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,2A125BB9-B377-4701-9244-FBA3EADB8B4D,0x28,0x64000)
6:379  0:007          This is SelfVolume !!
6:379  0:000  - [03]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,CE105F19-A28D-4A84-83D5-CDF4D547E35A,0x64028,0x35840BD8)
6:379  0:000  - [04]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(3,GPT,4539F38D-62B6-46EF-A59F-E0D35A1366D2,0x358A4C00,0x138800)
6:380  0:000  - [05]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(4,GPT,882E2BDA-CBF5-4C17-8404-35EC11AB98BA,0x359DD400,0x5E284CA)
6:381  0:000  - [06]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(5,GPT,D9951696-A967-46D5-AE22-B9CD84B2AEF0,0x3B806000,0x1DA800)

which look like this in config.plist

		<key>Custom</key>
		<dict>
			<key>Comment</key>
			<string>Windows Entries</string>
			<key>Entries</key>
			<array>
				<dict>
					<key>FullTitle</key>
					<string>macOS</string>
					<key>Type</key>
					<string>macOS</string>
					<key>Volume</key>
					<string>CE105F19-A28D-4A84-83D5-CDF4D547E35A</string>
				</dict>
				<dict>
					<key>FullTitle</key>
					<string>Windows 10</string>
					<key>Type</key>
					<string>Windows</string>
					<key>Volume</key>
					<string>2A125BB9-B377-4701-9244-FBA3EADB8B4D</string>
				</dict>
			</array>
		</dict>

Matgen84 · August 27, 2019

7 hours ago, tluck said:

here is what i did for a Custom entry for macOS and Windows on a single disk with this layout:


$ diskutil list

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *512.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         459.7 GB   disk0s2
   3:       Apple_KernelCoreDump                         655.4 MB   disk0s3
   4:       Microsoft Basic Data W10                     50.6 GB    disk0s4
   5:           Windows Recovery                         995.1 MB   disk0s5

my Window bootmgr is the Microsoft folder but in the ESP/EFI (vs SYSTEM) along side CLOVER


$ cat /Library/Logs/CloverEFI/boot.log |grep Custom
0:120  0:000  Custom boot CUSTOM_BOOT_DISABLED (0x0)
6:657  0:001  === [ AddCustomEntries ] ==================================
6:657  0:000  Custom entry 0 FullTitle:"macOS" Path:"\System\Library\CoreServices\boot.efi" Type:1 Flags:0x6 matching Volume:"CE105F19-A28D-4A84-83D5-CDF4D547E35A"
6:709  0:000  Custom entry 1 FullTitle:"Windows 10" Path:"\EFI\Microsoft\Boot\bootmgfw.efi" Options:"-s -h" Type:7 Flags:0x0 matching Volume:"2A125BB9-B377-4701-9244-FBA3EADB8B4D"

Then looking at the clover logs i can see what GUIDs to use:

refer to the GUID for HD(1, and HD(2

HD(1 is the EFI which seems wrong but that where MS bootmgfw thing is


$ cat /Library/Logs/CloverEFI/boot.log |grep Volume
6:370  0:064  === [ ScanVolumes ] =======================================
6:370  0:000  - [00]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)
6:371  0:000  - [01]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)
6:371  0:000  - [02]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,2A125BB9-B377-4701-9244-FBA3EADB8B4D,0x28,0x64000)
6:379  0:007          This is SelfVolume !!
6:379  0:000  - [03]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,CE105F19-A28D-4A84-83D5-CDF4D547E35A,0x64028,0x35840BD8)
6:379  0:000  - [04]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(3,GPT,4539F38D-62B6-46EF-A59F-E0D35A1366D2,0x358A4C00,0x138800)
6:380  0:000  - [05]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(4,GPT,882E2BDA-CBF5-4C17-8404-35EC11AB98BA,0x359DD400,0x5E284CA)
6:381  0:000  - [06]: Volume: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(5,GPT,D9951696-A967-46D5-AE22-B9CD84B2AEF0,0x3B806000,0x1DA800)

which look like this in config.plist


		<key>Custom</key>
		<dict>
			<key>Comment</key>
			<string>Windows Entries</string>
			<key>Entries</key>
			<array>
				<dict>
					<key>FullTitle</key>
					<string>macOS</string>
					<key>Type</key>
					<string>macOS</string>
					<key>Volume</key>
					<string>CE105F19-A28D-4A84-83D5-CDF4D547E35A</string>
				</dict>
				<dict>
					<key>FullTitle</key>
					<string>Windows 10</string>
					<key>Type</key>
					<string>Windows</string>
					<key>Volume</key>
					<string>2A125BB9-B377-4701-9244-FBA3EADB8B4D</string>
				</dict>
			</array>
		</dict>

Great explanations. Thanks.

I use two HDD (macOS Mojave and Windows 10). There isn't CloverEFI folder in /Library/Logs. I don't understand why?

D-an-W · August 27, 2019

Could someone please remind me which UUID I choose from a USB stick (With two installers on) to get it correctly detected in the Clover GUI?

Currently I get this but it should just say "Install macOS Catalina" (Same for Mojave installer)...

128765192_Screenshot2019-08-27at07_45_54.png.661edcd4b53107c889a9db1c1eb3b5de.png

Clover General discussion

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites