Clover General discussion

artur_pt · May 29, 2015

hello renegade...

ahahahah

i miss all info about clover .. not only but .. clover many things are in projectosx

i will be happy if anyone could get that info .. and post here

all the best .. regards

mac09hack · May 30, 2015

Is there a way to modify the text of what comes up as Clover starts up? I have three copies of MacOS on my computer and two are on Fusion drives (bootX) - I would like to be able to indentify the OS's that are installed on each Fusion drive. (Yosemite and Mavericks) at startup.

toleda · May 30, 2015

Nvidia GeForce GT 640 with Chameleon, Nvidia Chip Model with Clover. Both: 10.10.3/Official Drivers. Any suggestions?

Console/All Messages/nvda:

10.10.3
Clover 3021
Graphics/Nvidia=NO
5/29/15 7:47:33.000 PM kernel[0]: NVDAStartup: Official
5/29/15 7:47:33.000 PM kernel[0]: NVDAGK100HAL loaded and registered
5/29/15 7:47:34.000 PM kernel[0]: NVDA::rmStart failed
5/29/15 7:47:34.000 PM kernel[0]: NVDA,Display-B: Not usable
5/29/15 7:47:34.000 PM kernel[0]: NVDA,Display-C: Not usable
5/29/15 7:47:34.000 PM kernel[0]: NVDA,Display-D: Not usable

Graphics/Nvidia=YES
5/29/15 8:19:07.000 PM kernel[0]: NVDAStartup: Official
5/29/15 8:19:07.000 PM kernel[0]: NVDAGK100HAL loaded and registered
5/29/15 8:19:08.000 PM kernel[0]: NVDA::rmStart failed
5/29/15 8:19:08.000 PM kernel[0]: NVDA,Display-B: Not usable

Chameleon
GraphicsEnabler+NO
5/29/15 8:39:51.000 PM kernel[0]: NVDAStartup: Official
5/29/15 8:39:51.000 PM kernel[0]: NVDAGK100HAL loaded and registered

Chameleon/Clover

config.plist.zip

Slice · May 30, 2015

Nvidia GeForce GT 640 with Chameleon, Nvidia Chip Model with Clover. Both: 10.10.3/Official Drivers. Any suggestions?

Console/All Messages/nvda:

10.10.3
Clover 3021
Graphics/Nvidia=NO
5/29/15 7:47:33.000 PM kernel[0]: NVDAStartup: Official
5/29/15 7:47:33.000 PM kernel[0]: NVDAGK100HAL loaded and registered
5/29/15 7:47:34.000 PM kernel[0]: NVDA::rmStart failed
5/29/15 7:47:34.000 PM kernel[0]: NVDA,Display-B: Not usable
5/29/15 7:47:34.000 PM kernel[0]: NVDA,Display-C: Not usable
5/29/15 7:47:34.000 PM kernel[0]: NVDA,Display-D: Not usable

Graphics/Nvidia=YES
5/29/15 8:19:07.000 PM kernel[0]: NVDAStartup: Official
5/29/15 8:19:07.000 PM kernel[0]: NVDAGK100HAL loaded and registered
5/29/15 8:19:08.000 PM kernel[0]: NVDA::rmStart failed
5/29/15 8:19:08.000 PM kernel[0]: NVDA,Display-B: Not usable

Chameleon
GraphicsEnabler+NO
5/29/15 8:39:51.000 PM kernel[0]: NVDAStartup: Official
5/29/15 8:39:51.000 PM kernel[0]: NVDAGK100HAL loaded and registered

Chameleon/Clover

config.plist.zip

Your config.plist

A question about Nvidia, isn't it?

insanelyDeepak · May 30, 2015

Here is issue i faced shows only v2.3k no revision

Sherlocks · May 30, 2015

hello slice.

i report custom legacy option.

<key>Custom</key>

<dict>

<key>Legacy</key>

<array>

<dict>

<key>Disabled</key>

<false/>

<key>FullTitle</key>

<string>Hide Win Data</string>

<key>Hidden</key>

<true/>

<key>Ignore</key>

<false/>

<key>Type</key>

<string>Windows</string>

<key>Volume</key>

<string>Legacy HD3</string>

</dict>

<dict>

<key>Disabled</key>

