Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

Clover Problem boot partition BG_b10

 

clover boot beta 10 disk Preboot !

 

print 

 

boot kernel panic 

Spoiler

1505076541_bootpartitionBGbeta10Nobootkernelpanic.thumb.jpg.71f83833f7aad0e998f45c83bf7c1149.jpg

Spoiler

 

 

Krenel panic 

Spoiler

IMG_20201015_175308.thumb.jpg.cb55166505c69902f4a88771d0fdd8a3.jpg

 

boot bigsur beta 10 OK Clover r5124 (disk Preboot)

Spoiler

758478635_bootbeta10OKwork.thumb.jpg.6fefe56d4a411c71466a5144448613f7.jpg

 

 

 

 

 

Divulgacher

system Clover r5124 ok boot = Pré-démarrageIMG_20201015_175148.thumb.jpg.d8cd252ed011ece318e3cd4ebd41d7ce.jpg

 

 

  • Haha 1
Link to comment
Share on other sites

1 hour ago, PG7 said:

Clover Problem boot partition BG_b10

 

clover boot beta 10 disk Preboot !

 

print 

 

boot kernel panic 

  Hide contents

1505076541_bootpartitionBGbeta10Nobootkernelpanic.thumb.jpg.71f83833f7aad0e998f45c83bf7c1149.jpg

  Hide contents

 

 

Krenel panic 

  Hide contents

IMG_20201015_175308.thumb.jpg.cb55166505c69902f4a88771d0fdd8a3.jpg

 

boot bigsur beta 10 OK Clover r5124 (disk Preboot)

  Hide contents

758478635_bootbeta10OKwork.thumb.jpg.6fefe56d4a411c71466a5144448613f7.jpg

 

 

 

 

 

  Hide contents

system Clover r5124 ok boot = Pré-démarrageIMG_20201015_175148.thumb.jpg.d8cd252ed011ece318e3cd4ebd41d7ce.jpg

 

 

Just like me

Spoiler

1433483497_ScreenShot2563-10-16at04_26_43.png.62d3292ae3ad6e44453d3d62de300ca5.png

 

Edited by naiclub
  • Like 1
  • Thanks 1
Link to comment
Share on other sites

