Contribute
Register

<< Solved >> Cannot update Clover bootloader for Big Sur install

Joined
Oct 30, 2018
Messages
282
Motherboard
GIGABYTE Z370 AORUS Gaming 7
CPU
i7-8700K
Graphics
RX 5700XT
Mac
  1. iMac
  2. MacBook
  3. MacBook Pro
  4. Mac mini
  5. Mac Pro
Classic Mac
  1. eMac
  2. iMac
  3. Performa
  4. Power Mac
Mobile Phone
  1. iOS
My RevengeOfZee build currently runs Catalina 10.15.6
I decided to update to Big Sur and proceeded to perform the recommended updates of Lilu, WeG and AppleALC.
My current Clover version is 5119 with NVRAM emulation (installed by MultiBeast 12)

First of all, I am unable to update past Clover 5119. Catalina enters an immediate and perpetual reboot cycle after selecting the boot drive. Only by returning to 5119 can the system boot properly. ALL versions on the GitHub download page cause the same problem.

I also changed the system ID from MacMini to iMac18,1 as I don't think Big Sur supports the MacMini profile I had in place.

In a fit of angst, I decided to start up the Big Sur update anyway - with the current Clover 5119 in place. Needless to say, this did not go well.

1) Any suggestions on how to get a recent version of (Big Sur compatible) clover working?
2) Do all versions of Clover now have emulated NVRAM? I cannot find any versions that specify one way or the other.

Trimmed EFI attached.

Thank you
 

Attachments

  • EFI copy.zip
    3.2 MB · Views: 48

UtterDisbelief

Moderator
Joined
Feb 13, 2012
Messages
6,781
Motherboard
Gigabyte Z490i Aorus Ultra - OC 0.6.8
CPU
i5-10600K
Graphics
GT 1030
Mac
  1. iMac
  2. Mac mini
Classic Mac
  1. eMac
  2. iBook
Mobile Phone
  1. Android
My RevengeOfZee build currently runs Catalina 10.15.6
I decided to update to Big Sur and proceeded to perform the recommended updates of Lilu, WeG and AppleALC.
My current Clover version is 5119 with NVRAM emulation (installed by MultiBeast 12)

First of all, I am unable to update past Clover 5119. Catalina enters an immediate and perpetual reboot cycle after selecting the boot drive. Only by returning to 5119 can the system boot properly. ALL versions on the GitHub download page cause the same problem.

I also changed the system ID from MacMini to iMac18,1 as I don't think Big Sur supports the MacMini profile I had in place.

In a fit of angst, I decided to start up the Big Sur update anyway - with the current Clover 5119 in place. Needless to say, this did not go well.

1) Any suggestions on how to get a recent version of (Big Sur compatible) clover working?
2) Do all versions of Clover now have emulated NVRAM? I cannot find any versions that specify one way or the other.

Trimmed EFI attached.

Thank you

Hi there.

You need a later version of Clover to do anything at all with Big Sur. Your current version, as per the EFI upload, will not work.

The Clover team had to create a new, hybrid version of the bootloader which uses OpenCore elements, to get anywhere near installation. Most people have switched to OpenCore for Big Sur but the developer is trying to keep his project going for those who prefer Clover. A good way to get an idea of the differences is to run Clover Configurator as it lists the new "Quirks".

If you are still upgrading an existing Catalina installation then you need either the OpenCore 0.6.3 or Clover 5124 or later bootloader.

If you have decided to go for a completely clean installation then you need to create a new USB installer. See our beta guide.

P.S - The EFI folder seems to be for a different motherboard than the one in your profile. On top of that, with the UEFI drivers you have in place you need VirtualSMC.kext instead of FakeSMC.kext.

:)
 
Last edited:
Joined
Oct 30, 2018
Messages
282
Motherboard
GIGABYTE Z370 AORUS Gaming 7
CPU
i7-8700K
Graphics
RX 5700XT
Mac
  1. iMac
  2. MacBook
  3. MacBook Pro
  4. Mac mini
  5. Mac Pro
Classic Mac
  1. eMac
  2. iMac
  3. Performa
  4. Power Mac
Mobile Phone
  1. iOS
...with the UEFI drivers you have in place you need VirtualSMC.kext instead of FakeSMC.kext.

:)
Thanks for looking at it.

I will try replacing FakeSMC as suggested. But, I seem to recall a problem with this board and VirtualSMC when I first configured the system. Hazy as the memory is, I will try replacing it and see what happens. If I can get a newer Clover version installed, I should be able to buy some more time before being forced to address the Open Core switch.

I opened the case and checked the mainboard. The profile is correct. What leads you to believe the plist is configured for another mainboard? I'm curious if there are other unrelated fixes I could implement.
 
Last edited:

UtterDisbelief

Moderator
Joined
Feb 13, 2012
Messages
6,781
Motherboard
Gigabyte Z490i Aorus Ultra - OC 0.6.8
CPU
i5-10600K
Graphics
GT 1030
Mac
  1. iMac
  2. Mac mini
Classic Mac
  1. eMac
  2. iBook
Mobile Phone
  1. Android
Thanks for looking at it.

I will try replacing FakeSMC as suggested. But, I seem to recall a problem with this board and VirtualSMC

Big Sur needs it, I fear. What's more is, you have it's support file in your drivers/UEFI folder, which is the correct place for Clover v5*** versions. The other driver folders are "left overs".

The profile is correct. What leads you to believe the plist is configured for another mainboard? I'm curious if there are other unrelated fixes I could implement.

Not the config.plist. Look inside your ACPI/patched folder ...
 
Last edited:
Joined
Oct 30, 2018
Messages
282
Motherboard
GIGABYTE Z370 AORUS Gaming 7
CPU
i7-8700K
Graphics
RX 5700XT
Mac
  1. iMac
  2. MacBook
  3. MacBook Pro
  4. Mac mini
  5. Mac Pro
Classic Mac
  1. eMac
  2. iMac
  3. Performa
  4. Power Mac
Mobile Phone
  1. iOS
Big Sur needs it, I fear. What's more is, you have it's support file in your drivers/UEFI folder, which is the correct place for Clover v5*** versions. The other driver folders are "left overs".



Not the config.plist. Look inside your ACPI/patched folder ...
Apologies for the slow 'Thank You' to this. I have been distracted with other projects and trying to wrap my head around Open Core.

I will fix these issues and try again with 11.1
 
Last edited:
Joined
Oct 30, 2018
Messages
282
Motherboard
GIGABYTE Z370 AORUS Gaming 7
CPU
i7-8700K
Graphics
RX 5700XT
Mac
  1. iMac
  2. MacBook
  3. MacBook Pro
  4. Mac mini
  5. Mac Pro
Classic Mac
  1. eMac
  2. iMac
  3. Performa
  4. Power Mac
Mobile Phone
  1. iOS
Wound up doing a data backup and a clean install using OC 0.6.5 (prebuilt SSDTs though).
Remarkably, it worked perfectly the first time.
I then used the same USB installer on my SonOfZee build with a Z370N-WiFi mainboard with a changed out OTB-compatible WiFi/BT module. I had to switched the IntelMausi for the Realtek8111 kext for the correct LAN configuration. Again, installed on the first try.
Beginner's luck perhaps.
 
Last edited:
Top