<false/>

<key>FullTitle</key>

<string>Windows 7</string>

<key>Hidden</key>

<false/>

<key>Ignore</key>

<false/>

<key>Type</key>

<string>Windows</string>

<key>Volume</key>

<string>Legacy HD2</string>

</dict>

</array>

Title change work on Legacy HD2.

but, Ignored, Hidden, Disabled are not work on Legacy HD3.

i'm tested last clover r3215.

here is log

2:336 0:019 Custom legacy start

2:336 0:000 Custom legacy 0 skipped because it is hidden.

2:336 0:000 Custom legacy 1 matching "Legacy HD2" ...

2:336 0:000 Checking volume "Whole Disc Boot" (PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)) ... skipped because volume is not legacy bootable

2:336 0:000 Checking volume "Whole Disc Boot" (PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0x0,0x0)) ... skipped because volume is not legacy bootable

2:336 0:000 Checking volume "EFI" (PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(1,GPT,1570E32D-2A04-4041-B434-CEC6DB8F5D6B,0x28,0x64000)) ... skipped

2:336 0:000 Checking volume "Legacy HD2" (PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,GPT,9CF214B1-0A30-4EAD-9F8D-6BC8BFF114B9,0x64800,0xCCE4000)) ... added 'Windows 7' OSType=2 Icon=vista,win

2:339 0:003 match!

2:339 0:000 Checking volume "Legacy HD3" (PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(3,GPT,0F61706F-267F-4EBC-ACEE-BBC1D8252332,0xCD48800,0x6FC2000)) ... skipped

2:339 0:000 Checking volume "Macintosh HD" (PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(4,GPT,75F4915D-AAA7-4EC6-A38E-44F48CD01B26,0x13D0A800,0x6ECC490)) ... skipped because volume is not legacy bootable

2:339 0:000 Checking volume "Recovery HD" (PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(5,GPT,012EC0C3-EBF0-48AA-A542-8068F9A2D0B3,0x1ABD6C90,0x135F20)) ... skipped because volume is not legacy bootable

2:340 0:000 Checking volume "Mac Data" (PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(6,GPT,F29081BA-DA3F-4037-AFE3-2577CBFDBF60,0x1AD0CBB0,0x2FA66D8)) ... skipped because volume is not legacy bootable

2:340 0:000 Custom legacy end

2:340 0:000 Scanning legacy ...

2:340 0:000 0: 'Whole Disc Boot' (legacy) not legacy

2:340 0:000 1: 'Whole Disc Boot' (legacy) not legacy

2:340 0:000 2: 'EFI' (clover) add legacy

2:343 0:003 added 'Boot Clover from EFI' OSType=3 Icon=clover

2:343 0:000 3: 'Legacy HD2' (vista,win) add legacy

2:343 0:000 4: 'Legacy HD3' (vista,win) add legacy

2:345 0:001 added 'Boot Windows from Legacy HD3' OSType=2 Icon=vista,win

2:345 0:000 5: 'Macintosh HD' (legacy) not legacy

2:345 0:000 6: 'Recovery HD' (legacy) not legacy

2:345 0:000 7: 'Mac Data' (legacy) not legacy

toleda · May 30, 2015

A question about Nvidia, isn't it?

Yes. attached config.plist shows case: config.plist/Graphics/Nvidia=NO, results in Console errors reported

Second case: config.plist/Graphics/Nvidia=YES (config.plist not attached), results in Console errors reported

droples · May 31, 2015

Here is issue i faced shows only v2.3k no revision

screen.png

Official stable version http://sourceforge.net/projects/cloverefiboot/files/

Assembly using CloveGrowerPro

Building from source

Perhaps you need to perform @ cloverpro -u

insanelyDeepak · May 31, 2015

Official stable version http://sourceforge.net/projects/cloverefiboot/files/

Stable.jpg

Assembly using CloveGrowerPro

CloverGrower.jpg

Building from source

Clover.jpg

Perhaps you need to perform @ cloverpro -u

Thanks for reply

tried clover pro -u and -r 3215

same results

also tried to start from scratch nothing happens

GhostRaider · May 31, 2015

Has anyone here dealt with MSI motherboards here? I have an H81M-E34 and both Windows 8 and OS X are installed in the same partition. Both of them are pure UEFI.

