- Apr 16, 2017
- Gigabyte X299 WU-8
- RX 580
- Mobile Phone
Booting an OS is just a matter of invoking the correct boot file, whether BOOTx64.efi or GRUBx64.efi, etc. (Booting macOS on foreign hardware is much more complicated than that, but booting an OS that is supported by the firmware is much easier.)
On my Z490 Vision D, OpenCore detects macOS and Windows, but not Ubuntu Linux. Clover, however, auto-detects everything. With OpenCore we have to create an entry in Misc section using PCI paths that can be determined by running OpenShell.
Here are the volumes that OpenCore and Clover have auto-detected:
We can see that Clover has detected Linux, but OpenCore has not -- even with ScanPolicy set to 0.
- OpenCore on top
- Clover on bottom
View attachment 487981
View attachment 487982
But after manually adding an entry in Misc as follows...
<key>Entries</key> <array> <dict> <key>Arguments</key> <string></string> <key>Auxiliary</key> <false/> <key>Comment</key> <string></string> <key>Enabled</key> <true/> <key>Name</key> <string>Ubuntu Linux</string> <key>Path</key> <string>PciRoot(0x0)/Pci(0x17,0x0)/Sata(0x2,0xFFFF,0x0)/HD(2,GPT,1224743C-A3D6-4286-AA06-4F251E336011,0x109000,0x32000)/\EFI\ubuntu\grubx64.efi</string> </dict> </array>
...OpenCore now displays an entry for Ubuntu, which in turn boots grubx64.efi:
View attachment 487983
This is also speculation because only the developers know whether it's feature complete and whether it's time to move to 1.0.0. My speculation is that it's still not feature complete.
But this semantic is largely irrelevant as long as OpenCore does what we need it to do.
Using the example from my Z490 Vision D, the issue with OpenCore is as follows:Again, that's not "linux" detection, that's just showing grub in the menu, unlike clover that has hardcoded paths that it looks for, OpenCore does not have any hardcoded paths to look for but it checks the firmware and other partition information to get boot entries (like macOS boot.efi, and for windows, it assumes bootx64 that is found in your EFI drive as a windows system, like a real mac would do). For me, I'm literally running the kernel directly without any need for another bootloader like grub/systemd-boot, since most linux kernels support EFISTUB and can be ran as an EFI application.
In order for OpenCore to be UEFI-compliant or at least consistent with prevailing UEFI norms, it needs to handle this case because both Linux and Windows add their boot loaders into the first EFI partition they find (by default). So a single computer with multiple operating systems will have one EFI partition with multiple sub-directories -- one for each of the OSes.I don't think OpenCore will change in that regard, it will just check for boot entries like a mac would do (that's the behavior acidanthera is going for), so for it to detect Linux like Clover do will most likely never happen, if you want you can just copy grubx64 binary to boot folder and rename it to bootx64, and it will do the job, or add the entry manually which is not wrong either. Check Misc section of OpenCore documentation (Dortania's html documentation conversion from pdf for webviewing).
Shanee does have some patches for Adobe and other apps. They are also working on performance issues.Speaking as someone who built a Ryzen 3900 XT system just last month, on OpenCore for the first time, I can heartily recommend OpenCore.
However I am now back on an Intel i7 10700 build instead. The Ryzen was super-fast and all that, but the lack of virtualisation apps (except Virtualbox), some unexplained weirdness with XCode no Android EMulator (see virtualisation) and the failure of most Adobe Creative Studio apps to even launch ended it for me.
That said - the AMD announcement is great news from www.tonymacx86.com