Clover General discussion

[Matgen84]

2 minutes ago, corint1 said:

sorry, but is same ...only preboot and data partitions are showing ... 

 

Clover don't boot Big Sur data partition  because this bootloader detects only bootable partition  I don't think data partition, is bootable.

Upload your EFI Folder, please.

[corint1]

11 minutes ago, Matgen84 said:

 

Clover don't boot Big Sur data partition  because this bootloader detects only bootable partition  I don't think data partition, is bootable.

Upload your EFI Folder, please.

I have no problem with the two partitions, date or preboot ... the recovery partition is not displayed ... with this I have the problem
 

 

here my EFI folder ... https://mab.to/Ayo44id2c

[Matgen84]

21 minutes ago, corint1 said:

I have no problem with the two partitions, date or preboot ... the recovery partition is not displayed ... with this I have the problem
 

 

here my EFI folder ... https://mab.to/Ayo44id2c

 

Update yours kexts to the latest Release. Disable all DSDT patches in your config.plist.

Modify to the new standard config.plist (sample.plist):

Warning: Unknown key '/KernelAndKextPatches/KernelCpu:316'. Skipped.
Warning: Unknown key '/Quirks/PanicNoKextDump:386'. Skipped.
Warning: Unknown key '/Quirks/LapicKernelPanic:388'. Skipped.
Warning: Unknown key '/Quirks/DisableRtcChecksum:414'. Skipped.
Warning: Unknown key '/Quirks/AppleXcpmCfgLock:428'. Skipped.
Warning: Unknown key '/Quirks/CustomSMBIOSGuid:436'. Skipped.
Warning: Unknown key '/Quirks/AppleCpuPmCfgLock:450'. Skipped.

Update BOOTX64.efi by renaming a copy of latest CLOVERX64.efi

After, I do not know what to do.

 

Maybe a debug.log and a screenshot, if the problem persists others can help. I think you have to check your config.plist closely. A topic has been created on the forum.

Edited December 9, 2020 by Matgen84

[corint1]

40 minutes ago, Matgen84 said:

 

Update yours kexts to the latest Release. Disable all DSDT patches in your config.plist.

Modify to the new standard config.plist (sample.plist):

Warning: Unknown key '/KernelAndKextPatches/KernelCpu:316'. Skipped.
Warning: Unknown key '/Quirks/PanicNoKextDump:386'. Skipped.
Warning: Unknown key '/Quirks/LapicKernelPanic:388'. Skipped.
Warning: Unknown key '/Quirks/DisableRtcChecksum:414'. Skipped.
Warning: Unknown key '/Quirks/AppleXcpmCfgLock:428'. Skipped.
Warning: Unknown key '/Quirks/CustomSMBIOSGuid:436'. Skipped.
Warning: Unknown key '/Quirks/AppleCpuPmCfgLock:450'. Skipped.

Update BOOTX64.efi by renaming a copy of latest CLOVERX64.efi

After, I do not know what to do.

 

Maybe a debug.log and a screenshot, if the problem persists others can help. I think you have to check your config.plist closely. A topic has been created on the forum.

it's not a problem of config.plist or kexts ... these will load after selecting the partition ... or I don't see the recovery partition ... which is at least one step before reading config or loading kexts
 

edit:

trying the one you suggested to me, it doesn't even boot anymore ... the elimination of the one you proposed leads to KP of all beauty ...
 

Edited December 9, 2020 by corint1

[iCanaro]

remove HFSPlus.efi and place VboxHfs.efi in its place
in the config GUI Hide delete preboot 
in my opinion however you have configuration still to be developed, without any DSDT, just the SSDTs

https://dortania.github.io/Getting-Started-With-ACPI/ssdt-methods/ssdt-prebuilt.html#desktop-coffee-lake

 

even when you see the recovery partition clover currently fails to start it

the version of clover that I downloaded, as well as renaming it to CLOVERx64.efi you have to duplicate it and rename it to BOOTX64.efi and put it in the BOOT folder

 

system all the errors matgen84 reported to you

[corint1]

3 hours ago, Alpha999 said:

Hello corint1

Based on the EFI folder you sent, I put in the latest commit for Clover 5127.
Then, I added an aml file that should be included in Coffee lake to acpi / patched and added it. (According to Dortania)
Kext has been updated as much as possible.

My computer is also Coffeelake and the chipset is 300 series, so I replaced the my SMBIOS  and booted. There, Big Sur, Catalina was able to boot.

 

First, the Recovery entry was displayed, as you can see in the screenshot on misc folder. (I commented out GUI-HIDE and displayed it all)
The following is the fixed folder.

 

corint1.EFI.2012101004.zip

(SMBIOS has been restored to yours.)

