Clover General discussion

[loganMac]

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

[apianti]

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.

[kosakgroove]

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

[PMheart]

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.

[kosakgroove]

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"

[cecekpawon]

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

[Philip Petev]

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

[apianti]

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.

[PMheart]

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

[bs0d]

instead of guessing maybe just use the kernel version thats available ?

[PMheart]

instead of guessing maybe just use the kernel version thats available ?

Yes, let's wait.

[loganMac]

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.

 

 

[D-an-W]

Set it to -1 instead of 0

[loganMac]

Set it to -1 instead of 0

 

Thank you.  Will try that tonight.

[PMheart]

CONFUSING CONTENTS REMOVED, SORRY FOR THE INCONVENIENCE

[blayze®]

Can you release it compiled

[PMheart]

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)

[vandroiy2012]

 

[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

[PMheart]

 

 

No kext injection with this version at all

 

Unfortunately, could you please to show some logs of debug? (Set KextAndKernelPatches -> Debug = true)

[bronxteck]

i got cpu kp on haswell booting 10.13,

could not boot back into sierra probably graphics kext injection issue

[vandroiy2012]

Unfortunately, could you please to show some logs of debug? (Set KextAndKernelPatches -> Debug = true)

 

Sorry. But where can i find this log? EFI/Clover/Misc is empty...

[mhaeuser]

Unfortunately, could you please to show some logs of debug? (Set KextAndKernelPatches -> Debug = true)

Verified both of your patches against TheRacerMaster's kernel, they are fine... either they added some other security ****, or the issue is not kext injection. They also might have accidentially broken it as the code is not used in any non-OSx86 scenario.

 

EDIT: Was just told by a guy that he sees FakeSMC init messages, though boot still doesn't succeed. No message about DSMOS.

EDIT2: Am I wrong guessing there is no supported Mac with a PMIO SMC?

EDIT3: AppleSMC.kext still has and calls PMIO functions... phew, no clue now.

EDIT4: So yeah... might the issue just be the revert to the 'old way', i.e. that and old patch is applied to the new kernel?

[TheRacerMaster]

I had to change #if 0 to #if 1 in order for injection to work on 10.12.5... I can't get 10.13 to boot just yet, panics with AppleACPIPlatform.

[mhaeuser]

panics with AppleACPIPlatform.

Have you disabled all Clover DSDT patches?

[Riley Freeman]

Unfortunately, could you please to show some logs of debug? (Set KextAndKernelPatches -> Debug = true)

 

IIRC there won't be a log file written with this, so here's some screengrabs from Debug = True

 

I booted into El Capitan and Sierra with 4077 and Debug = True enabled and both show 2 kernel patches being applied to enable kext injection whereas here there's only 1.