Clover General discussion

MagicNAS · August 28, 2019

7 hours ago, Slice said:

Disable CSM in BIOS.

Thanks!

pkdesign · August 28, 2019

On 8/26/2019 at 6:06 PM, 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>

I simplified my config based on tluck:

This still results in the same boot screen.

I think my point is being missed. The two options are exactly what I want. It always selects macOS as the default boot and only these two option appear. The problem is they don’t (cosmetically) appear the way I expect them to.

I assume that the "FullTitle" keys would make the boot options have that title. The macOS boot would show up as "Mojave" and the Windows boot would show up as "Windows 10 Pro" since that is what I have them labeled as in the config. Also that they would appear in the order I had them in (Mojave first, then Windows 10 Pro.)

Am I mistaken? This is purely cosmetic as both option boot just fine.

D-an-W · August 28, 2019

I have a similar problem with the OSXInstaller entries I have that are both situated on the same USB stick, I can't get the custom names to show up (They did used to work ok).

I wonder if our issues are related?

pkdesign · August 28, 2019

1 hour ago, D-an-W said:

I have a similar problem with the OSXInstaller entries I have that are both situated on the same USB stick, I can't get the custom names to show up (They did used to work ok).

I wonder if our issues are related?

It would seem so. This seems to be a simple issue. The custom title doesn't show up correctly andin the right order.

Slice · August 29, 2019

Each custom entry must contain correct Path.

Badruzeus · August 29, 2019

About "Moving Clover Project" repo to GitHub may be a POLL is needed @Slice..?

pkdesign · August 29, 2019

13 hours ago, Slice said:

Each custom entry must contain correct Path.

I did have the custom paths in originally (see config file in original post and screenshot below)

It still did not show up as I expected.

BTW, it boots just fine with paths and show the options as in my above capture. It just doesn't show customized titles.

Edited August 29, 2019 by pkdesign

Badruzeus · August 29, 2019

31 minutes ago, pkdesign said:

I did have the custom paths in originally (see config file in original post and screenshot below)

It still did not show up as I expected.

BTW, it boots just fine with paths and show the options as in my above capture. It just doesn't show customized titles.

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.

Edited August 29, 2019 by Badruzeus

D-an-W · August 29, 2019

Does anyone know where Catalina and Mojave hides the boot.efi on the installers created by "createinstallmedia" so I can try using that in the path of the custom entry?

fusion71au · August 30, 2019

On 8/30/2019 at 7:25 AM, D-an-W said:

Does anyone know where Catalina and Mojave hides the boot.efi on the installers created by "createinstallmedia" so I can try using that in the path of the custom entry?

Path for High Sierra, Mojave and Catalina installers is \System\Library\CoreServices\boot.efi eg after preparing Catalina installer with createinstallmedia, you will see the following in Finder...

Spoiler

715382809_HighSierraInstaller.png.54d1e451307d6673ba7327f76dc54407.png

To show hidden files, press <Command ⌘ ><Shift><.> on Apple Keyboard or <Windows ⊞><Shift><.> on Standard US Keyboard.

Note: There are additional, different paths to boot.efi for Sierra and older installers eg

\.IABootFiles\boot.efi

Spoiler

1008182755_SierraInstaller.png.d1c974af6feb455c985d8152d2953f64.png

On 8/29/2019 at 2:50 AM, D-an-W said:

I have a similar problem with the OSXInstaller entries I have that are both situated on the same USB stick, I can't get the custom names to show up (They did used to work ok).

I wonder if our issues are related?

Yes, it looks like a bug in Clover.

The custom entries for macOS installer worked for Sierra & before when the boot path was .\IABootFiles\boot.efi.

<key>GUI</key>
<dict>
		<key>Custom</key>
		<dict>
			<key>Entries</key>
			<array>
				<dict>
					<key>Disabled</key>
					<false/>
					<key>FullTitle</key>
					<string>Sierra Installer</string>
					<key>Hidden</key>
					<false/>
					<key>Ignore</key>
					<false/>
					<key>InjectKexts</key>
					<string>Detect</string>
					<key>NoCaches</key>
					<false/>
					<key>Path</key>
					<string>\.IABootFiles\boot.efi</string>
					<key>Type</key>
					<string>OSXInstaller</string>
					<key>Volume</key>
					<string>0CF7B7D3-A54C-4D5D-98AF-6F4B9996EF58</string>
				</dict>

Corresponding Clover boot log shows successful match ...

1:921  0:004  === [ AddCustomEntries ] ==================================
1:921  0:000  Custom entry 0 Title:"Install macOS" FullTitle:"Sierra Installer" Path:"\.IABootFiles\boot.efi" Type:11 Flags:0x6 matching Volume:"0CF7B7D3-A54C-4D5D-98AF-6F4B9996EF58"
1:921  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:921  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:921  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:921  0:000      Checking volume "Install macOS Sierra" (PciRoot(0x0)\Pci(0x11,0x0)\Pci(0x4,0x0)\Sata(0x2,0x0,0x0)\HD(3,GPT,0CF7B7D3-A54C-4D5D-98AF-6F4B9996EF58,0x515F9E0,0x12605F8)) ... match!
1:945  0:023  Custom settings: <null string>.plist will  be applied