Hmmb, it's bit weird that I'm still unable to load Clover on my Legacy mach (GPT Scheme with 200MB ESP) since r5123. It just got stuck at boot6 / boot7. I've also tried using boot binaries from prev releases with same results, either re-erased my EFI partition several times then manually installing it using 'dd' under Linux following m13253's script (not using any macOS #atm). debug=true didn't help either, it gave me no log at all. Or, do I need using OpenCore legacy method for this? Thanks.

  • Like 1
Link to comment
Share on other sites

1 hour ago, Badruzeus said:

Hmmb, it's bit weird that I'm still unable to load Clover on my Legacy mach (GPT Scheme with 200MB ESP) since r5123.

 

Yeah, it looks like the OC integration process has resulted in bad legacy boot files (boot6, boot7) that hang the boot process before reaching the Clover GUI.

 

Attached is the latest Clover_r5124_ 62e6f8ddd (with good boot6 from r5058) that you can manually install after mounting the EFI System Partition.

 

Some tips for converting over from old Clover r5122 to new ones with OC 0.6.1 integration in this post.

 

Works for both my legacy systems (System2, System3 in signature), booting OSX 10.6.8 to macOS Big Sur Beta10 (USB installer and already installed system).

 

Also tested on my Skylake NUC6i5SYH to successfully update Big Sur Beta6--->Beta10 on an external USB HD (running the full installer app in Beta6...link to Beta10 InstallAssistant.pkg (11.4GB size))

 

Spoiler

1742472991_B10update3.png.cc4e3eb17e8217ddca55c829283edb4e.pngReboot1_1.thumb.png.23f487c2184021b1b8634a01d8afe3b3.pngReboot2.thumb.png.145d84b5680863b311821384a3e7c46e.pngReboot3_1.thumb.png.1e4887186f27f2681d856cc9a95dce6b.pngReboot3_2.thumb.png.a0313340df3285cc3bc7b1258e3da2a2.png1396049986_NUC6i5SYHupdateinstallwithfullB10installerusingClover_r5124.thumb.png.cda1fe6adf44c4185ea1d9862b2781c3.png

 

 

PS - Can confirm delta OTA update is still offered through System Preferences/Software Update when you boot to older Big Sur beta through its Preboot volume eg boot to Beta6 via Preboot ---> offered Beta10 upgrade of 4.56GB...

 

Spoiler

878167467_NUC6i5SYHdeltaupdateB6toB10viaCloverr5124.thumb.png.637e169f4c11b99decce18af3774168c.png

  • SIP partially disabled with config.plist/RtVariables/CsrActiveConfig=0x67 to enable third party USB wifi
  • Booting off original sealed APFS snapshot

 

  • Like 2
  • Thanks 1
  • Haha 1
Link to comment
Share on other sites

3 hours ago, fusion71au said:

 

Yeah, it looks like the OC integration process has resulted in bad legacy boot files (boot6, boot7) that hang the boot process before reaching the Clover GUI.

 

I found the issue and resolved it in release 5125.

  • Like 5
  • Thanks 2
Link to comment
Share on other sites

I can't boot Catalina with any Clover after r5122.

 

With latest r5125

If all quirks turned off, I get spontanous reboot after selecting macos to boot.

With default quirk settings, the Apple screen shows up and within split second I get spontaneous reboot.

 

I have AptioMemoryFix.efi in drivers\UEFI.  Should I remove it?

 

Thanks.

  • Like 1
Link to comment
Share on other sites

10 minutes ago, Zenith432 said:

I can't boot Catalina with any Clover after r5122.

 

With latest r5125

If all quirks turned off, I get spontanous reboot after selecting macos to boot.

With default quirk settings, the Apple screen shows up and within split second I get spontaneous reboot.

 

I have AptioMemoryFix.efi in drivers\UEFI.  Should I remove it?

 

Thanks.

As far as I try, I have to remove it. If not, then it will conflict with ...

 

Clover_r5125.pkg I gathered it for people who don't have it yet.

Edited by naiclub
Link to comment
Share on other sites

13 minutes ago, Zenith432 said:

I moved AptioMemoryFix.efi to drivers\off, but still same problem with spontaneous reboots as before.

boot with debug mode and with "-v debug=0x100 keepsyms=1" flags to see what is causing this, obtain Clover's debug log from CLOVER/misc

Link to comment
Share on other sites

21 minutes ago, Zenith432 said:

I moved AptioMemoryFix.efi to drivers\off, but still same problem with spontaneous reboots as before.

OpenRuntime.efi is used instead.

What is your chipset? Probably for Z490 there are others quirks should be set/unset. 

See RebuildAppleMemoryMap in OpenCore documentation.

https://github.com/acidanthera/OpenCorePkg/blob/master/Docs/Configuration.pdf

  • Like 1
Link to comment
Share on other sites

Installing 5125.pkg on 10.15.7 failed, even with sudo mount -uw /.

The system booted from another HDD's 5122 EFI which is a backup.

Reinstalling 5124.pkg also failed.

Found that BootX64.efi and CloverX64.efi were missing.

C&P 5125's BootX64.efi and CloverX64.efi, and the system boots fine now.

So I guess the pkg needs to be fixed?

 

Edited by Henry2010
  • Like 1
Link to comment
Share on other sites

Switching to virtualsmc.kext and virtualsmc.efi service driver i can boot even with clover 5124, i finally dismissed fakesmc, but now Smcfancontrol nor Macsfancontrol are working, the fans are stopped! how to fix this please?

Link to comment
Share on other sites

14 minutes ago, Vampirexx said:

Switching to virtualsmc.kext and virtualsmc.efi service driver i can boot even with clover 5124, i finally dismissed fakesmc, but now Smcfancontrol nor Macsfancontrol are working, the fans are stopped! how to fix this please?

These technologies work with fakesmc not with virtualsmc.

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

So if I stay on Catalina and want to update Clover past 5123, then I must use opencore quirks for my chipset, and not use aptio, right? Anything else I need to know to keep with updated Clover and Catalina? Thanks

Edited by jmacie
Link to comment
Share on other sites

1 minute ago, jmacie said:

So if I stay on Catalina and want to update Clover past 5123, the I must use opencore quirks for my chipset, and not use aptio, right?


Right. Have a look too to Slice's explanations in Clover change explanations topic 

  • Like 1
Link to comment
Share on other sites

10 minutes ago, mifjpn said:

Thank you for your efforts.
I will report r 5125.
It boots Catalina perfectly.
It boots Big Sur Beta 10 perfectly. (However, I have to choose the preboot entry)
Is this preboot entry issue a beta 10 issue?
I am wondering.I think.
Thank you.

I think the Preboot is not really an issue.

Well, if it'll not change in the future then I'll hide the normal partitions and use Preboot only. I don't see any problem with that, I think Apple did smth on purpose. 

  • Thanks 1
Link to comment
Share on other sites

×
×
  • Create New...