Jump to content
ErmaC

Clover General discussion

21,380 posts in this topic

Recommended Posts

Hi Guys,

 

I have an issue with Clover overwriting NVRAM.PLIST with an MLB value that does not correspond to the the value I setup in Config.plist.

I would not mind if the nvram value is the same as the config.plist one (17 Chars) but the clover injected value is strange (18 Chars) and I do not know where clover gets it from (it is always the same). I have tried deleted nvram.lis and resting it but in vain.

 

Please note that I am triple booting Win8.1/Yosemite/Maverick on a single disk MBR system (Dell XPS M1530). It does work except from the MLB issue described above. (too much work to convert to GPT) <—note to  fusion71au aka Tintin   :) .

 

Having checked the boot.log file, I arrived at the rc.shutdown.log which shows that the nvram.plist is actually updated at shutdown:

 

>> Begin Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local

NVRAM saved to '/nvram.plist' [disk0s2]

>> End Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local

 

 

I have 2 questions:

 

1- Is there an option to stop Clover updating the NVRAM file at shutdown ?

 

2- Where is the injected MLB value gotten from ? Is is cached somewhere?

 

Thanks in advance

 

boot.log.zip

Share this post


Link to post
Share on other sites
Advertisement

Hey slice and others, 

 

can you _PLEASE_ add the following information to your Clover online documentation:

 

 

- Some UEFI boards like (my) Asus-B85M-G only support booting from the very first partition on a GPT formatted drive!  So if you have an EFI partition first, and you want to boot from an HFS+ partition after the first EFI partition (2+), you will need to write the boot1h2 partition boot block to the first EFI-partition!   So boot1h2 is capable of booting another partition than it is installed on. In my case, my first partition is EFI formatted with FAT32, using boot1h2 (yes believe it or not). This EFI partition has no contents, it is empty! The second partition is the Boot partition, formatted with HFS+ and clover installed on it. The first EFI partition must be also marked as active!  I use boot0ss.

 

Guys, please extract the information from this and add it to your docs, since this is the only way with my main board to boot from a GPT formatted drive. I tested all combinations for hours.

 

So, the extract is:

 

Some UEFI boards will support partition boot from the first partition only, if the drive is formatted with GPT. This first partition is usually the EFI partition, which can be empty and formatted with any format (HFS+ / FAT32 or other). Writing boot1h2 to the first (EFI) partition enables the computer to load clover from another partition after the first partition.

Clover documentation recommends you the follow

GPT partitioned drive. Pure GPT, not Hybrid! No active partitions!

First partition is EFI formatted to FAT32 (not FAT16!, not HFS+), and has partition type of 0xEF00 (and not 0x0B as usual for FAT32 partitions).

Clover installed into EFI partition. It is not recommended to install on HFS+ partition because for Clover only FAT32 can save logs and screenshots.

Sector 0 contains boot0af

Sector1 of EFI partition contains boot1f32alt

EFI partition contains all bootloaders you may imagine

Screen Shot 2015-04-23 at 17.03.44.png

Share this post


Link to post
Share on other sites

Hey guys, it has been a while and oh boy, projectosx is gone too...  :(

 

Anyway, I upgraded Clover from r2953 to r3193, no config changes, and suddenly, my "automatic" boot stopped working. Trying to search this topic for information yielded a few results, but that was with people using the wrong volume name, and I'm using DefaultVolume with GUID.

 

I've been playing with it, timeout 1 and timeout 0 on boot section, and sure enough, timeout 1 works, but 0 doesn't anymore.

 

This system has a Fusion Drive, thus why "Boot OS X".

 

So, with timeout 1, here are the relevant portions of boot.log:

0:108  0:008  Using OEM config.plist at path: EFI\CLOVER\config.plist
0:108  0:000  EFI\CLOVER\config.plist loaded: Success
0:108  0:000  Loading early settings
0:108  0:000  timeout set to 1
0:108  0:000  Custom boot CUSTOM_BOOT_DISABLED (0x0)
...
0:838  0:000  GetEfiBootDeviceFromNvram: efi-boot-device-data not found
0:838  0:000  EfiBootVolume not found
0:838  0:000   found entry 0. 'Boot Mac OS X from Boot OS X', Volume 'Boot OS X', DevicePath 'PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(3,GPT,4E0887AC-E303-46D7-A873-A9462BF539E0,0x170EE1A8,0x40000)\System\Library\CoreServices\boot.efi'
0:838  0:000  DefaultIndex=0 and MainMenu.EntryCount=6
0:856  0:018  GUI ready
2:856  2:000  StartLoader() start

Now, with timeout 0:

0:108  0:008  Using OEM config.plist at path: EFI\CLOVER\config.plist
0:108  0:000  EFI\CLOVER\config.plist loaded: Success
0:108  0:000  Loading early settings
0:108  0:000  timeout set to 0
0:108  0:000  Custom boot CUSTOM_BOOT_DISABLED (0x0)
...
0:471  0:000  GetEfiBootDeviceFromNvram: efi-boot-device-data not found
0:471  0:000  EfiBootVolume not found
0:471  0:000   found entry 0. 'Boot Mac OS X from Boot OS X', Volume 'Boot OS X', DevicePath 'PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(3,GPT,4E0887AC-E303-46D7-A873-A9462BF539E0,0x170EE1A8,0x40000)\System\Library\CoreServices\boot.efi'
0:471  0:000  DefaultIndex=0 and MainMenu.EntryCount=6
0:859  0:388  GUI ready
12:318  11:459  Boot option Boot0000 not found
12:319  0:000  StartLoader() start

Just so the timing makes sense, I took about 10 seconds to press Enter.

 

Would anyone have any idea of what could be holding the startup from automatically continuing to the default option?

 

I've noticed the "Boot option" extra line, but I have no clue of what it means.

Share this post


Link to post
Share on other sites

Hi there,

 

seems I cannot boot into safe mode anymore. Instead I get this:

 

Y59smGD.jpg

 

Because this happens very early (seems my comp cannot even load kernelcache), I think it might be connected to Clover?

 

Any ideas what could cause this?

Share this post


Link to post
Share on other sites

Hi Guys,

 

I have an issue with Clover overwriting NVRAM.PLIST with an MLB value that does not correspond to the the value I setup in Config.plist.

I would not mind if the nvram value is the same as the config.plist one (17 Chars) but the clover injected value is strange (18 Chars) and I do not know where clover gets it from (it is always the same). I have tried deleted nvram.lis and resting it but in vain.

 

Please note that I am triple booting Win8.1/Yosemite/Maverick on a single disk MBR system (Dell XPS M1530). It does work except from the MLB issue described above. (too much work to convert to GPT) <—note to  fusion71au aka Tintin   :) .

 