I installed OS X first, then Windows 8 and Windows 8 boot automatically for some reason. I went back to OS X and installed Clover to the EFI partition. Even though Clover is in the EFI partition, Windows boots automatically regardless. In the EFI partition I can see both Clover and Windows boot folders.

I checked the MSI Click Bios screen and then clicked on UEFI Hard Drive BBS and there is no way to manually specify CloverX64. It just shows the hard drive with Windows Boot Manager. Is this a limitation of MSI motherboards? The only way I can use Clover is to use an external flash drive.

The only solution I found to this is to have 2 hard drives or have a hybrid MBR, or have a usb stick dedicated for clover.

Another thing that I don't understand is how Clover detects the kexts in the EFI/Clover/kext/ folder. Clover is in the EFI partition. I wanted to have FakeSMC in these folders instead of the S/L/E folder and Clover refuses to detect it. Without FakeSMC, I get stuck with the whole UUID number and then a bunch of ++++++++++. I used the Clover installer to create the EFI partition. Then I just dragged FakeSMC to the kext folders. When I reboot, Clover does not boot OS X and gets stuck at UUID. Using Clover Configurator I set Inject to Yes but that doesn't fix the problem.

~~Does the EFI partition require special permissions to detect kexts? Because I created a Clover USB with Clover special edition installer with FakeSMC already integrated and it works.~~

EDIT: Nevermind about Clover not detecting FakeSMC. Apparently OsxAptioFixDrv-64.efi is needed for this motherboard and I forgot to copy it.

mhaeuser · May 31, 2015

You need to create a boot option for Clover. Best is to use an UEFI Shell and enter: bcfg boot add X fsY:\EFI\CLOVER\CLOVERX64.EFI "Clover OS X Boot" where X is the first free index for a boot option (check via bcfg boot dump) and Y the identifier for the partition Clover is on (use ls fsY:)

GhostRaider · May 31, 2015

You need to create a boot option for Clover. Best is to use an UEFI Shell and enter: bcfg boot add X fsY:\EFI\CLOVER\CLOVERX64.EFI "Clover OS X Boot" where X is the first free index for a boot option (check via bcfg boot dump) and Y the identifier for the partition Clover is on (use ls fsY:)

I've pressed F11 on the Bios screen and selected UEFI shell. Then I'm getting the error message that bcfg is not recognized as an internal or external command, operable program or batch file.

Do I have to use some other shell? If so which one is best? Didn't realize MSI motherboards are harder to configure.

I also had my Clover USB Yosemite installer connected and it had a shell. I booted it and got this:

Here the bcfg commands works but i'm not sure how to proceed. Clover is installed in the EFI partition but how can you tell from here?

BIOS UEFI Hard Disk BB:

EFI Partition:

These are the files inside that partition just for confirmation.

liujianwei · May 31, 2015

Why I set Performance level(Performance level: It is tRD of DRAM parameter):to 10 or 15,after boot to osx86 yosemite,it restore to auto,but if I only boot to windows it doesn't change?How can I set it permanently if I use yosemite?And do I need turn off CPU Feature like EIST C1E?

fusion71au · June 1, 2015

I checked the MSI Click Bios screen and then clicked on UEFI Hard Drive BBS and there is no way to manually specify CloverX64. It just shows the hard drive with Windows Boot Manager. Is this a limitation of MSI motherboards? The only way I can use Clover is to use an external flash drive.

@GhostRaider,

You can try setting the UEFI BIOS priority in Windows using the EasyUEFI tool. @besweeet reported this worked for him on his MSI H81M-P33 board in this thread.

Good Luck!

GhostRaider · June 1, 2015

@GhostRaider,

You can try setting the UEFI BIOS priority in Windows using the EasyUEFI tool. @besweeet reported this worked for him on his MSI H81M-P33 board in this thread.

Good Luck!

This is amazing, it does work! Very simple to use. Thank you Must have for MSI motherboards.

Allan · June 1, 2015

Hi there!

Someone already have this problem?

boot-args <UNPRINTABLE>

I can't add my boot-args in Nvram again.

I use:

nvram -d boot-args

nvram -c

But the values don't disappear.

And if i try add again, nothing change.

ericChng · June 2, 2015