I am on behalf of Mifjpn. Thank you for using his Minimalism 2-2.
By the way, he issued Minmalism3-1, so I replaced it.

 

Just include USBInjectAll.kext and there is no 15 port limit or patch to remove the port limit. How did you use USB? I'm wondering.

Also, USBInjectAll was included, but I think it is more convenient to make a USBPort.kext I recommend making it.

 

https://www.tonymacx86.com/threads/the-new-beginners-guide-to-usb-port-configuration.286553/

 

thanks ... indeed with the folder you sent, the recovery partition appears, but it can't boot from it ... the changes you made did neither good nor bad, in the sense that I didn't notice anything new ... maybe fewer ACPI errors at boot ... the limit of the usb ports is not a priority for me ... it works with more than 15 ... and the cosmeica doesn't bring anything improved ...
 

[MacKonsti]

On 12/9/2020 at 6:11 PM, Matgen84 said:

I just compiled r5127 the last commit 4af8a02: the recovery partition is displayed as since the commits of November 28. On the other hand, I hid the main partition to leave only the preboot. See the screenshot (the BS icon on the left is the USB key, beside Recovery there is BigSur's Preboot icon).

Hi @Jief_Machak and @Slice and any other major contributor to Clover that I may forget.

 

For us end-users that rely on Git releases (pre-compiled) as we may not have the means/time/knowledge to keep building Clover continuously like some courageous people here (like @iCanaro et al).

 

Can I consider r5127 as not really ready for prime-time or stable?

 

I want to update my Catalina booter from r5123-1 to r5127 and I am hesitant with all the things I read and possibly (not) understand (yet).

 

Perhaps in the next days I will use a second spare drive to install Big Sur and see how it boots etc.

 

So in your view, do we need to better expect a r5128 release that will be more polished and without (major or not) well known bugs?

 

Just to understand and appreciate the release cycles.

 

Thanks again for your commitment and contributions! Warm regards.

Edited December 11, 2020 by MacKonsti

[iCanaro]

to call myself courageous is a little exaggerated; perhaps many do not realize the powerful means that Jief has provided us with, namely BootLoderChooser (BLC) through which you can use 2 CONFIGURATIONS of CLOVER in the same EFI, (CLOVER + CLOVERTEST) and also have bootable, also in the same EFI, OpenCore.
What this translates, that you can start normally with the Clover stable and have another one for testing and development, without using pendrive and wasting time.

[Matgen84]

@MacKonsti If you have some difficulty to convert old Clover to new Clover config.plist. It is necessary to use r5127+

 

Please take a look to this topic:

You can also use BootLoader Chooser as @iCanaro says (only if you compile Clover yourself or want testing a new release). 
 

The Clover r5127 can boot Big Sur, like a charm except that Recovery partition is detected but not bootable yet from GUI. If I remember well : @iCanaro has an Z97+4790k Hack. If you have some problems to convert your config.plist... 

Edited December 11, 2020 by Matgen84

[MacKonsti]

Thanks guys both of you @iCanaro and @matgen84 (merci) my question was more about the release and pre-compiled builds found on Git that are available to download.

As there's a lot of discussions here and obviously open issues, I was wondering if r5127 is ready for real wider use or if there's still work needed, as it was released not far after r5126.

Just to be sure if it's work investing time trying out r5127 or rather wait for possibly r5128 before Christmas time...

I mean, just to know about how confident the lead developers are about r5127 features and stability. I do not have time, unfortunately, to test and build releases, at this moment.
Thanks again, everyone.

[Slice]

@MacKonsti

You may wait infinitely. We will publish new releases and users will found new bugs. It is endless process.

Yes, release 5127 can be account as final.

[MacKonsti]

Thanks @Slice ! Of course it will be endless as new macOS may show the need for new stuff to add, besides bugs found, reported and solved.

 

Just that the original r5123 had this bug where on my hack, device (H_EC) could not be renamed (if you remember) that was a regression of sorts and no one reported, a bug serious enough to make us look for a solution in a totally different direction as we wouldn't guess it immediately.

 

So if r5127 was tested enough and doesn't have unknown regressions, that is good news, thanks for your feedback, appreciate it.

[Slice]

16 hours ago, MacKonsti said:

Thanks @Slice ! Of course it will be endless as new macOS may show the need for new stuff to add, besides bugs found, reported and solved.

 

Just that the original r5123 had this bug where on my hack, device (H_EC) could not be renamed (if you remember) that was a regression of sorts and no one reported, a bug serious enough to make us look for a solution in a totally different direction as we wouldn't guess it immediately.

 

So if r5127 was tested enough and doesn't have unknown regressions, that is good news, thanks for your feedback, appreciate it.

Sorry I didn't remember if you ever reported this and I know you usually didn't provide any logs. But the renaming are working and this is my config.plist that works at this moment on my computer #1 booting to Mojave or BigSur with Clover 5127.

 

[MacKonsti]

Hi @Slice I may have not expanded on my point there, I meant "rename a device with TargetBridge set". I did create it of course officially: https://github.com/CloverHackyColor/CloverBootloader/issues/252

It was @Jief_Machak who confirmed this bug few pages ago and kindly provided a r5123-1 release (pre-OpenCore) for non-BigSur systems that wanna keep old-style.

It doesn't matter anyway, the community and yourself as top dev always read our comments/issues and assist. Thanks again, I managed last night to update to r5127 and used Quirks for my Comet Lake in config.plist by comparing line-by-line the ones suggested on Dortania guides.

Seems it booted without problems to my Catalina hack.

 

Please, a last piece of advice from you that I kindly request:

a) what do you call that "matrix-style" screen before OS booting step? The preboot screen? what is the name (after we select drive) please?