Having checked the boot.log file, I arrived at the rc.shutdown.log which shows that the nvram.plist is actually updated at shutdown:

 

>> Begin Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local

NVRAM saved to '/nvram.plist' [disk0s2]

>> End Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local

 

 

I have 2 questions:

 

1- Is there an option to stop Clover updating the NVRAM file at shutdown ?

 

2- Where is the injected MLB value gotten from ? Is is cached somewhere?

 

Thanks in advance

 

Hi @RN95,

 

Check the syntax/formatting of your config.plist file - maybe there is an error there somewhere.

 

Clover injects MLB from either RtVariables/MLB or SMBIOS/BoardSerialNumber but I would recommend injecting the MLB string from RtVariables and deleting BoardSerialNumber in SMBIOS to avoid conflicts:

<key>MLB</key>
<string>XXXXXXXXXXXXXXXXX</string>

Since our XPS M1530 don't have real NVRAM, I wouldn't recommend disabling the RC scripts since the NVRAM.plist file is needed for proper function of iMessage/Facetime (from your bootlog, this plist is located on the root of your Yos volume).  You can try resetting the NVRAM using terminal:

sudo rm /nvram.plist
sudo nvram -c

Good Luck!

Share this post


Link to post
Share on other sites

And what do you want to say? Clover never working?

Post#6 How to use - common words

 

Well I'm able to finally get past clover and into the OSX kernel. 

 

Adding DumpUefiCalls.efi allows me to boot into UEFI clover and get through it.   I don't understand why that would make a difference, but removing it prevents boot and adding lets it continue to the kernel.

 

However I get an early kernel panic.  Depending on kernel patches selected I see two different panics.  Both are attached along with clover and eficall logs, and plist

post-205145-0-56639400-1429835985_thumb.jpg

post-205145-0-33367800-1429836023_thumb.jpg

debug.txt

EfiCalls.txt

config.plist.txt

Share this post


Link to post
Share on other sites

Post your Clover boot.log (found in /Library/Logs/CloverEFI or the output of bdmesg in terminal).

 

Maybe Clover is reading the wrong config.plist eg you have installed Clover in more than one place?  You can also try resetting your NVRAM in terminal:

sudo rm /nvram.plist
sudo nvram -c

The boot.log should show which config.plist is being used eg for my desktop....

Using OEM config.plist at path: EFI\CLOVER\OEM\P55A-UD3\config.plist

and whether it finds the default boot volume...

thank you !!
was having a conflict of config.plist
one in the EFI partition and another in the root system

 

Now everything is resolved, automatic assembly of the EFI partition does not work
 
<key>RtVariables</key>
	<dict>
		<key>MountEFI</key>
		<true/>		
	</dict>

Share this post


Link to post
Share on other sites

 

thank you !!
was having a conflict of config.plist
one in the EFI partition and another in the root system

 

Now everything is resolved, automatic assembly of the EFI partition does not work
 
<key>RtVariables</key>
	<dict>
		<key>MountEFI</key>
		<true/>		
	</dict>

 

Mount EFI in RT Variables is long time obsolete, see chris1111 post 6832 above, mount EFI is actioned  thru the Clover Prefpane which write to to your nvram.

Share this post


Link to post
Share on other sites

Hi @RN95,

 

Check the syntax/formatting of your config.plist file - maybe there is an error there somewhere.

 

Clover injects MLB from either RtVariables/MLB or SMBIOS/BoardSerialNumber but I would recommend injecting the MLB string from RtVariables and deleting BoardSerialNumber in SMBIOS to avoid conflicts:

<key>MLB</key>
<string>XXXXXXXXXXXXXXXXX</string>

