CaseySJ
Moderator
- Joined
- Nov 11, 2018
- Messages
- 22,208
- Motherboard
- Asus ProArt Z690-Creator
- CPU
- i7-12700K
- Graphics
- RX 6800 XT
- Mac
- Classic Mac
- Mobile Phone
It's a good thing that you were able to test both the original "Catalina 10.15.4 Fresh Install" package and the new "May 2020 Update". Now we know that the May 2020 update does not play nicely with Mojave.Using the files provided in Catalina 10.15.4 Fresh Install.zip macOS Mojave seems to start normally.
I need clarification: wanting to install macOS Catalina by creating a second APFS Volume on the same drive in a dualboot configuration I should use the same Catalina package 10.15.4 Fresh Install.zip or I should use the new May 2020 Update package to create the new Catalina USB install disk?
If you intend to have both (a) Mojave and (b) Catalina on the same physical SSD, but on different APFS Volumes, then the EFI folder needs to be capable of booting either of the two macOS versions. Right now only the original "Catalina 10.15.4 Fresh Install" can do that.
Yes -- if we use the original "Catalina 10.15.4 Fresh Install" zip package.After having possibly installed macOS Catalina, will it be possible to start Mojave or Catalina using the same configuration that I just verified working with macOS Mojave?
I've become quite a fan of Kubuntu 20.04 and also have a copy installed on a separate SSD in the Z490 Vision D. During installation I used the "manual" option to create a 200MB EFI partition and pointed the Boot Loader to the Linux disk (but not specifically to the EFI partition). However, because I'm using OpenCore on the Vision D, it does not currently recognize or boot Linux. So I always press F12 at the BIOS splash screen and choose the Linux disk. That always works.Furthermore, with the latest changes, a problem arose: in my multiboot system I have a separate drive with Ubuntu 18.04 with GRUB as Master bootloader, using the latest version of Clover (5119) selecting the Ubuntu entry from the Clover menu the GRUB menu appears but selecting any linux boot entry (i have several distributions installed in this drive) none of them start differently than what happen using the Clover 4920 version. I know that between the two versions of Clover there was an update Folders structure but I don't know if it could depend on this or on lack/update of some drivers.
...
In your case, however, some questions:
- Are you saying that with Clover v4920 you were able to boot the Linux installation(s) properly?
- But after the switch to Clover v5xxx the Grub boot loader appears, but Grub is unable to boot Linux?