Hi there!

Someone already have this problem?
boot-args <UNPRINTABLE>
I can't add my boot-args in Nvram again.

I use:
nvram -d boot-args
nvram -c
But the values don't disappear.

And if i try add again, nothing change.Try sudo nvram -c, followed by your password

Try sudo nvram -c, followed by your password when prompted.

ericChng · June 2, 2015

Re secure boot. The original files were "lost" when Project OS X disappeared.

Any chance of a quick setup guide particularly in respect of the computer BIOS and the application to sign the Clover release?

Tks in anticipation, as I do not see a thread here.

insanelyDeepak · June 3, 2015

Here is issue i faced shows only v2.3k no revision

screen.png

Any other help still have same issue ??

@Slice

CarlosML · June 4, 2015

I'm having problems with sleep and my MSI motherboard, and after searching in the logs I found it's related to Unsynchronized TSC. Here other person had the same issue with another motherboard, and Pike determined that the CPU microcode was to blame. Now, I have no idea if it's the same in my case, but I'd like to try. Pike posted a guide for patching the updated microcode that resides in the BIOS, but I know in Linux for example bootloaders and/or the kernel can update the microcode. Is that possible using Clover + XNU?

Slice · June 4, 2015

I'm having problems with sleep and my MSI motherboard, and after searching in the logs I found it's related to Unsynchronized TSC. Here other person had the same issue with another motherboard, and Pike determined that the CPU microcode was to blame. Now, I have no idea if it's the same in my case, but I'd like to try. Pike posted a guide for patching the updated microcode that resides in the BIOS, but I know in Linux for example bootloaders and/or the kernel can update the microcode. Is that possible using Clover + XNU?

May be using VoodooTSC.kext?

anibalin · June 5, 2015

I'm having a weird issue (maybe its not).

The thing is that it happened in two different mainboards. Asus H97M-E & GA-Z97M-D3H

I have to untick every dsdt fix on clover configurator in order to have a bootable system. Other than that, not problem.

But when I try to patch AppleHDA I first open DPCIManager to see what codec to use and -sometimes I get it populated and sometimes not-. So I cannot properly use audio_cloverALC-100.command.