Since our XPS M1530 don't have real NVRAM, I wouldn't recommend disabling the RC scripts since the NVRAM.plist file is needed for proper function of iMessage/Facetime (from your bootlog, this plist is located on the root of your Yos volume).  You can try resetting the NVRAM using terminal:

sudo rm /nvram.plist
sudo nvram -c

Good Luck!

Hi Fusion,

 

Thank you for your input on the above issue and the relentless and dedicated support you have been providing us. I have tried the above suggestions already but in vain. 

 

Even though the MLB is correct in both SMBios and Rtvariables sections, the NVRAM.plist gets updated on "Shutdown" with an MLB value different from the one in the config.plist. 

 

What bugs me is where is the shutdown script getting this value from? is it cashed?

 

I was hoping that Slice could answer that.

 

Thanks anyway

Best regards

 

P.S. Could it be related to the fact that I am using an MBR disk with no EFI partition. Clover is booting from an EFI folder in the   root of the boot disk.

Share this post


Link to post
Share on other sites

@RN95,

 

I'm pretty sure the problem isn't related to your MBR install vs GPT/EFI (Clover should work in both cases).

 

Maybe Clover is reading the wrong config.plist file or NVRAM.plist?  Have you installed Clover on both your Yosemite and Mavericks partitions?  Do you have more than one /EFI/Clover folder?

 

Try booting with a single partition, FAT32 & MBR formatted Clover USB and run imessage_debug ---> MLB value should be the one injected by the config.plist on the USB.

 

Clover's rc shutdown script only records changes to NVRAM variables between boots, not over-ride your config.plist values.  You can test by resetting your NVRAM, then disabling/renaming the file 80.save_nvram_plist.local (hidden in /private/etc/rc.shotdown.d) to 80.save_nvram_plist.local.disabled.

 

Edit

Glad to hear you've solved your problem :).

 

Still don't know how you ended up with an 18 character MLB in the first place :blink:.

Share this post


Link to post
Share on other sites

@RN95,

 

I'm pretty sure the problem isn't related to your MBR install vs GPT/EFI (Clover should work in both cases).

 

 

@Fusion71au,

 

Thanks again for your response.

 

I have tried to hide all EFI folders on the mac partition. I have even rename the 80.save_nvram_plist.local script file so as not to overwrite it at shutdown. This was quite tricky as I had to boot into Mavericks, edit the file (removing the MLB/ROM sections) then rebooted into Yosemite. It still recreated the NVRAM with the unwanted MLB string. It is as if there was an invisible EFI partition/Folder.

 

It must be cashed somewhere.

 

The reason I suspected the MBR install is that I read that on UEFI systems (I have a haswell based PC which works perfectly with iMessage) clover does not bother with overwriting the NVRAM. In fact I have checked it and the nvram.plist file does not contain MLB and ROM values.

 

All in all it seems to ignore the config.plist values and gives priority to the NVRAM values. 

 

Is it possible to manually inject the ROM/MLB values before shutting down?

 

Cheers

Share this post


Link to post
Share on other sites

Slice, the recent sourceforge clover build has the following bugs and problems:

 

- If I boot in non verbose mode, fakesmc is not loaded. If I boot in verbose mode, it is loaded.

 

- Sometimes, my in kext placed voodoohda will not load, sometimes it will load.

 

- I use the boot in which I can press 1-6 for a specific boot loader. If it loads the default nr. 6, "5" will be written now. 5 != 6  . Also the delay could be a lot shorter.

 

- I am booting from one SATA drive, but clover will be used on another drive. Maybe this is because of wrong(?), boot1 blocks, or the bios is too old to support it (no GPT support I guess).   But the problem is, there is no indication in clover, from which drive clover + config was started. Please add such a message.

 

- The new blue background is ugly.

 

Please fix, thanks for this great loader.

Share this post


Link to post
Share on other sites

@RN95

Make full DarwinDumper report (without BIOS to reduce size) for us to see what about you.

     DarwinDumper    

@ Slice, @Fusion71au,

 

Thank you for your interest in my issue. However I think I found a workaround:

Please note that this is valid for an MBR Based system with Legacy (Non UEFI Bios).

 

Lessons learnt:

1- The culprit RC script is "80.save_nvram_plist.local" which insists on saving the NVRAM.plist file at each shutdown (not boot up).

     Note that there is a function which checks :"# Check if user requested to not save nvram"

     but this option does not seem to exist in t Configurator.

    

     @Slice : can one request not to save NVRAM in config.plist?

 

2- When I said in a previous post that I "renamed" the above script, I only put an "under-score" before the file name. That did not prevent the script from running.

 

3- NVRAM.PLIST MLB value seems to override the one in Config.plist.

 

The Workaround consisted of:

 

a - deleting the "80.save_nvram_plist.local" from /etc/rc.shutdown.d/ completely

b - Delete nvram.plist file from root directory

c - Reboot

d - Presto: the config.plist MLB values are injected. 

e - iMessage, FaceTime are now working.

 

I copied "80.save_nvram_plist.local" back and, although it creates a new nvram.plist file on shutdown, it does not affect my MLB anymore.

 

Hope this is helpful.

Rgds

Share this post


Link to post
Share on other sites

Hi Slice do you please when you have time to  check Typo description in the Installer distribution

 