b) I see a couple of "EB:ERR" flash quickly... How to understand these, are they errors? Can you kindly point me to some guide/manual/thread? I've been searching for a week but without correct search keywords, can't find much.

 

Спасибо. Сезонное поздравление!

Edited December 12, 2020 by MacKonsti

[Slice]

a) This "matrix-style screen appeared because of OC integration. It means nothing and has no name. Close your eyes and count up to ten.

b) There are errors just like there is an error to install macOS on ordinary PC. Hackintosh is an error itself.

[deeveedee]

12 hours ago, Alpha999 said:

Hello everyone.
Searching the web doesn't hit many pages on how to migrate to an OpenCore integrated Clover

 

 @Matgen84 's suggested thread here works well for me, too.

 

 

4 hours ago, Slice said:

b) There are errors just like there is an error to install macOS on ordinary PC. Hackintosh is an error itself.

 

There are errors installing Windows on an ordinary PC

Edited December 12, 2020 by tonyx86

[ameenjuz]

i have clean installed Big Sur 11.0.1 successfully puting CsrActiveConfig =0x877

now i m able to boot preboot volume & Big Sur volume

but i couldn't hide preboot volume 

anyone guide me how to hide preboot volume from boot menu

Spoiler

Spoiler

 

[Matgen84]

@ameenjuz Don't hide Preboot volume because Clover boot Big Sur from Preboot by default. You can hide main partition instead.

The screenshot show Catalina preboot !

Edited December 12, 2020 by Matgen84

[JorgeMax]

 

29 minutos atrás, ameenjuz disse:

 

  Ocultar conteúdo

 

 

Where do I download this theme friend?

[ameenjuz]

1 hour ago, Matgen84 said:

@ameenjuz Don't hide Preboot volume because Clover boot Big Sur from Preboot by default. You can hide main partition instead.

The screenshot show Catalina preboot !

i know my dear i m able to boot big sur do not need i have two partitions installed big sur this is not catalina because i renamed one partition to named catalina just for remmember

i m able to boot from preboot and bigsur  just in case i want to hide preboot volumes

1 hour ago, JorgeMax said:

 

 

 

Where do I download this theme friend?

attached thems

 

clover-theme-oss.zip

[MacKonsti]

11 hours ago, Slice said:

a) This "matrix-style screen appeared because of OC integration. It means nothing and has no name. Close your eyes and count up to ten.

b) There are errors just like there is an error to install macOS on ordinary PC. Hackintosh is an error itself.

 

Thank you, I am just eager to understand. I don't do -v verbose usually, just created an "emergency" USB flash disk with r5127 and saw it. Just wondering what is called and what boot stage it represents...

 

1) OK please you are the only person who can confirm if r5127 now includes Quirk DisableRtcChecksum because in your older post you exclude it in some way, but I found an entry in the CLOVERX64.efi binary and in config sample of the release ZIP...

 

Do we include this quirk in the config.plist now?

 