Using clover 3202.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>ACPI</key>
	<dict>
		<key>DSDT</key>
		<dict>
			<key>Debug</key>
			<false/>
			<key>DropOEM_DSM</key>
			<false/>
			<key>Fixes</key>
			<dict>
				<key>AddHDMI_8000000</key>
				<true/>
				<key>AddPNLF_1000000</key>
				<true/>
				<key>DeleteUnused_400000</key>
				<true/>
				<key>FIX_ACST_4000000</key>
				<true/>
				<key>FIX_ADP1_800000</key>
				<true/>
				<key>FIX_RTC_20000</key>
				<true/>
				<key>FIX_S3D_2000000</key>
				<true/>
				<key>FixRegions_10000000</key>
				<true/>
				<key>NewWay_80000000</key>
				<true/>
			</dict>
			<key>Name</key>
			<string>DSDT.aml</string>
			<key>ReuseFFFF</key>
			<false/>
		</dict>
		<key>DropTables</key>
		<array>
			<dict>
				<key>Signature</key>
				<string>SSDT</string>
				<key>TableId</key>
				<string>Cpu0Ist</string>
			</dict>
			<dict>
				<key>Signature</key>
				<string>DMAR</string>
			</dict>
			<dict>
				<key>Signature</key>
				<string>SSDT</string>
				<key>TableId</key>
				<string>CpuPm</string>
			</dict>
		</array>
		<key>HaltEnabler</key>
		<true/>
		<key>SSDT</key>
		<dict>
			<key>DropOem</key>
			<false/>
			<key>Generate</key>
			<true/>
		</dict>
	</dict>
	<key>Boot</key>
	<dict>
		<key>Arguments</key>
		<string>nvda_drv=1 kext-dev-mode=1</string>
		<key>Debug</key>
		<false/>
		<key>DefaultLoader</key>
		<string>boot.efi</string>
		<key>DefaultVolume</key>
		<string>LastBootedVolume</string>
		<key>Legacy</key>
		<string>PBR</string>
		<key>Secure</key>
		<false/>
		<key>Timeout</key>
		<integer>2</integer>
		<key>XMPDetection</key>
		<false/>
	</dict>
	<key>Devices</key>
	<dict>
		<key>Audio</key>
		<dict>
			<key>ResetHDA</key>
			<true/>
		</dict>
		<key>USB</key>
		<dict>
			<key>AddClockID</key>
			<true/>
			<key>FixOwnership</key>
			<true/>
			<key>Inject</key>
			<true/>
		</dict>
	</dict>
	<key>GUI</key>
	<dict>
		<key>Mouse</key>
		<dict>
			<key>DoubleClick</key>
			<integer>500</integer>
			<key>Enabled</key>
			<false/>
			<key>Mirror</key>
			<false/>
			<key>Speed</key>
			<integer>8</integer>
		</dict>
		<key>Scan</key>
		<true/>
		<key>ScreenResolution</key>
		<string>1280x1024</string>
		<key>Theme</key>
		<string>embedded</string>
	</dict>
	<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<false/>
			<key>Intel</key>
			<false/>
			<key>NVidia</key>
			<false/>
		</dict>
	</dict>
	<key>KernelAndKextPatches</key>
	<dict>
		<key>AppleRTC</key>
		<true/>
		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>t1-10.9-10.10-AppleHDA/Resources/xml>zml</string>
				<key>Find</key>
				<data>
				eG1sLnps
				</data>
				<key>Name</key>
				<string>AppleHDA</string>
				<key>Replace</key>
				<data>
				em1sLnps
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>TRIM Enabler</string>
				<key>Find</key>
				<data>
				AEFQUExFIFNTRAA=
				</data>
				<key>Name</key>
				<string>IOAHCIBlockStorage</string>
				<key>Replace</key>
				<data>
				AAAAAAAAAAAAAAA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>t1-10.9-10.10-AppleHDA/Realtek ALC887</string>
				<key>Find</key>
				<data>
				ixnUEQ==
				</data>
				<key>Name</key>
				<string>AppleHDA</string>
				<key>Replace</key>
				<data>
				hwjsEA==
				</data>
			</dict>
		</array>
	</dict>
	<key>RtVariables</key>
	<dict>
		<key>MLB</key>
		<string>C02032109R5DC771H</string>
		<key>ROM</key>
		<string>UseMacAddr0</string>
	</dict>
	<key>SMBIOS</key>
	<dict>
		<key>Manufacturer</key>
		<string>Apple Inc.</string>
		<key>Trust</key>
		<false/>
	</dict>
	<key>SystemParameters</key>
	<dict>
		<key>InjectKexts</key>
		<string>YES</string>
		<key>InjectSystemID</key>
		<true/>
	</dict>
</dict>
</plist>

anonymousnbs · June 6, 2015

I'm having a weird issue (maybe its not).

The thing is that it happened in two different mainboards. Asus H97M-E & GA-Z97M-D3H

I have to untick every dsdt fix on clover configurator in order to have a bootable system. Other than that, not problem.

But when I try to patch AppleHDA I first open DPCIManager to see what codec to use and -sometimes I get it populated and sometimes not-. So I cannot properly use audio_cloverALC-100.command.