All theme as  _title  

 

Thanks  :) 

 

223.png

Share this post


Link to post
Share on other sites

Slice, the recent sourceforge clover build has the following bugs and problems:

 

- The new blue background is ugly.

 

The blue background is because the installer deletes previously installed themes. In my case I had bootcamp set as my Clover theme and this was wiped by the update to r3202. So when it tried to draw the theme it ends up half-drawing the embedded theme instead, causing the blue background. I just copied the bootcamp theme back into my EFI folder from the backup made by the Clover installer and everything was back to normal again.

Share this post


Link to post
Share on other sites

Hi Slice do you please when you have time to  check Typo description in the Installer distribution

 

All theme as  _title  

 

Thanks  :) 

 

223.png

yes, I see.

The titile and descriptions for every themes must be written into installer scripts and into language translation files. I can add in english and in russian for current set of themes but the problem is much more compex. We should somehow includes theme description from theme folder and may be propose translations if accessible.

Share this post


Link to post
Share on other sites

Is anyone else seeing this issue during their build of the latest clover using CLoverGrower Pro?  I am still able to build the latest release but not sure if their is a simple fix for this?  Also should I choose SVN or Github during the sh configuration stages?

 

Do I need to upgrade or is this a source forge svn issue?

 

http://subversion.apache.org/faq.html#working-copy-format-change

 

 

Cloverx64 release OK

 

Clover Grower Complete Build process took 1m25s to complete...

 

Type 'm' To make Clover_v2_r3202.pkg...

m

cd to /Users/osxfr33k/CloverGrowerPro/edk2/Clover/CloverPackage and run ./makepkg.

svn: E155036: Working copy '/Users/osxfr33k/CloverGrowerPro/edk2/Clover/CloverPackage' is too old (format 9, created by Subversion 1.5)

Share this post


Link to post
Share on other sites

I don't see problems.

Last login: Mon Apr 27 07:42:10 on console
iMac-Droplets:~ droplets$ cloverpro -u
Checking for new version of CloverGrowerPro...
Current branch master is up to date.
********************************************
*              Good Morning                *
*     Welcome To CloverGrowerPro v5.0      *
*           This script by JrCs            *
*        Original script by STLVNUB        *
* Clover Credits: Slice, dmazar and others *
********************************************
running 'CloverGrowerPro.sh' on 'Mavericks'
Work Folder: /Users/droplets/CloverGrowerPro
Available  : 84348 MB
Clover Update Detected !
******** Clover Package STATS **********
*       local  revision at 3194        *
*       remote revision at 3202        *
*       Package Built   =  No          *
****************************************
Getting SVN Source, Hang ten…
    Checked, Updates found...
    Auto Updating edk2 From 17120 to 17200 ...
    ......
    ........
 --------------------------
 Building process complete!
 --------------------------
 Build info.
 ===========
  Package name: Clover_v2.3k_r3202.pkg
  MD5:          4905d34421bb81b5795da3b85f231b2b
  Version:      v2.3k
  Stage:        v2.3k
  Date/Time:    2015-04-27 07:48:18
  Built by:     droplets
  Copyright     2012-2014
  adding: Clover_v2.3k_r3202.pkg (deflated 0%)
  adding: Clover_v2.3k_r3202.pkg.md5 (stored 0%)
open builtPKG
Good Morning  .
Ejecting RAM disk
"disk1" unmounted.
"disk1" ejected.
iMac-Droplets:~ droplets$ 
    

Share this post


Link to post
Share on other sites

Well I am able to complete the build.  I also chose to be Asked to create the modules "m"  It does not look like you chose that way and to auto make so maybe that message does not show up on yours?  Are you on 10.10.3 with the latest xcode which probably does not matter as this is a SVN version message.  I believe this is their end not mine, because I am running JRc script and did a fresh install.  What advantage is it using SVN versus Github?  You can choose either/or during the sh configuration.

 

 

 

Edited:

 

Figured it out not sure why though?   I am guessing I have been upgrading my 10.10x up to 10.10.3, only 10.10.0 was a clean install.  I had svn client v1.5.5 installed so maybe the svn was not updating properly from the OS X upgrades not sure what the reason is, but I updated to 1.8x and ran another clean install of CloverGrower Pro.  The svn message is no longer there.

 

My fix:

 

http://www.jarysta.com/2014/10/16/updating-to-svn-1-8-for-mac-os-x-10-10-yosemite/

 

 

Just not sure if these error: (null) messages are normal or not?

Generating BootSectors
[NASM] boot0af.s -> /Users/osxfr33k/CloverGrowerPro/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot0af
[NASM] boot0ss.s -> /Users/osxfr33k/CloverGrowerPro/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot0ss
[NASM] boot1h.s -> /Users/osxfr33k/CloverGrowerPro/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1h
[NASM] boot1h2.s -> /Users/osxfr33k/CloverGrowerPro/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1h2
[NASM] boot1f32.s -> /Users/osxfr33k/CloverGrowerPro/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1f32
[NASM] boot1f32alt.s -> /Users/osxfr33k/CloverGrowerPro/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1f32alt
[NASM] boot1x.s -> /Users/osxfr33k/CloverGrowerPro/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1x
[NASM] boot1xalt.s -> /Users/osxfr33k/CloverGrowerPro/edk2/Clover/CloverPackage/CloverV2/BootSectors/boot1xalt
Description.txt -> /Users/osxfr33k/CloverGrowerPro/edk2/Clover/CloverPackage/CloverV2/BootSectors/Description.txt
Installation.txt -> /Users/osxfr33k/CloverGrowerPro/edk2/Clover/CloverPackage/CloverV2/BootSectors/Installation.txt
Done!
Cloverx64 release OK

