LockDown Posted October 22, 2015 Share Posted October 22, 2015 Thank You TheRaceMaster Not a bug, it's a new feature. When Clover loads you can briefly see the "Welcome to Clover revision xxxx" text (and some others I think, but these are very quick and not very noticeable). With RehabMan's additions (r3296) you can now add NoEarlyProgress=FALSE in config.plist/GUI and it'll hide these messages while loading Clover. One thing though... Default false, but set to true, will eliminate these messages and result in a cleaner startup. NoEarlyProgress=TRUE will hide it Link to comment Share on other sites More sharing options...
Slice Posted October 22, 2015 Share Posted October 22, 2015 The feature that we are going to hide now was introduced to eliminate a number of messages "Clover is not working. Black screen!". So for novices there will be messages. Advanced users can hide the messages. It will not be default. 1 Link to comment Share on other sites More sharing options...
luxinhaus Posted October 22, 2015 Share Posted October 22, 2015 Hi Slice Im compiling Clover manually. can you confirm if: cp -R Clover/Patches_for_EDK2/* ./ still needed? Link to comment Share on other sites More sharing options...
magnifico Posted October 22, 2015 Share Posted October 22, 2015 Sergey , today i see 3297 on clover grower pro . Now try On 3297 ..no work ...i see again welcome on clover <key>GUI</key> <dict> <key>NoEarlyProgress</key> <string>Yes</string> </dict> Link to comment Share on other sites More sharing options...
Slice Posted October 22, 2015 Share Posted October 22, 2015 Hi Slice Im compiling Clover manually. can you confirm if: cp -R Clover/Patches_for_EDK2/* ./ still needed? Obligatory else you can't compile. Sergey , today i see 3297 on clover grower pro . Now try On 3297 ..no work ...i see again welcome on clover <key>GUI</key> <dict> <key>NoEarlyProgress</key> <string>Yes</string> </dict> I didn't revise this patch. Seems to be wrong. Link to comment Share on other sites More sharing options...
magnifico Posted October 22, 2015 Share Posted October 22, 2015 I didn't revise this patch. Seems to be wrong. I did not understand, you're saying that my mistake to make the flag? Link to comment Share on other sites More sharing options...
RehabMan Posted October 22, 2015 Share Posted October 22, 2015 Sergey , today i see 3297 on clover grower pro . Now try On 3297 ..no work ...i see again welcome on clover Post the config.plist you're using. I didn't revise this patch. Seems to be wrong. It is working fine here (with my edits)... I will test the repo as checked in by Slice. It is working fine here (with my edits)... I will test the repo as checked in by Slice. Typo in post #165 (fixed). Key is config.plist/Boot/NoEarlyProgress=true. Sorry for any confusion/inconvenience. Link to comment Share on other sites More sharing options...
magnifico Posted October 22, 2015 Share Posted October 22, 2015 Post the config.plist you're using. It is working fine here (with my edits)... I will test the repo as checked in by Slice. Typo in post #165 (fixed). Key is config.plist/Boot/NoEarlyProgress=true. Rehab ..in the Boot or Gui ?? Link to comment Share on other sites More sharing options...
RehabMan Posted October 22, 2015 Share Posted October 22, 2015 Rehab ..in the Boot or Gui ?? The config.plist is wrong. You have config.plist/Boot/NoEarlyProgress.=true. Must be config.plist/Boot/NoEarlyProgress=true. There is no period at the end of the NoEarlyProgress key. Seems as if I already pointed this out yesterday... Edit: Yes... I did point this out yesterday... see post #169 and #170: http://www.insanelymac.com/forum/topic/306156-clover-bugissue-report-and-patch/page-9?do=findComment&comment=2180531 1 Link to comment Share on other sites More sharing options...
magnifico Posted October 22, 2015 Share Posted October 22, 2015 The config.plist is wrong. You have config.plist/Boot/NoEarlyProgress.=true. Must be config.plist/Boot/NoEarlyProgress=true. There is no period at the end of the NoEarlyProgress key. Seems as if I already pointed this out yesterday... I made a typo, and I put a point ... Sorry was my distraction now works fine Thanks Rehab PS: you edited the post 165, because yesterday I read GUI 1 Link to comment Share on other sites More sharing options...
Slice Posted October 23, 2015 Share Posted October 23, 2015 What about 10.9 which is also 64 bit? Link to comment Share on other sites More sharing options...
luxinhaus Posted October 26, 2015 Share Posted October 26, 2015 @Slice, a follow up question. Its been a while since i compiled clover. Do we need to execute this whenever we downgrade/update EDK2? cp -R Clover/Patches_for_EDK2/* ./ Link to comment Share on other sites More sharing options...
Slice Posted October 26, 2015 Share Posted October 26, 2015 @Slice, a follow up question. Its been a while since i compiled clover. Do we need to execute this whenever we downgrade/update EDK2? cp -R Clover/Patches_for_EDK2/* ./ Yes, obligatory. Link to comment Share on other sites More sharing options...
Slice Posted October 27, 2015 Share Posted October 27, 2015 I reverted *.po files because pootle send wrong versions. JrCs, where you are? Link to comment Share on other sites More sharing options...
dgsga Posted October 29, 2015 Share Posted October 29, 2015 Hi Slice, thanks very much for all your work on making changes for clang 3.8 compilation. I can compile successfully but the resulting binary doesn't load. Have you found the same thing?? Link to comment Share on other sites More sharing options...
Slice Posted October 29, 2015 Share Posted October 29, 2015 Yes, same. Clang is still not able to create working efildr20 (boot file) although CloverX64.efi is working. As well as Shell.efi and mostly all other modules. I found some problems is past and corrected that I known: - optimisation with memcpy must be disabled - avoid absolute addresses, including asm files used in modules - clang before 3.7 was not understanding _ms_va_args. Now can. It seems there are other caveats... Link to comment Share on other sites More sharing options...
Ikky Phoenix Posted November 5, 2015 Share Posted November 5, 2015 Hi, I have a problem trying to boot my notebook (Core 2 Duo) with Clover and 8GB of ram. With 6GB it works. So i took two debug log files. If i try to boot with chameleon (enoch), it works fine. Can anyone help me? debugs.zip Link to comment Share on other sites More sharing options...
bomerr Posted November 6, 2015 Share Posted November 6, 2015 I am having an issue with my RAM being incorrectly reported. I have 16GB installed but the system only reports 8GB. DarwinDumper_2.9.9_AMI_X64_3320_Cap.zip Link to comment Share on other sites More sharing options...
Slice Posted November 6, 2015 Share Posted November 6, 2015 I am having an issue with my RAM being incorrectly reported. I have 16GB installed but the system only reports 8GB. 0:284 0:000 Sorry, DDR4 is not fully implemented! Use settings in config.plist Add the follow into config <key>SMBIOS</key> <dict> <key>Trust</key> <true/> Link to comment Share on other sites More sharing options...
bomerr Posted November 6, 2015 Share Posted November 6, 2015 0:284 0:000 Sorry, DDR4 is not fully implemented! Use settings in config.plist Add the follow into config <key>SMBIOS</key> <dict> <key>Trust</key> <true/> No effect. Link to comment Share on other sites More sharing options...
TheRacerMaster Posted November 6, 2015 Share Posted November 6, 2015 No effect. You might have to manually add Memory entries under config.plist/SMBIOS. Link to comment Share on other sites More sharing options...
Slice Posted November 6, 2015 Share Posted November 6, 2015 No effect. A proof? Link to comment Share on other sites More sharing options...
LockDown Posted November 10, 2015 Share Posted November 10, 2015 hello... What is the "minimum" Xcode version to build clover? Link to comment Share on other sites More sharing options...
Slice Posted November 10, 2015 Share Posted November 10, 2015 hello... What is the "minimum" Xcode version to build clover? I don't remember about 3.3 but XCode 4.4.1 is really enough. Link to comment Share on other sites More sharing options...
LockDown Posted November 10, 2015 Share Posted November 10, 2015 I don't remember about 3.3 but XCode 4.4.1 is really enough. 4.6.3 worked great. no errors/warnings compared to 7.x Thanks Link to comment Share on other sites More sharing options...
Recommended Posts