2) Also, I am sorry to report that in my almost perfectly working Catalina on Intel NUC8, updating from r5123-1 to r5127 breaks wake-from-sleep really bad. With no other changes (except Quirks added in config.plist) the NUC upon wake shows the BIOS boot screen instead and goes to that error screen (Apple's forbidden logo with text) ; I don't see CMOS being reset, but have no idea how to fix it or where to start from. Deleting references to /Library/Preferences/com.apple.PowerMagement* doesn't solve it.

 

Any ideas if a Quirk might be responsible for sleep? Kexts, config remained the same to r5123-1.... Thanks

 

Update: Here is what I can provide by running the pmset command; could this be related to wrong quirks? Now under "Energy Saver" in System preferences I have less options to choose from (e.g. no Power Nap)

% pmset -g log | grep -i failure
2020-12-12 15:04:51 +0200 Failure             	Failure during wake: 0x00000023 : Failure while halting boot CPU panic
2020-12-12 18:51:47 +0200 Failure             	Failure during wake: 0x00000023 : Failure while halting boot CPU panic
2020-12-12 19:15:05 +0200 Failure             	Failure during wake: 0x00000021 : Failure while halting non-boot CPUs panic
2020-12-12 19:21:45 +0200 Failure             	Failure during wake: 0x00000021 : Failure while halting non-boot CPUs panic
2020-12-12 20:25:19 +0200 Failure             	Failure during wake: 0x00000021 : Failure while halting non-boot CPUs panic
2020-12-12 20:33:31 +0200 Failure             	Failure during wake: 0x00000023 : Failure while halting boot CPU panic
2020-12-12 20:59:49 +0200 Failure             	Failure during wake: 0x00000023 : Failure while halting boot CPU panic
2020-12-12 23:02:56 +0200 Failure             	Failure during wake: 0x00000023 : Failure while halting boot CPU panic

 

Edited December 12, 2020 by MacKonsti

[deeveedee]

@MacKonsti I admire your tenacity.  I'm still on r5122 / Catalina as my main rig's baseline. At the risk of angering everyone in this thread and appearing ignorant because I missed this in one of your previous posts, have you tried booting OC to confirm your Quirks?  It's the strategy that I've opted to employ. I prefer and am most comfortable with CLOVER and am currently running OC 0.6.3 in a test environment so I can learn the Quirks and possible other related settings.

 

What I've found with OC is that it is requiring me to understand more about my rig and its configuration than I needed to understand with CLOVER.  I think this is a good thing and definitely can't hurt.

 

EDIT: @MacKonsti This is some good reading.

Edited December 13, 2020 by tonyx86

[Slice]

@MacKonsti

As Alpha999 told the Clovers setting "AppleRTC" do the same as OC "DisableRtcChecksum".

Sorry that DisableRtcChecksum is still present in config-sample.plist. It will be excluded in next release.

Use AppleRTC

[MacKonsti]

5 hours ago, Slice said:

As Alpha999 told the Clovers setting "AppleRTC" do the same as OC "DisableRtcChecksum".

Sorry that DisableRtcChecksum is still present in config-sample.plist. It will be excluded in next release.

Use AppleRTC

 

Hi everyone, thanks for your replies and ideas. I am sorry if my posts are sometimes longer but I tend to report here as I do in my professional work (IT) trying to be precise and verbose so I can help.

 

1. Thanks @Slice for confirming that DisableRtcChecksum is not part of Quirks and CLOVERX64.EFI won't take read/consider it. I did mention your older post where you point to AppleALC instead.

But inside CLOVERX64.EFI binary, I see text references that puzzled me, hence why I asked: "OCAK: Failed to apply patch com.apple.driver.AppleRTC DisableRtcChecksum" and "OCAK: Patch success com.apple.driver.AppleRTC DisableRtcChecksum"

That is why I was not sure if DisableRtcChecksum is an accepted parameter...

 

2. Thanks @Alpha999 and @tonyx86 but as I mentioned, my Quirks are based for Comet Lake and I boot just fine. I compared line-by-line the Quirks from Dortania AND those generated by OC-Gen-X application.

I am not using AppleALC (=false) nor DisableRtcChecksum (=false) at all.

But I have a obvious KP when I wake from sleep with Clover r5127 that I do not have with r5123-1 !

 

With the SAME exact SSDTs (AML) and Kexts loaded, same config.plist (including SMBIOS) I have different behaviour. I just added Quirks to replace AptioMemoryFix.efi...

I discovered that with Clover r5127 even "Energy Saver" now shows LESS parameters than r5123-1 without any config changes:

• Wake for Ethernet network access = missing (not enabled)
• Start up automatically after power failure = missing (that I enable since years go)
• Enable Power Nap = missing (not enabled)

Therefore my question is : What changed with r5127 and Quirks that is not the same behaviour as AptioMemoryFix.efi with r5123 with regards to sleep-wake Kernel Panics?

 

I did consider creating OpenCore bootable USB and see how it behaves but that means I will be migrating to OC if wake works, and was hoping to keep use Clover for some time...

Thanks, here's my CONFIG without S/N etc. thanks for having a look and see which Quirk may cause the wake KP and is related to sleep/wake...

Stay safe.

konsti-nuc8i7beh-config-r5127.plist

[deeveedee]

11 minutes ago, MacKonsti said:

I did consider creating OpenCore bootable USB and see how it behaves but that means I will be migrating to OC if wake works, and was hoping to keep use Clover for some time...

Migrate to OpenCore?  Blasphemy!