Clover Grower Complete Build process took 1m17s to complete...

Type 'm' To make Clover_v2_r3202.pkg...
m
cd to /Users/osxfr33k/CloverGrowerPro/edk2/Clover/CloverPackage and run ./makepkg.

========= Translating Resources ========
Updating 'en' strings file for CloverUpdater... done
Updating 'en' strings file for Clover Preference Panel... done
Updating strings file for Clover Preference Panel... done
 (180 entries)
Discard ../sym/Resources/Clover/Resources/sv.lproj/Welcome.html (0 of 10 strings; only 0% translated; need 80%).
Discard ../sym/Resources/Clover/Resources/sv.lproj/Description.html (0 of 29 strings; only 0% translated; need 80%).
Discard ../sym/Resources/Clover/Resources/sv.lproj/Conclusion.html (0 of 4 strings; only 0% translated; need 80%).
Discard ../sym/Resources/Clover/Resources/sv.lproj/Localizable.strings (0 of 90 strings; only 0% translated; need 74%).
Discard ../CloverUpdater/src/sv.lproj/CloverUpdater.strings (0 of 12 strings; only 0% translated; need 74%).
Discard ../CloverPrefpane/src/sv.lproj/CloverPrefpane.strings (0 of 39 strings; only 0% translated; need 74%).
Discard ../CloverPrefpane/src/sv.lproj/Localizable.strings (0 of 10 strings; only 0% translated; need 74%).
Discard ../sym/Resources/Clover/Resources/tr.lproj/Description.html (22 of 29 strings; only 75.86% translated; need 80%).

Building CloverUpdater application...
2015-04-27 00:38:38.996 xcodebuild[96540:460246] error: (null)
[XCODE]
Building CloverPrefpane preference...
2015-04-27 00:38:44.278 xcodebuild[96624:460594] error: (null)
[XCODE]
================= Making all in fdisk440 =================
	[MKDIR] /Users/osxfr33k/CloverGrowerPro/edk2/Clover/CloverPackage/sym/build/fdisk440
	[CC32] auto.c
	[CC32] cmd.c
	[CC32] disk.c
	[CC32] fdisk.c
	[CC32] getrawpartition.c
	[CC32] mbr.c
	[CC32] misc.c
	[CC32] opendev.c
	[CC32] part.c
	[CC32] user.c
	[CC64] auto.c
	[CC64] cmd.c
	[CC64] disk.c
	[CC64] fdisk.c
	[CC64] getrawpartition.c
	[CC64] mbr.c
	[CC64] misc.c
	[CC64] opendev.c
	[CC64] part.c
	[CC64] user.c
	[LD32] fdisk440_32
	[LD64] fdisk440_64
	[LIPO] /Users/osxfr33k/CloverGrowerPro/edk2/Clover/CloverPackage/sym/utils/fdisk440
================= Making all in boot1-install =================
	[XCODE] boot1-install
2015-04-27 00:38:51.144 xcodebuild[96894:461158] error: (null)
================= Making all in partutil =================
	[XCODE] partutil
2015-04-27 00:38:52.087 xcodebuild[96926:461270] error: (null)
================= Making all in bdmesg =================
	[XCODE] bdmesg
2015-04-27 00:38:52.776 xcodebuild[96950:461325] error: (null)
================= Making all in clover-genconfig =================
	[XCODE] clover-genconfig
2015-04-27 00:38:53.382 xcodebuild[96981:461389] error: (null)

  ----------------------------------
  Building Clover Install Package
  ----------------------------------

====================== Preinstall ======================
	[BUILD] Pre
===================== Installation =====================
	[BUILD] UEFI.only
================== Target ESP ==========================
	[BUILD] Target.ESP
=================== BiosBoot ===========================
	[BUILD] BiosBoot
===================== Utils ============================
	[BUILD] Utils
===================== EFI folder =======================
	[BUILD] EFIFolder
===================== BootLoaders ======================
	[BUILD] AltBoot
	[BUILD] bootNo
	[BUILD] boot0af
	[BUILD] boot0ss
====================== CloverEFI =======================
	[BUILD] cloverEFI.64.sata
======================== Themes ========================
	[BUILD] applestyle
	[BUILD] BGM
	[BUILD] black_green
	[BUILD] bluemac
	[BUILD] bootcamp
	[BUILD] iclover
	[BUILD] magnifico
	[BUILD] metal
	[BUILD] mrengles
	[BUILD] orange
	[BUILD] os_box
	[BUILD] os_one
	[BUILD] Shield
	[BUILD] thinkpad
================= drivers64 mandatory ==================
	[BUILD] FSInject-64
