I want to update a running Catalina installation on a Designare Z390 to Monterey. Because I have a tripe boot system running, I prefer to keep my existing Clover installation yet instead of migrating to Open Core. In an instruction, I read about the quirks which are required in the clover configuration now to make Big Sur or Monterey bootable.
One of the required quirks is RebuildAppleMemoryMap. But if I try to boot any macOS while this is switched on, Clover exists immediately and the next UEFI boot entry is beeing started. This affects the existing Catalina installation as well as the Monterey installer. If I turn this off, the existing Catalina installation starts as usual while trying to start the Monterey installer results in a Kernel panic.
Has anybody an idea, why RebuildAppleMemoryMap fails in my case?
Installed Clover version is 5132. BIOS version is F9I, CPU is an i7-9700K.
Edit: If I remove all boot entries except Clover, the bootloader starts again if I try to boot macOS while RebuildAppleMemoryMap is turned on but then, there aren't any systems shown which are placed on my NVME disks. macOS is installed on a NVME disk. For any reason, the NVME support gets lost if this quirk is activated after you try to start macOS in my case. But why?