and Clover GUI shows correct Title "Sierra Installer"

Spoiler

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" ...

1:924  0:004  === [ AddCustomEntries ] ==================================
1:924  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:924  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:924  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:924  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:924  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 standard macOS path because volume is 2nd stage Install Media

So only the autoscan entry "Boot macOS Install from Install macOS xxxxx" shows...

Spoiler

A workaround is to manually create the hidden .IABootFiles folder containing boot.efi, com.apple.Boot.plist, PlatformSupport.plist and the prelinkedkernel, and .IABootFilesSystemVersion.plist to the root of the High Sierra/Mojave/Catalina Installer (these files can be found in /Library/Preferences/SystemConfiguration and /System/Library/CoreServices + /System/Library/PrelinkedKernels). Then you can change the path in your custom installer entry to \.IABootFiles\boot.efi...

693687315_AddIABootFilestoMojaveInstaller.png.3e7b9a2dca29749d307824675904044d.png

	<key>GUI</key>
	<dict>
		<key>Custom</key>
		<dict>
			<key>Entries</key>
			<array>
				<dict>
					<key>Disabled</key>
					<false/>
					<key>FullTitle</key>
					<string>Mojave Installer</string>
					<key>Hidden</key>
					<false/>
					<key>Ignore</key>
					<false/>
					<key>InjectKexts</key>
					<string>Detect</string>
					<key>NoCaches</key>
					<false/>
					<key>Path</key>
					<string>\.IABootFiles\boot.efi</string>
					<key>Type</key>
					<string>OSXInstaller</string>
					<key>Volume</key>
					<string>0CF7B7D3-A54C-4D5D-98AF-6F4B9996EF58</string>
				</dict>

Clover boot log now shows correct match for the custom installer entry...

1:838  0:003  === [ AddCustomEntries ] ==================================
1:838  0:000  Custom entry 0 Title:"Install macOS" FullTitle:"Mojave Installer" Path:"\.IABootFiles\boot.efi" Type:11 Flags:0x6 matching Volume:"0CF7B7D3-A54C-4D5D-98AF-6F4B9996EF58"
1:838  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:838  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:838  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:838  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:861  0:022  Custom settings: <null string>.plist will  be applied

End result...Correct title "Mojave Installer"...

Edited August 31, 2019 by fusion71au
Additional info: .IABootFiles path in Sierra and older

August 30, 2019

I'm not sure if the issue is Clover, but I guess I have the biggest chance to get an answer here :lol:

Situation:

Clover UEFI is set as first boot option in my UEFI bios. So when I boot up the system, it boots up into Clover. No issues there.

The issue:

When rebooting from macOS the system reboots normal but then hangs a couple of secs on POST. Eventually it'll continue the booting process but on the point where Clover should load up the system just freezes, like if it can't find Clover. This happens 9/10 times. 1/10 times it reboots into Clover just fine.

This only happens while rebooting from macOS. Rebooting from any other OS (booted from Clover) works just fine.
Also rebooting from Clover itself works without issues, so the issue really is limited to a fully booted macOS.

Any ideas?

Matgen84 · August 30, 2019

4 minutes ago, ricoc90 said:

I'm not sure if the issue is Clover, but I guess I have the biggest chance to get an answer here

Situation:

Clover UEFI is set as first boot option in my UEFI bios. So when I boot up the system, it boots up into Clover. No issues there.

The issue:

When rebooting from macOS the system reboots normal but then hangs a couple of secs on POST. Eventually it'll continue the booting process but on the point where Clover should load up the system just freezes, like if it can't find Clover. This happens 9/10 times. 1/10 times it reboots into Clover just fine.

This only happens while rebooting from macOS. Rebooting from any other OS (booted from Clover) works just fine.
Also rebooting from Clover itself works without issues, so the issue really is limited to a fully booted macOS.

Any ideas?

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

August 30, 2019

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

Matgen84 · August 30, 2019

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.

August 30, 2019

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 August 30, 2019 by ricoc90

pkdesign · August 30, 2019

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.

fusion71au · August 31, 2019

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"...

Edited August 31, 2019 by fusion71au

Slice · August 31, 2019

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?

Sherlocks · August 31, 2019

hi @Slice

10.6 folder was removed in package.

is not 10.6 folder support now?

LockDown · September 1, 2019

Its still supported as long you create it manually.

artur_pt · September 1, 2019

hello

new update for Catalina last dev in platform.c

thanks to all dev

Sherlocks · September 1, 2019

5 hours ago, ellaosx said:

Its still supported as long you create it manually.

already there is 10.6 folder. but after install clover, 10.6 will be removed

fusion71au · September 1, 2019

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

CLOVERX64_r5059.zip

Edited September 3, 2019 by fusion71au
Custom entry for macOS createinstallmedia installer now working for Clover r5059+

Slice · September 2, 2019

I also think the check is redundant. Committed.

SoThOr · September 2, 2019

15 hours ago, fusion71au said:

LOL, I'm not a developer so I was hoping you might know ....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?

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