===================== drivers64 ========================
	[BUILD] GrubEXFAT-64
	[BUILD] GrubISO9660-64
	[BUILD] GrubNTFS-64
	[BUILD] GrubUDF-64
	[BUILD] NvmExpressDxe-64
	[BUILD] Ps2MouseDxe-64
	[BUILD] UsbMouseDxe-64
	[BUILD] VBoxExt2-64
	[BUILD] VBoxExt4-64
	[BUILD] VBoxIso9600-64
	[BUILD] XhciDxe-64
=============== drivers64 UEFI mandatory ===============
	[BUILD] FSInject-64.UEFI
	[BUILD] OsxFatBinaryDrv-64.UEFI
	[BUILD] VBoxHfs-64.UEFI
=================== drivers64 UEFI =====================
	[BUILD] CsmVideoDxe-64
	[BUILD] DataHubDxe-64
	[BUILD] EmuVariableUefi-64
	[BUILD] OsxAptioFix2Drv-64
	[BUILD] OsxAptioFixDrv-64
	[BUILD] OsxLowMemFixDrv-64
	[BUILD] PartitionDxe-64
===================== RC Scripts =======================
	[BUILD] rc.scripts.on.target
	[BUILD] rc.scripts.on.all.volumes
	[BUILD] rc.scripts.core
================= Optional RC Scripts ==================
	[BUILD] disable_sleep_proxy_client
==================== Clover Prefpane ===================
	[BUILD] CloverPrefpane
================= Post =================
	[BUILD] Post

 --------------------------
 Building process complete!
 --------------------------

 Build info.
 ===========
  Package name: Clover_v2.3k_r3202.pkg
  MD5:          31ba5da64f85271cfba85e16cf18de7f
  Version:      v2.3k
  Stage:        v2.3k
  Date/Time:    2015-04-27 00:37:20
  Built by:     osxfr33k
  Copyright     2012-2014

  adding: Clover_v2.3k_r3202.pkg (deflated 0%)
  adding: Clover_v2.3k_r3202.pkg.md5 (stored 0%)
open builtPKG
Good Night    .


Ejecting RAM disk
"disk2" unmounted.
"disk2" ejected.
osxfr33ksiMac3:CloverGrowerPro osxfr33k$ 


Edited:

 

The svn client was downgraded because of some application I installed.   Still unclear of the Error: (null)

Share this post


Link to post
Share on other sites

New Clover updates (from 3185 up) does not boot my system. I updated to 3202 and before that to 3192 , but my system was unbootable. I must revert to 3185 in order to be able to boot again. Whats the problem ? Is it only by me , or ?

Share this post


Link to post
Share on other sites

Hi. im new here

 

and i cant start a new topic but i thought id go ahead and reply here.

 

Any info on Intel 750 pcie ssd and yosemite?

 

tried installing 10.10.4 and its still a no go as it cant detect the disk at all.

 

Figured it isnt even supported anywhere, and search resaults in this forum all lead to the intel 750 cpu ofc :)

 