Using clover 3202.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>ACPI</key>
	<dict>
		<key>DSDT</key>
		<dict>
			<key>Debug</key>
			<false/>
			<key>DropOEM_DSM</key>
			<false/>
			<key>Fixes</key>
			<dict>
				<key>AddHDMI_8000000</key>
				<true/>
				<key>AddPNLF_1000000</key>
				<true/>
				<key>DeleteUnused_400000</key>
				<true/>
				<key>FIX_ACST_4000000</key>
				<true/>
				<key>FIX_ADP1_800000</key>
				<true/>
				<key>FIX_RTC_20000</key>
				<true/>
				<key>FIX_S3D_2000000</key>
				<true/>
				<key>FixRegions_10000000</key>
				<true/>
				<key>NewWay_80000000</key>
				<true/>
			</dict>
			<key>Name</key>
			<string>DSDT.aml</string>
			<key>ReuseFFFF</key>
			<false/>
		</dict>
		<key>DropTables</key>
		<array>
			<dict>
				<key>Signature</key>
				<string>SSDT</string>
				<key>TableId</key>
				<string>Cpu0Ist</string>
			</dict>
			<dict>
				<key>Signature</key>
				<string>DMAR</string>
			</dict>
			<dict>
				<key>Signature</key>
				<string>SSDT</string>
				<key>TableId</key>
				<string>CpuPm</string>
			</dict>
		</array>
		<key>HaltEnabler</key>
		<true/>
		<key>SSDT</key>
		<dict>
			<key>DropOem</key>
			<false/>
			<key>Generate</key>
			<true/>
		</dict>
	</dict>
	<key>Boot</key>
	<dict>
		<key>Arguments</key>
		<string>nvda_drv=1 kext-dev-mode=1</string>
		<key>Debug</key>
		<false/>
		<key>DefaultLoader</key>
		<string>boot.efi</string>
		<key>DefaultVolume</key>
		<string>LastBootedVolume</string>
		<key>Legacy</key>
		<string>PBR</string>
		<key>Secure</key>
		<false/>
		<key>Timeout</key>
		<integer>2</integer>
		<key>XMPDetection</key>
		<false/>
	</dict>
	<key>Devices</key>
	<dict>
		<key>Audio</key>
		<dict>
			<key>ResetHDA</key>
			<true/>
		</dict>
		<key>USB</key>
		<dict>
			<key>AddClockID</key>
			<true/>
			<key>FixOwnership</key>
			<true/>
			<key>Inject</key>
			<true/>
		</dict>
	</dict>
	<key>GUI</key>
	<dict>
		<key>Mouse</key>
		<dict>
			<key>DoubleClick</key>
			<integer>500</integer>
			<key>Enabled</key>
			<false/>
			<key>Mirror</key>
			<false/>
			<key>Speed</key>
			<integer>8</integer>
		</dict>
		<key>Scan</key>
		<true/>
		<key>ScreenResolution</key>
		<string>1280x1024</string>
		<key>Theme</key>
		<string>embedded</string>
	</dict>
	<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<false/>
			<key>Intel</key>
			<false/>
			<key>NVidia</key>
			<false/>
		</dict>
	</dict>
	<key>KernelAndKextPatches</key>
	<dict>
		<key>AppleRTC</key>
		<true/>
		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>t1-10.9-10.10-AppleHDA/Resources/xml>zml</string>
				<key>Find</key>
				<data>
				eG1sLnps
				</data>
				<key>Name</key>
				<string>AppleHDA</string>
				<key>Replace</key>
				<data>
				em1sLnps
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>TRIM Enabler</string>
				<key>Find</key>
				<data>
				AEFQUExFIFNTRAA=
				</data>
				<key>Name</key>
				<string>IOAHCIBlockStorage</string>
				<key>Replace</key>
				<data>
				AAAAAAAAAAAAAAA=
				</data>
			</dict>
			<dict>
				<key>Comment</key>
				<string>t1-10.9-10.10-AppleHDA/Realtek ALC887</string>
				<key>Find</key>
				<data>
				ixnUEQ==
				</data>
				<key>Name</key>
				<string>AppleHDA</string>
				<key>Replace</key>
				<data>
				hwjsEA==
				</data>
			</dict>
		</array>
	</dict>
	<key>RtVariables</key>
	<dict>
		<key>MLB</key>
		<string>C02032109R5DC771H</string>
		<key>ROM</key>
		<string>UseMacAddr0</string>
	</dict>
	<key>SMBIOS</key>
	<dict>
		<key>Manufacturer</key>
		<string>Apple Inc.</string>
		<key>Trust</key>
		<false/>
	</dict>
	<key>SystemParameters</key>
	<dict>
		<key>InjectKexts</key>
		<string>YES</string>
		<key>InjectSystemID</key>
		<true/>
	</dict>
</dict>
</plist>

config.plist.zip

try this and report

D-an-W · June 6, 2015

Re secure boot. The original files were "lost" when Project OS X disappeared.

Any chance of a quick setup guide particularly in respect of the computer BIOS and the application to sign the Clover release?

Tks in anticipation, as I do not see a thread here.

Did you get any further with this, I have to be honest I completely forgot how to implement Secure Boot when we first tested it on Project OS X?!?

anibalin · June 6, 2015

config.plist.zip

try this and report

You rock!

what was that?

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