apianti Posted May 28, 2017 Share Posted May 28, 2017 I just said that so he would try and discover that most warnings are just warnings, like "don't look over the edge", but every one does that anyway - cause it's cool. Most of the warnings are actually in EDK, I try to fix the fixable ones in clover. As far as I remember there are few warnings that you can't get rid of with -Wall and they involve compiler defined macros not being defined (for the compiler not being used) and defaulting to zero. Apparently this is a problem, lol. I can't remember the others off the top of my head. Link to comment Share on other sites More sharing options...
bronxteck Posted May 28, 2017 Share Posted May 28, 2017 ok. if i build the existing local rev of clover. i do not get the warnings using micky's script but if i have the script pull edk and clover even though they are already at same revisions i get the warnings. i will attach a build log if you want to look at it. so maybe it is the script or edk. CloverCommandBuildLog.txt Link to comment Share on other sites More sharing options...
Slice Posted May 29, 2017 Share Posted May 29, 2017 ok. if i build the existing local rev of clover. i do not get the warnings using micky's script but if i have the script pull edk and clover even though they are already at same revisions i get the warnings. i will attach a build log if you want to look at it. so maybe it is the script or edk. Yes, there are numeroes warning building BaseTools. It is not our affair. EDK2 developers said also "there are not our sources, not our license so we keep them as is. They works and let it be". Link to comment Share on other sites More sharing options...
bronxteck Posted May 29, 2017 Share Posted May 29, 2017 thanks guy for clearing that up. Link to comment Share on other sites More sharing options...
Slice Posted May 30, 2017 Share Posted May 30, 2017 What is the reason to make custom NASM? Will it be better than official release? http://www.nasm.us/pub/nasm/releasebuilds/2.13.01/macosx/ 1 Link to comment Share on other sites More sharing options...
loganMac Posted May 31, 2017 Share Posted May 31, 2017 Question. My board is UEFI and Legacy. I plan to change bios to UEFI since I heard it's better and faster?? . On Clover setup, do I check both "Install for UEFI boot only" and "Install Clover in ESP"? Thanks Link to comment Share on other sites More sharing options...
apianti Posted May 31, 2017 Share Posted May 31, 2017 Yeah those are the options you would select. Remember you need to have a GPT formatted drive so if your drive is MBR, you'll need to basically reformat it. Also I would suggest using a fat formatted usb, installing to that without "Install Clover in ESP" and test booting UEFI with that, so you can still get into your current install. In that case the MBR formatting will be fine for the tests. 1 Link to comment Share on other sites More sharing options...
kosakgroove Posted June 3, 2017 Share Posted June 3, 2017 Hi guys i have a doubt .. I have spotted a cool bug regarding the boot logo of macOS.. While installing Sierra in my Lenovo L420 ( Macbook Pro 8,1 ) and El Capitan on my EP45-UD3LR ( Mac Pro 3,1) i noticed that my config plist did not have a Custom Logo setting and the boot logo was grey on grey like this I like it much better than the white on black logo that loads in my Asus X550LDV ( MacBook Pro 11,2 ) I tried all the different settings in the plist for the logo like Apple and Yes but nothing changes , the three of my hacks seem to render the white on black by default regardless of the setting, with the exception that in my Lenovo and EP45 the grey on grey loads on recovery hd and in install . Could you throw your two cents about this? Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
PMheart Posted June 3, 2017 Share Posted June 3, 2017 Hi guys i have a doubt .. I have spotted a cool bug regarding the boot logo of macOS.. While installing Sierra in my Lenovo L420 ( Macbook Pro 8,1 ) and El Capitan on my EP45-UD3LR ( Mac Pro 3,1) i noticed that my config plist did not have a Custom Logo setting and the boot logo was grey on grey like this I like it much better than the white on black logo that loads in my Asus X550LDV ( MacBook Pro 11,2 ) I tried all the different settings in the plist for the logo like Apple and Yes but nothing changes , the three of my hacks seem to render the white on black by default regardless of the setting, with the exception that in my Lenovo and EP45 the grey on grey loads on recovery hd and in install . Could you throw your two cents about this? Sent from my iPhone using Tapatalk Isn't this normal? boot.efi uses the legacy grey logo with white background on old SMBios, and the white logo with black background on new SMBios. And MP3,1 is obviously an "old" one, whereas MBP11,2 is relatively "newer". For now, as for MacPro series, only MacPro6,1 is showing the white logo with black backgd while booting. The way to determine the logos is that... Oops sorry I cannot remember it anymore, if I remember correctly, there should be an array for that. Link to comment Share on other sites More sharing options...
kosakgroove Posted June 3, 2017 Share Posted June 3, 2017 Isn't this normal? boot.efi uses the legacy grey logo with white background on old SMBios, and the white logo with black background on new SMBios. And MP3,1 is obviously an "old" one, whereas MBP11,2 is relatively "newer". For now, as for MacPro series, only MacPro6,1 is showing the white logo with black backgd while booting. The way to determine the logos is that... Oops sorry I cannot remember it anymore, if I remember correctly, there should be an array for that. What I find strange is that the grey on grey logo only loads when installing Mac OS X, once it is installed it loads the white on black, even on my "MacPro3,1" and "MacBook Pro 8,1" 1 Link to comment Share on other sites More sharing options...
cecekpawon Posted June 3, 2017 Share Posted June 3, 2017 You may continue my experiment http://www.insanelymac.com/forum/topic/321135-can-we-get-black-apple-logo-gray-background-on-boot/I already gave up 2 Link to comment Share on other sites More sharing options...
Philip Petev Posted June 3, 2017 Share Posted June 3, 2017 Guys, noticed a path to iasl in tools_def.txt, could you tell me is it really necessary, because haven't got any iasl-related build errors so far? Sent from my MI 5s using Tapatalk Link to comment Share on other sites More sharing options...
apianti Posted June 3, 2017 Share Posted June 3, 2017 It's there to build custom ACPI tables for putting into the built firmware roms (or just to have in a efi binary to install or something). I doubt it's ever used, I don't think there are any custom tables for Clover/DUET. EDIT: It's from EDK2, just in case you were wondering. 1 Link to comment Share on other sites More sharing options...
PMheart Posted June 4, 2017 Share Posted June 4, 2017 (edited) Hello, first of all sorry to bother you, I may be posting something irrelevant. As for kext injection, we should revert back to the old way, well, 10.13 is coming, and nobody knows what the kernel will look like, in case the patches still work then... Also, according to these comments, that's really somewhat not good. // // We can not rely on OSVersion global variable for OS version detection, // since in some cases it is not correct (install of ML from Lion, for example). // So, we'll use "brute-force" method - just try to patch. // Actually, we'll at least check that if we can find only one instance of code that // we are planning to patch. // So, we should revert back to use this "brute-force" method, like the attachment does. Alright, everything will be clear 2 days later. EDIT: Indenting. old_way_kext_inject.c.zip Edited June 4, 2017 by PMheart Link to comment Share on other sites More sharing options...
bs0d Posted June 4, 2017 Share Posted June 4, 2017 instead of guessing maybe just use the kernel version thats available ? 1 Link to comment Share on other sites More sharing options...
PMheart Posted June 4, 2017 Share Posted June 4, 2017 instead of guessing maybe just use the kernel version thats available ? Yes, let's wait. Link to comment Share on other sites More sharing options...
loganMac Posted June 5, 2017 Share Posted June 5, 2017 Hi, Is there a way to disable "Automatic boot in xx second" so that Clover loader menu still active even thought I don't click anything. In Clover Config, if I put "0" second, Clover will not show other OS selection. It will just go straight to whatever OS last used. Currently I set to 25 second. Link to comment Share on other sites More sharing options...
D-an-W Posted June 5, 2017 Share Posted June 5, 2017 Set it to -1 instead of 0 1 Link to comment Share on other sites More sharing options...
loganMac Posted June 5, 2017 Share Posted June 5, 2017 Set it to -1 instead of 0 Thank you. Will try that tonight. Link to comment Share on other sites More sharing options...
PMheart Posted June 5, 2017 Share Posted June 5, 2017 CONFUSING CONTENTS REMOVED, SORRY FOR THE INCONVENIENCE 15 Link to comment Share on other sites More sharing options...
blayze® Posted June 5, 2017 Share Posted June 5, 2017 Can you release it compiled Link to comment Share on other sites More sharing options...
PMheart Posted June 5, 2017 Share Posted June 5, 2017 Can you release it compiled Yep, a fair bit later, currently compiling Can you release it compiled Hi, updated, please test and feedback! (http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2435840) 2 Link to comment Share on other sites More sharing options...
vandroiy2012 Posted June 5, 2017 Share Posted June 5, 2017 [uPDATE 2] Added pre-compiled binaries of Clover. clover_r4079_patch_1013_test.zip Also, don't forget to add APFS driver! If you don't have one, you may download it from here. No kext injection with this version at all 2 Link to comment Share on other sites More sharing options...
PMheart Posted June 5, 2017 Share Posted June 5, 2017 No kext injection with this version at all Unfortunately, could you please to show some logs of debug? (Set KextAndKernelPatches -> Debug = true) Link to comment Share on other sites More sharing options...
bronxteck Posted June 5, 2017 Share Posted June 5, 2017 i got cpu kp on haswell booting 10.13, could not boot back into sierra probably graphics kext injection issue Link to comment Share on other sites More sharing options...
Recommended Posts