thanks

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 Simon's InsaneMac
      Hi, I'm kind of lost when scrolling to Clover Configurator, so I decided to use an EFI from the web and just configure the most basic stuff. But that sadly didn't work, im always getting the attached screen IMG_0054.HEIC (and I don't know whether all the errors are listed, as I can't scroll). 
      Anyways I thought it'd be better to do a custom setup. Can anyone give me some help with what to choose in the settings? Here's my rig:
      i7 8700k
      Asus z370-G (Rog Strix)
      gtx 1060 6gb
      samsung ssd (SATA)
      WD hard drive
       
      Your help would be much appreciated!
    • By kylon
      A big thanks to wegface for teaching me a lot of things.
       
       
      Tested on Catalina 10.15.4 and Clover EFI 5104 (Catalina Patcher)
       
      Not Working:
      - realtek sd card reader (pm me if you have a fix)
       
      Notes:
      **CPU patches are disabled, if you are using a locked BIOS you must enable them**
       
      Clover EFI:
      - Install it in UEFI Mode and change your hdd partition table to GPT.
      - You will be able to install ANY OS in EFI mode, even if this pc does not support EFI at all! (No guide available for this)
       
      You will need:
      My unlocked BIOS (OPTIONAL) (here) Latest Clover config from CCE Bank (here) (asus k53sj-kylon) Rehabman Voodoo PS2 Controller (here) acidanthera AppleALC (here) acidanthera Lilu (here) acidanthera VirtualSMC (here) acidanthera SMCBatteryManager (here) acidanthera SMCLightSensor (here) acidanthera WhateverGreen (here) Mieze Realtek RTL8111 (here)
    • By Rohan20
      Opencore is running really really slow on Catalina 10.15.4. So It was running perfectly before I put the ssdt-pnlf for enabling Brightness control. it is running really slow and I verified my config with the sanity checker and its all correct. can someone please help. I am attaching my oc folder.

       
      https://www.dropbox.com/s/drkek0eaz19ina5/OC.zip?dl=0
       
    • By y010204025
      Disclaimer: All files of this article are from itpwd.com and rehabman ’s github.com

       
      After Testing:
       
      Graphics card: NVIDIA K1000M / K2000M / K2100M / K3000M / K3100M / K4000M / M1000M (ordinary TN1600x900 or 1920x1080), AMD W5170M / W7170M (DC2 or 4K), Intel HD4000 (ordinary TN1600x900 or 1920x1080) can be driven normally, but NVIDIA graphics card Brightness adjustment is disabled. AMD W5170m and w7170m are the best choices on 8570W and 8770W. The brightness can be adjusted normally and the graphics performance is very good. For WX7100m and WX4170m, the graphics card fans cannot be controlled, and other methods are required to control the fans. CPU: 3rd generation Intel Core i3, i5 and i7 (Ivy Bridge architecture, including all dual-core and quad-core. Celeron and Pentium are not supported), frequency conversion is normal. In general: If you have 8570W, 8770W, and hope you can get the best Hackintosh experience, it is recommended to replace the CPU with i7-3840QM / i7-3940XM, 8570W is recommended to choose W5170M, 8770W, and it is recommended to choose W7170M. In addition: If you want to have a 4K experience or perfect HIDPI, W5170m / W7170M supports 4K output, you can choose a suitable 4K screen to replace, but because 4K screens are mostly edp interface, and 8570W / 8770W motherboard is lvds interface, This requires a custom screen cable, which seems to be a difficult choice, but you can choose to do it yourself or buy it separately. In China, taobao.com is almighty and may be more suitable for you than eBay.
       
      EFI features:
      out of the box, the relevant hardware can be driven after the OS is installed, and it is easy to use without code operation.
      Supported models: HP EliteBook 8470p, 8570p, 8570w, 8770w (click the model for official specifications)
      Wireless network card: Recommended: BCM94360cd (requires ipex4 to ipex1,3 antenna 1300mbps), BCM94352HMB / DW1550 (2 antennas, 867mbps)
      Wireless characteristics: no white list, wireless network card with Bluetooth does not support the Bluetooth function of the wireless network card (also does not need to shield the pins), but the wireless normal use, you need the Bluetooth function to use this machine comes with Bluetooth:
      Clover version: 5103, keyboard mapping has been added Command key = Alt key, Option key = Win key
      Supported systems: macOS Mojave 10.14.6 (18G103)-macOS Catalina 10.15.x,
       
      Notes on known issues:
      1. The touchpad and the left and right keys under the touchpad are normal, the pointing stick and the left and right keys above the touchpad are temporarily unavailable (recommended to use the second generation of Apple Magic Trackpad)
      2. Indicator display problem (can be ignored, function is normal): Caps light is sometimes not switched in time, mute / wireless key may be yellow
      3.AMD graphics card / Intel nuclear display has supported sleep and 15 levels of brightness adjustment, NVIDIA has no
      4. If the AMD graphics card enters Huaping, refer to editing the Clover startup parameters, and add the Boot parameter radpg = 15 (the EFI file that has been configured with this parameter has been uploaded, refer to the following EFI-guided download link)
      5. Using the above NVIDIA graphics card with a normal TN screen 1600x900 or 1920x1080 can not enter the installation interface, please check whether the VBiOS of the graphics card is exclusively for HP, thank you for your test face K1000M
      6. Due to product design defects, the MSata positions of 8570w and 8770w cannot be used as boot disks, so EFI boot can only be placed on the main hard disk (turn the machine over and open the hard disk in the lower left corner of the cover, which is the main hard disk). Put on msata plate
      +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
      Hardware requirements:
      Model: 8470p, 8570p, 8570W, 8770W 1 or more, it is recommended to use another notebook for emergency Hard disk: It is recommended to choose an SSD hard disk of 240g or more. Samsung or Intel SATA hard disk is a good choice. Wireless card: BCM94352HMB, DW1550, BCM94360CD, miniPCIe slot U disk: 1 for 16g and above, another winPE emergency USB disk is recommended If you use a rescue USB flash drive, it means that you read this post carefully
       
      Make and install a USB flash drive:
      Get the mirror: please do it your way Making and installing a USB flash drive: macOS command line production is recommended, whether it is a real macOS model or a virtual machine (although this is not allowed to be discussed in many forums)Or you can choose to use TransMac or ether under Windows. This is not recommended, but it is simple enough for those new to Hackintosh. Make boot U disk: If you know how to put the boot into the installation U disk, unzip the EFI file and put it in the EFI partition, or you can choose a fat32 format U disk to store the EFI file separately Note: EFI is an unzipped folder, not a zip or ISO suffix file.
       
      BIOS settings From RehabMan
      To start, set BIOS to defaults.
      Then insure:
      UEFI boot is enabled (hybrid/with CSM for best result) secure boot is disabled disable fast boot IGPU graphics memory set to 64mb, if available disable the serial port via BIOS option, if available disable "LAN/WLAN switching", if available disable "Extended Idle Power States" if you find it under "Power Management Options" disable "Wake on LAN" and "Wake on USB" disable Firewire/IEEE 1394, if your laptop has it for Skylake and KabyLake laptop, enable "Launch Hotkeys without Fn keypress" Note: If you have a laptop with switchable graphics, leave it enabled. You can still use it on Windows, although the discrete card will be disabled when running OS X by the ACPI patches provided here. If you want to also disable it in Windows (via BIOS option), make sure you read about the DGPU option in your model specific SSDT (source is in SSDT-HACK.dsl), as in the scenario where the DGPU is disabled by BIOS, DGPU should be set to zero.
       
      Install:
      Please modify according to the above BIOS settings: Press F9 after booting, select the boot efi to file option, which is generally the last item. Enter your boot USB disk to find the location of cloverx64.efi, select cloverx64.efi, press Enter, and enter the clover boot interface. Select the location of the install entry and press Enter. Enter the macOS interface, use the disk tool to format the partition you need to install to hfs + or apfs format, do not choose the encryption option, this will make your efforts in vain. Note: The disk must be in gpt format, and the remaining EFI space is greater than 200M, 300mb + is recommended. If it is not, please try to modify it in WindowsPE environment. This may cause you to lose the Windows system boot and disk data. Please prepare for backup.
      After formatting the partition successfully, close the disk tool and select install, you will find the partition you installed, and follow the interface prompts. When the installation reaches a certain progress, it will restart. When restarting, select F9, enter from the boot U disk, select the disk partition where you installed macOS (no longer the U disk installation), the installation will continue, and it may restart 2 ~ 3 times Every time, you need F9 to select the boot. After entering the installation interface, except for the first installation, select the U disk, and then select the disk installation partition. Eventually you will enter the settings interface. After following the interface prompts, you will enter the macOS system interface. Remember the system password and turn off the Find my mac option.  
      Post install:
       
      After the installation is complete, you need to hang the EFI partition of the disk, copy the EFI file of the U disk to the EFI partition of the disk, so that you can directly use the disk to boot, otherwise you need to select the U disk to boot each time. The mount tool can choose cloverconfigurator. If after copying the EFI file to the disk, the computer cannot recognize your clover boot, you can use the custom boot option of bios: set the custom boot path to \efi\clover\cloverx64.efi, and set it as the first boot, Use bootice or easyUEFI to increase the clover boot option under Windows and set it as the first boot. If you do not have a wireless network card available temporarily, you can use the USB binding function of your Android phone to share the network. This may require the HoRndis driver. It is not recommended to use a US wireless network card. If you need Windows or Linux, you can install it normally. Be careful not to let Windows overwrite your boot files.  
      For other uses of macOS and brew, please pay attention to forums and other communities. Hackintosh is just the beginning.
       
      Finally, I would like to thank rehabman, vit9696 and others who contributed to Hackintosh. I also thank Cwen for his efforts to modify files and hardware tests. I hope that Hackintosh will be eternal.
       
      Please comply with the laws and regulations of your country or region. My description may not be clear or professional, but I think it is necessary. I think the existence of Hackintosh is everyone's technical hobby and experience macOS, not as a substitute for macOS cheap hardware.

      EFI_8x70_5103_W7170m_20200116 .zip
    • By StarFighter_77
      I built this hack years ago now. Started with Lion, now on El Cap. I want to update now to High Sierra.

      I think I messed up my Clover when I downloaded the update .pkg and just installed it without taking my time or customizing the install. Was on Clover r3423, now I think I'm on r5104

      I've been searching and reading this site and others for a few days before making this thread, but I need help compiling what I've learned to get my system running correctly again and ready to update to High Sierra. Then, eventually, I want to update my graphics card, switch to UEFI (if necessary) and update to Mojave.

      I couldn't get system to boot. Could get to Clover and all the options, except the Shell... I hit enter on the Shell and I get black screen and nothing.

      The only way I got it to boot was to add -v to boot args, and change smbios from 14,2 to 13,2. Not sure why that worked still. Also I'm running two monitors, but I can only now run one of them off the Intel 3000 Graphics and the second one off my GFX Card.

      So now I'm afraid to shut down or reboot.... I could really use some help with Clover.

      I'm pretty sure my config file in Clover is not right. Also, some of the files in my Clover backups are not in the new Clover install. (2.5k 5104)

      If someone could please take a look at the files I've attached and help me sort this out, I would be grateful. Thank you, Thank you, Thank you.

      I've attached
      - The last boot log
      - The current Clover folder from the EFI partition after performing Clover update. (.zip)
      - The Clover backup that was working before Clover update (.zip)
      - Library/Extensions Folder (screen shot)
      - System/Library/Extensions Folder (.zip)

      Here is my current hardware:

      Mobo: GIGABYTE GA-Z68MX-UD2H-B3

      CPU: Intel Core i7-2600K

      GPU: GIGABYTE ATI Radeon HD6870 1GB DDR5 2DVI/HDMI/2x

      RAM: Corsair Vengeance Blue 16 GB DDR3 SDRAM Dual Channel Memory Kit CMZ16GX3M4A1600?C9B

      HD0 (for OS and Apps): OCZ Technology 120 GB Vertex Series SATA II Solid State Drive

      HD1 (file storage, Adobe scratch disk): Samsung 1 TB Spinpoint 7200 RPM 32MB Cache SATA

      BURNER: LG CD/DVD Burner Model GH22NS50

      CPU COOLER: Corsair Cooling Hydro Series H50 All in One High-performanc?e CPU Cooler CWCH50-1

      P/S: Antec CP-850 850 Watt CPX Power Supply Unit

      CASE: Antec Performance One P183 V3 Case
      CLOVER.zip
      CloverBackup.zip
      bootlog.txt

      S_L_E.zip
×